Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Monitoring & ops
2,408 results · page 54 of 81
- View details
leave-tracker-zhou210712SkillMonitoring & ops
Check leaves in progress, with deadline alerts and decisions that need to be made. Presents only the leaves that need action and explains why—not a status dashboard. Recommended to run weekly, or whenever a lawyer needs to know which leaves have upcoming approvals, certifications, or expiration dead
Ready to connect★ 73
- View details
privilege-log-review-zhou210712SkillMonitoring & ops
Evidence three-criteria review — performs a first-round review of the evidence list, makes obvious admissibility/relevance determinations and flags difficult items that require attorney review. Use when the user says "审查证据清单", "证据三性审查", "检查这些证据的可采性", or when there is an evidence list that needs to b
Ready to connect★ 73
- View details
sdlc-bug-reportSkillMonitoring & ops
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Ready to connect★ 74
- View details
tracedecay-dev-sweepSkillMonitoring & ops
TraceDecay Dev: Use for a full introspection-and-improvement pass over TraceDecay itself — triggers every dev skill in dependency order (diagnostics gate, evidence sweep across usage/logs/automation/hints/code-health, synthesis, fixes, verification). Use when asked to 'improve tracedecay from its ow
Ready to connect★ 74
- View details
tracing-functionsSkillMonitoring & ops
Use when the task is call-relationship shaped: "who calls X", "what does X call", "trace this", references before a rename, shortest path, recursion, or hubs. Trigger before grepping a function name — grep misses dynamic dispatch. Do NOT use to locate a symbol (tracedecay:exploring-code).
Ready to connect★ 74
- View details
analyzing-catastrophe-riskSkillMonitoring & ops
Structures catastrophe risk assessment with model output interpretation and accumulation monitoring. Use when analyzing cat risk, interpreting cat model results, or managing cat exposure.
Ready to connect★ 73
- View details
analyzing-insurance-financialsSkillMonitoring & ops
Structures insurance company financial analysis with combined ratio, reserve adequacy, and capital metrics. Use when analyzing insurance financials, evaluating combined ratios, or assessing reserve strength.
Ready to connect★ 73
- View details
anti-fraud-screeningSkillMonitoring & ops
Use this skill when the user needs insurance fraud risk screening. Suitable for scenarios such as application fraud identification, claims fraud alerts, and suspicious behavior analysis.
Ready to connect★ 73
- View details
ares-grafanaSkillMonitoring & ops
Reference for Grafana dashboards and specific Loki queries used to monitor and debug Ares operations via the grafana MCP server. Use when you need to handily check operation health, errors, agent restarts, or loot discovery.
Ready to connect★ 73
- View details
breach-credit-monitorSkillMonitoring & ops
Coordinates credit monitoring and identity theft protection services for individuals affected by a data breach. Covers vendor selection criteria, enrollment logistics, coverage duration (12-24 months), identity theft insurance options, communication to affected individuals, and enrollment rate track
Ready to connect★ 73
- View details
discoverSkillMonitoring & ops
[UDS] Assess project health, architecture, and risks before adding features to an existing codebase. Use when: onboarding to an unfamiliar or legacy project, sizing risk before starting a feature, building a risk register. Not for: ongoing metric tracking on a codebase you already know — use /metric
Ready to connect★ 73
- View details
durableSkillMonitoring & ops
[UDS] Guide fault-tolerant workflow design with checkpoints, retry policies, and rollback plans. Use when: a long-running workflow keeps failing partway, designing checkpoint granularity, choosing a retry or backoff strategy. Not for: responding to a production incident already in progress — use /in
Ready to connect★ 73
- View details
error-code-guideSkillMonitoring & ops
Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. Use when: defining error codes, creating error handling, designing APIs. Not for: log format and levels — use /logging-guide; handling errors that already reached production — use /incident. Keywords: error code, error handli
Ready to connect★ 73
- View details
logging-guideSkillMonitoring & ops
Implement structured logging with proper log levels and sensitive data handling. Use when: adding logging, debugging, setting up observability. Not for: metrics, traces, and alerting design — use /observability; error code taxonomy — use /error-code-guide. Keywords: logging, log level, structured lo
Ready to connect★ 73
- View details
metricsSkillMonitoring & ops
[UDS] Track development metrics, code quality indicators, and technical debt over time. Use when: assessing ongoing project health, classifying and trending technical debt, reporting code quality to a team. Not for: first-time assessment of an unfamiliar codebase — use /discover; test coverage speci
Ready to connect★ 73
- View details
retrospectiveSkillMonitoring & ops
[UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Not for: post-mortems for a production incident — use /incident; tracking metric trends between retros — use /metrics. Keywords: retrospective,
Ready to connect★ 73
- View details
sloSkillMonitoring & ops
Guide SLI selection, SLO setting, and Error Budget management. Use when: defining service quality targets, setting up SLO-based alerting, Error Budget policy. Not for: instrumentation and metric collection — use /observability; responding to an active breach of the target — use /incident. Keywords:
Ready to connect★ 73
- View details
datagrok-calc-columnSkillMonitoring & ops
Add a calculated, formula-based column to a dataframe via the datagrok_exec tool. Use whenever the user asks to compute, derive, add, or create a new column from existing columns — LipE, ratios, log/round, heavy atom count, any expression in the Datagrok formula DSL. Replaces hand-written addNewFloa
Ready to connect★ 72
- View details
dotnet-logging-configurationSkillMonitoring & ops
Configures structured logging with ILogger<T> and ILoggerFactory following Microsoft best practices. Includes Serilog setup, log enrichment, and logging source generators for high-performance logging.
Ready to connect★ 72
- View details
dotnet-options-patternSkillMonitoring & ops
Implements the Options pattern for strongly-typed configuration in .NET. Covers IOptions<T>, IOptionsSnapshot<T>, and IOptionsMonitor<T> with validation and reload support.
Ready to connect★ 72
- View details
dotnet-pipeline-behaviorsSkillMonitoring & ops
Generates MediatR Pipeline Behaviors for cross-cutting concerns like logging, validation, exception handling, caching, and performance monitoring. Implements the decorator pattern around handlers.
Ready to connect★ 72
- View details
network-watcherSkillMonitoring & ops
Audit and monitor network requests made by OpenClaw skills. Detects data exfiltration, unauthorized API calls,
Ready to connect★ 72
- View details
winget-defender-fpSkillMonitoring & ops
Use when a ryl winget-pkgs validation PR is blocked by a Microsoft Defender false positive (`Validation-Defender-Error` / "Installer failed security check"). Covers the transient-vs-reproducible decision, local Defender + VirusTotal reproduction, the WDSI false-positive submission, and the log noise
Ready to connect★ 72
- View details
agent-interaction-auditSkillMonitoring & ops
Load when the user asks for private agent interaction audits from local Codex/Claude Code traces, task profiles, tool-call decisions, collaboration bottlenecks, prompt/rule or automation-log audits, closeout retrospectives, or evidence-backed Skill/project-rule/Eval/SOP/OKF improvements.
Ready to connect★ 71
- View details
android-device-debugSkillMonitoring & ops
Android device or emulator debugging, logs, instrumented tests, crashes, and network issues.
Ready to connect★ 71
- View details
atlas-changelogSkillMonitoring & ops
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
Ready to connect★ 71
- View details
autonomous-loopsSkillMonitoring & ops
Performing repetitive enumeration across many targets - Running batch vulnerability scans on multiple hosts - Monitoring for changes in target environment - Executing attack chains that require iterative steps - User says \"loop\", \"automate\", \"batch\", \"repeat.
Ready to connect★ 71
- View details
bench-profileSkillMonitoring & ops
Design a performance benchmark for an API — test scenarios, metrics, and tooling. Use when asked to "benchmark this API", "design a load test", or "measure throughput".
Ready to connect★ 71
- View details
bind-policySkillMonitoring & ops
Draft compliance policies required by a framework (access control, incident response, data retention). Use when asked to "write an access control policy", "draft our incident response policy", or "we need a data retention policy".
Ready to connect★ 71
- View details
blue-detectSkillMonitoring & ops
Design detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".
Ready to connect★ 71
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
53,585 of the 54,017 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.