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,353 results · page 23 of 79
- View details
fp-checkSkillMonitoring & ops
Systematic false positive verification for security findings. Provides structured methodology to confirm or dismiss scanner results, manual audit findings, and automated alerts. Adapted from Trail of Bits. Use when triaging security scan results or verifying audit findings.
Ready to connect★ 530
- View details
harvest-monitorSkillMonitoring & ops
Web change monitoring - track changes on pages, detect updates, changelog diffs
Ready to connect★ 530
- View details
hipaa-complianceSkillMonitoring & ops
HIPAA compliance - PHI protection, technical/administrative/physical safeguards, minimum necessary standard, BAA requirements, de-identification, access logging
Ready to connect★ 530
- View details
incident-response-patternsSkillMonitoring & ops
Incident severity classification, runbook templates, root cause analysis, and post-incident review
Ready to connect★ 530
- View details
depot-ciSkillMonitoring & ops
Read CI logs, test results and failure diagnoses for the `Check` workflow, and retry its failed jobs, using the `depot` CLI against `DEPOT_TOKEN`. Use whenever a `Check / …` check run is red and you need the actual failure — the GitHub API returns empty output for these checks and `depot.dev` links
Ready to connect★ 520
- View details
tracingSkillMonitoring & ops
Architecture and API reference for @dxos/tracing. Use when working with TracingBackend, TRACE_PROCESSOR, @trace.resource(), @trace.span(), @trace.info(), metrics counters, diagnostics, ContextRpcCodec, tracing-types.ts, trace-processor.ts, or api.ts.
Ready to connect★ 520
- View details
user-submissionsSkillMonitoring & ops
Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path. Use when working a DX-#### issue created from a user report, when an issue body names a `composer-feedback-logs-*` NDJSON bundle, or when asked to find the root
Ready to connect★ 520
- View details
debugging-techniquesSkillMonitoring & ops
Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe debugging techniques with distributed tracing and correlation IDs. Use when setting breakpoints, debugging containers/pods, rem
Ready to connect★ 517
- View details
implementing-observabilitySkillMonitoring & ops
Monitoring, logging, and tracing implementation using OpenTelemetry as the unified standard. Use when building production systems requiring visibility into performance, errors, and behavior. Covers OpenTelemetry (metrics, logs, traces), Prometheus, Grafana, Loki, Jaeger, Tempo, structured logging (s
Ready to connect★ 517
- View details
implementing-realtime-syncSkillMonitoring & ops
Real-time communication patterns for live updates, collaboration, and presence. Use when building chat applications, collaborative tools, live dashboards, or streaming interfaces (LLM responses, metrics). Covers SSE (server-sent events for one-way streams), WebSocket (bidirectional communication), W
Ready to connect★ 517
- View details
managing-incidentsSkillMonitoring & ops
Guide incident response from detection to post-mortem using SRE principles, severity classification, on-call management, blameless culture, and communication protocols. Use when setting up incident processes, designing escalation policies, or conducting post-mortems.
Ready to connect★ 517
- View details
siem-loggingSkillMonitoring & ops
Configure security information and event management (SIEM) systems for threat detection, log aggregation, and compliance. Use when implementing centralized security logging, writing detection rules, or meeting audit requirements across cloud and on-premise infrastructure.
Ready to connect★ 517
- View details
monitoring-pull-requestsSkillMonitoring & ops
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base
Ready to connect★ 516
- View details
use-sentry-cli-debugSkillMonitoring & ops
Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.
Ready to connect★ 505
- View details
tracing-recompositions-at-runtimeSkillMonitoring & ops
Use this skill to instrument a Jetpack Compose composable with `@TraceRecomposition` from `skydoves/compose-stability-analyzer` so per-recomposition diffs (which state or parameter changed, what value transition) print to logcat under the `Recomposition` tag. Works in release-with-debug-symbols buil
Ready to connect★ 503
- View details
ai-slopSkillMonitoring & ops
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, esp
Ready to connect★ 501
- View details
code-explorerSkillMonitoring & ops
Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need to understand how a feature works before modifying or extending it, when dispatched as a sub-task d
Ready to connect★ 501
- View details
eval-agentsSkillMonitoring & ops
Score a review agent (Rex/Hakim/Tariq) against a labeled PR corpus — ground-truth defect-set overlap, never a prose rubric. Headline metric is approve-precision.
Ready to connect★ 498
- View details
monitoring-auditSkillMonitoring & ops
Observability audit — logging, error tracking, health endpoints, alerting, runbooks. Deep-dive for /launch-check monitoring.
Ready to connect★ 498
- View details
pr-createSkillMonitoring & ops
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses
Ready to connect★ 497
- View details
inflectionSkillMonitoring & ops
Auto-detect biggest acceleration/deceleration inflections across all metrics
Ready to connect★ 487
- View details
make-traceSkillMonitoring & ops
Turn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace. Lift it into a DAG, write a contract per step, place inputs, and drive the full run lifecycle to verify it. Use whenever someone wants to make a trace from a sour
Ready to connect★ 486
- View details
researchers-primary-sourceSkillMonitoring & ops
Researches the subject's own words from tweets, blogs, forums, and chat logs. Use when research needs direct quotes or first-person accounts.
Ready to connect★ 483
- View details
researchers-securitySkillMonitoring & ops
Researches malware analysis, CVEs, attribution reports, and hacker community sources. Use when the album subject involves cybersecurity incidents or threat actors.
Ready to connect★ 483
- View details
observability-testing-patternsSkillMonitoring & ops
Observability and monitoring validation patterns for dashboards, alerting, log aggregation, APM traces, and SLA/SLO verification. Use when testing monitoring infrastructure, dashboard accuracy, alert rules, or metric pipelines.
Ready to connect★ 475
- View details
qcsd-development-swarmSkillMonitoring & ops
Use when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.
Ready to connect★ 475
- View details
qcsd-production-swarmSkillMonitoring & ops
Use when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.
Ready to connect★ 475
- View details
qe-defect-intelligenceSkillMonitoring & ops
Predicts defect-prone code using change frequency, complexity metrics, and historical bug patterns. Use when predicting defects before they escape, analyzing root causes of test failures, learning from past defect patterns, or implementing proactive quality management.
Ready to connect★ 475
- View details
quality-metricsSkillMonitoring & ops
Tracks quality metrics including defect density, test effectiveness ratio, DORA metrics, and mean time to detection. Use when establishing quality dashboards, defining KPIs, evaluating test suite effectiveness, or reporting quality trends to stakeholders.
Ready to connect★ 475
- View details
test-idea-rewritingSkillMonitoring & ops
Transform passive 'Verify X' test descriptions into active, observable test actions. Use when test ideas lack specificity, use vague language, or fail quality validation. Converts to action-verb format for clearer, more testable descriptions.
Ready to connect★ 475
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.
52,524 of the 52,958 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.