Debug & triage
5,138 rows, by stacks then stars
1,113 of these skill files have been read, by 1,020 distinct authors, and what they tell an agent counted. What Debug & triage authors agree on, and what they forbid
AshExplained/roblox-skills/roblox-triage Skill
0★ repoTriage Roblox game slices and bug reports through a small state machine so only fully-specified, playtestable work gets built. Use when the user wants to review incoming slices or bugs, decide what to build next, prepare a slice for building, mark work ready, or manage the roadmap/issue workflow. Keeps Claude from picking up vague, half-specified work and building the wrong thing.
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/golang-observability Skill
0★ repoWhen to activate: Go logging with slog, structured logging, metrics with Prometheus, distributed tracing with OpenTelemetry
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/logging-patterns Skill
0★ repoWhen to activate: logging, structured logs, ELK, EFK, fluentd, fluent bit, log aggregation, correlation ID, log levels, Loki
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/python-logging Skill
0★ repoWhen to activate: Python logging, structlog, JSON logs, correlation IDs, log levels, observability setup
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/rust-error-handling Skill
0★ repoWhen to activate: Rust error handling, thiserror, anyhow, custom errors, Result, question mark operator, error propagation
Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/rust-observability Skill
0★ repoWhen to activate: Rust tracing, logging, metrics, spans, instruments, OpenTelemetry, tracing-subscriber, prometheus, structured logging
Srltas/claude-skills/review-triage Skill
0★ repoTriage the review comments on your pull request. Fetches a PR's reviews (inline code comments, review summaries, and PR-level comments, from humans and bots) and, for each, gives an easy Korean summary, judges whether it is valid by checking the actual code, then either drafts a fix plan (if valid) or a reasoned reply explaining why not (if not). Analysis and drafts only: it does not post replies or change code. Use when your PR has review feedback you want to understand and respond to. Triggers on phrases like 'PR 리뷰 정리해줘', '리뷰 코멘트 타당한지 봐줘', '리뷰 대응', 'triage my PR reviews', 'help me respond to PR review'.
NeuralMedic-DE/claude-skills/medical-ai-compliance-gate Skill
0★ repoAudit a medical/health-AI codebase or data pipeline against GDPR, EU MDR, ISO 27001, and SOC 2 — gated by automated checks that actually run. A stdlib Python scanner runs ~29 heuristics from a 47-control catalog (hardcoded secrets, PII/PHI in logs, encryption at rest, TLS, audit logging, retention/ erasure, RBAC, EU data residency, consent, model cards, data lineage, SBOM, dependency pinning, CI/tests/monitoring), maps each finding to its control + framework + severity, fails the build on blocking gaps, and sends the rest to a mandatory human attestation. Use for a compliance/readiness audit or gap analysis, a healthcare/medical-AI compliance checklist or CI gate, or a DPIA/RoPA starting point. Honest scope: engineering assistance to PREPARE for compliance — NOT legal advice, certification, an MDR conformity assessment/CE marking, or a Notified Body, ISO, or SOC 2 audit. Triggers: "GDPR", "MDR", "medical device software", "MDSW", "ISO 27001", "SOC 2", "compliance gate", "DPIA", "healthcare AI audit".
SkillMedev/ai-engineer-toolkit/skills/error-handling Skill
0★ repoDesigns typed, observable, recoverable error handling - an explicit taxonomy of retryable vs terminal failures, Result types at boundaries, single-point logging, and retry policies with real backoff numbers. Use when someone asks "should I retry this error", "how do I structure error types", "why are my logs full of duplicate stack traces", "where do I put the try/catch", or is designing failure paths for an API, job, or client. Do NOT use for building the circuit breaker component itself - use circuit-breaker-builder instead; do NOT use for handling 429s against third-party APIs - use rate-limit-handler instead; do NOT use for writing user-facing error copy - use error-message-writer instead.
The same file is in 1 other repository
whobat/AI-Agent-skills/skills/nav-2009/nav2009-troubleshooting Skill
0★ repoTriage runbook and router for Microsoft Dynamics NAV 2009 operational problems — covers RTC/Classic client can't connect, Service Tier won't start, login/permission and license errors, slowness/locking/deadlocks during posting, posting and No.-Series errors, NAS/Job Queue not running, .NET/COM failures (R2), RDLC report failures, deployment/compile failures, and crashes. It maps a reported symptom to the most likely cause and routes you to the right sibling NAV 2009 skill. Use when: a user reports any NAV/Navision error or outage and you need to find the cause fast; "RTC won't connect"; "the NAV service won't start"; "posting is failing"; "the Job Queue stopped"; or any other NAV 2009 operational complaint where the root cause is unknown.
whobat/AI-Agent-skills/skills/sql-server/sqlserver-perf-triage Skill
0★ repoDiagnose performance problems on ANY Microsoft SQL Server instance or database. The bundled script collects a read-only DMV snapshot (top queries by CPU/reads, wait statistics, live blocking, deadlock graphs, missing/unused indexes, fragmentation, stale statistics, server/database configuration) as JSON; the agent interprets it and proposes next actions. Use when the user reports a slow SQL Server, a slow database/application, blocking or deadlocks, or wants a SQL Server health check — e.g. "why is SQLSRV01 slow", "check the SQL server behind our app", "are there blocking sessions right now". Do NOT use for Dynamics NAV 2009 or AX 2012 databases — use nav2009-sql-performance / ax2012-sql-performance, which add the application-specific interpretation. Requires PowerShell 7+ and VIEW SERVER STATE.
whobat/AI-Agent-skills/skills/windows-ops/rds-profile-triage Skill
0★ repoRead-only triage of Remote Desktop Services (RDS) session-host profile & WinRM-host health across one or many servers. The bundled script collects (over WinRM, with a CIM-over-DCOM fallback for hosts whose WinRM host process won't even launch) profile-hive leaks, temp-profile sprawl, ProfileList corruption, the roaming-profile path read RAW, drain state, and User-Profiles-Service failures grouped BY THE ACTUAL USER, then renders a uniform deterministic report the agent relays (JSON optional). Use when a user reports RDS/terminal-server problems like "user gets logged out immediately / logged off right after sign-in", "everyone's getting temporary profiles", "settings don't save on the RDS farm", "the session host won't accept logins", or "can't PowerShell-remote into the RDS server (could not launch a host process)". Do NOT use for generic event-log sweeps (use win-eventlog-triage) or SQL Server issues (sqlserver-perf-triage). Requires PowerShell 7+ and a tier-admin credential (prompted).
whobat/AI-Agent-skills/skills/windows-ops/win-eventlog-triage Skill
0★ repoTriage Windows Event Logs across one or many servers. Pulls Critical/Error events (System + Application by default; Security opt-in) over a time window via PowerShell Remoting (WinRM), groups them deterministically, and returns JSON the agent turns into a short, critical-first summary. Use when the user wants to check/triage/investigate Windows server event logs — e.g. "what happened on SRV01 overnight", "triage the event logs on these servers", or "any errors across the file servers in the last 12 hours". Requires PowerShell 7+ and a tier-admin credential (always prompted).
SkillMedev/security-compliance-hardening/skills/vulnerability-triage Skill
0★ repoPrioritizes vulnerability findings from scanners, pentest reports, and bug bounty submissions by real-world exploitability rather than raw CVSS, assigning internal severity tiers with fix SLAs. Use when someone asks "which of these CVEs do we fix first", "triage this scanner report", "is this CVSS 9.8 actually critical for us", or is facing a wall of security findings and needs an actionable queue. Do NOT use for enumerating threats in a design that has not shipped - use threat-model-stride instead; for an active exploitation incident in production, use sev-triage; for reviewing the code itself, use secure-code-review.
The same file is in 1 other repository
mbackschat/a12-dmtool-releases/skills/a12-dmtool-bug-report Skill
0★ repoProduce a well-isolated bug-and-findings report for the dmtool CLI (a12-dmkits / A12 kernel) and save it to a folder the user picks. Use when a user hits an error, crash, internal error, or unexpected behaviour in dmtool, when they want to capture findings / DX friction / improvement notes, or when they ask to write or file a bug report against dmtool. Covers reading the result envelope (telling an internal tool error apart from a rejected input), shrinking to a minimal repro, an affected-vs-unaffected table, classifying genuine defects vs. your own input mistakes, a verbatim replay log, and a self-audit — then writing the report to a folder the user can upload or send however they like.
cody-hutson/pmo-platform/operations/skills/pmo-tier-2-support Skill
no license0★ repoEscalation/RCA support Specialist — consumes the pmo-tier-1-support Escalation Handoff Record, performs a structured root-cause analysis, drives the issue to resolution, and authors/updates a runbook so it becomes first-line-resolvable. Owns the RCA method (invokes core/disciplines/root-cause-analysis.md, never redefines it); composes artifact-generator (runbook + RCA record), routes via file-router / pmo-knowledge-manager (persist to the knowledge base), and intake-desk (tracked work items) — invokes them via the core/ registry skill-chain (ADR-019). Modes: RCA · Drive-to-Resolution · Runbook-Authorship. Use for an escalated or novel problem that needs a causal explanation. Triggers: "tier 2 support", "escalated issue", "root cause this", "RCA", "write a runbook for this", "why did this break", "this keeps happening — why".
cody-hutson/pmo-platform/release/skills/pipeline-triage Skill
no license0★ repoRuns Stage-2 Triage over the platform's improvement backlog — reads `status: proposed` GitHub Issues, executes the Phase-A analysis sequence (A1–A6.5: DoR completeness, duplicate/subsumption + similarity, dependency-state validation + native-dep mirror, feasibility, priority re-evaluation, oversize routing, per-issue summary, management-task signals), and produces ONE consolidated triage summary with a per-issue Approve/Defer/Reject recommendation. Auto-execute is the operative default: the A1–A6 enrichment runs end-to-end without per-action approval; only the state-mutating Close/Reject requires operator confirmation, and the Approve/Defer/Reject verdict itself stays operator-only (Tier 3). Reads the pipeline improvement backlog, not the Jira / project delivery backlog. Triggers: "triage the proposed queue", "run Stage-2 triage", "triage the improvement backlog", "run the triage analysis on the proposed issues", "what's the triage recommendation for the proposed backlog".
scoobydrew83/skills/plugins/coordinated-skills/skills/repo-troubleshooting-guide Skill
0★ repoGenerate a clean, professional troubleshooting guide (a TROUBLESHOOTING.md) by analyzing a code repository — detecting its tech stack and mining real evidence (raised exceptions, error strings, env vars, ports, Docker services, CI) to document common failure modes with step-by-step fixes. Use this whenever the user wants to create, build, or generate a troubleshooting doc, guide, runbook, or ops reference for a repo, codebase, or project; wants to document common errors, setup problems, failure modes, or "how to fix X"; or points Claude at a repository and asks for a debugging/operations reference. Trigger even if the user doesn't say the exact word "troubleshooting" — e.g. "document the common errors in this repo", "make a debugging runbook", "build a setup-issues guide", "write an ops doc for this project".
SkillMedev/database-performance/skills/replication-lag-debugger Skill
0★ repoDiagnoses read-replica lag and the stale-read bugs it causes, then applies read-after-write consistency strategies to fix them. Use when someone says "users see stale data right after saving", "my read replica is lagging behind the primary", "data written a second ago is missing from the next request", when replica lag monitoring alerts or grows after a backfill, or when deciding which reads must hit the primary versus a replica.
The same file is in 1 other repository
Sidsaladi9/persona-os/plugins/product-manager-os/skills/triage-requests Skill
0★ repoSorts a pile of inbound feature requests from sales, support, and users into themes, quantifies demand behind each, and recommends build / watch / decline with a templated reply for every requester. Use when you say "I have 40 requests to go through," "what are people actually asking for," "triage this feedback dump," "theme these tickets," or "should we build this or say no?"
SkillMedev/incident-response-command/skills/sev-triage Skill
0★ repoClassifies incident severity (SEV1-4) using impact, scope, and urgency signals and decides who to page. Use when an alert fires or a report comes in and a severity call must be made quickly.
The same file is in 1 other repository
justhandledlabs/skills/skills/env-doctor-free Skill
0★ repoDiagnose local project environment issues that prevent apps from starting or running. Use when the user says "why won't this run", "check my environment", "env doctor", "diagnose startup issue", "it works on my machine", or asks for help debugging missing dependencies, runtime versions, port conflicts, .env problems, file permissions, or stopped services.
The same file is in 2 other repositories
digitaldreams/tuhin/skills/log-analyzer Skill
0★ repoLaravel log file analyzer for expert-level bug diagnosis. Use this skill whenever the user mentions 'laravel.log', 'check the log', 'analyze logs', 'log file', 'there's an error in the log', or asks to diagnose, investigate, or fix a bug from a Laravel log file. Triggers on any mention of Laravel errors, exceptions, undefined variable errors, or stack traces from a Laravel application. This skill reads the log file, isolates actionable errors (ignoring INFO/DEBUG/routine logs), identifies the root cause by tracing into App-namespaced source files, inspects database table structure when model-related, and recommends a minimal, pattern-consistent fix. Always use this skill before attempting to diagnose any Laravel bug from a log.
bradmccloskey/claude-cisco-skills/cisco-troubleshoot Skill
0★ repoGenerate Python scripts for troubleshooting Cisco network issues. Use when the user needs to diagnose connectivity problems, protocol issues, performance problems, or collect diagnostic data from Cisco devices.
lankyjo/lankyjo-core-skills/skills/code/diagnose Skill
no license0★ repoDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
The same file is in 21 other repositories
lankyjo/lankyjo-core-skills/skills/code/triage Skill
no license0★ repoTriage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
The same file is in 14 other repositories
jgamaraalv/delivery-loop/.claude/skills/diagnose Skill
0★ repoDisciplined diagnosis loop for hard bugs and performance regressions — reproduce → hypothesise → instrument → fix → regression-test. Use when asked to diagnose/debug, something is broken or failing, or a perf regression is reported.
Fanout cve validation debugger
omonuj/claude-horizon-skills/skills/fanout-cve-rollout/fanout-cve-validation-debugger Skill
no license0★ repoFetches and interprets validation logs (No-Op and Oracle) for the fanout-cve-rollout task (<TASK_ID>). Maps each of the 5 reward-shaped subscores' failures to a root cause and the smallest safe fix. Use after a validation fails before editing anything.
omonuj/claude-horizon-skills/skills/maddy-delivery-split-brain/maddy-validation-debugger Skill
no license0★ repoFetches and interprets validation logs (No-Op and Oracle) for the maddy-delivery-split-brain task (<TASK_ID>). Maps observed log patterns to root causes and the smallest safe fix. Use after a validation fails to understand why it failed before editing anything.
omonuj/claude-horizon-skills/skills/oncall-schedule-coverage-collapse/oncall-validation-debugger Skill
no license0★ repoFetches and interprets validation logs (No-Op and Oracle) for the oncall-schedule-coverage-collapse task (<TASK_ID>). Maps observed log patterns to root causes and the smallest safe fix. Use after a validation fails to understand why it failed before editing anything.
omonuj/claude-horizon-skills/skills/variation-fanout-pipeline-break/mtls-validation-debugger Skill
no license0★ repoFetches and interprets validation logs (No-Op and Oracle) for the variation-fanout-pipeline-break task (<TASK_ID>). Maps observed log patterns to root causes and the smallest safe fix. Use after a validation fails to understand why it failed before editing anything.
omonuj/claude-horizon-skills/skills/variation-istio-split-brain/istio-validation-debugger Skill
no license0★ repoFetches and interprets validation logs (No-Op and Oracle) for the variation-istio-split-brain task (<TASK_ID>). Maps observed log patterns to root causes and the smallest safe fix. Use after a validation fails to understand why it failed before editing anything.
kochellenk-afk/claude-marketing-skills/skills/meta-creative-engine Skill
0★ repoPlan, test, diagnose, and iterate Meta (Facebook and Instagram) paid ad creative for ecommerce and content or creator clients. Creative is the primary performance lever on Meta, so this treats it as a testing and diagnostic system, not a "write me ads" tool. Use whenever the work involves Meta ad creative, whether building a creative test plan or brief, choosing angles, hooks, and formats to test, diagnosing why a Meta ad or account underperforms (weak hook, weak hold, poor CTR, high CPM, rising frequency, fatigue), or scaling and iterating a winning ad. Trigger on Meta ads, Facebook ads, Instagram ads, ad creative testing, hook rate, thumbstop, "why are my Meta ads not converting", "my Facebook ads stopped working", "scale my winning ad", or "refresh fatigued creative". Ecommerce optimizes cost per purchase and ROAS; content clients optimize cost per subscriber, lead, or engaged view. Do NOT use for Google Ads, organic social production (use social-goddess), or account-wide unit economics.
joshphoenix1/skill-security-audit/skills/skill-doctor Skill
0★ repoDiagnose hygiene problems across an installed skill set — routing token cost, vague or missing trigger descriptions, overlapping triggers between skills, and duplicates installed in multiple places. Use when the user asks to tidy, audit, trim, or debug their skills, when skills fire at the wrong time or not at all, or when too many skills are installed.
willianbs/skills/defect-analyst Skill
0★ repoInvestigates bugs with evidence and analyzes root causes. Use for defects, incidents, flakes, and “why did this break?” work. Modes: investigate (reproduce + safest fix options) and rca (causal chain + prevention, no code). Replaces debugging-investigator and root-cause-analyzer. Never guesses or patches symptoms without evidence.
Alexxiang2008/awesome-skills-map/skills/第6章智能邮件分类与回复助手/智能邮件分类与回复助手/email-triage Skill
0★ repo智能邮件分类与回复助手 - 收件箱零焦虑。邮件优先级分类(紧急/重要/可延后)、智能回复草稿生成、待办事项自动提取。支持 /email-triage 或 /邮件分类 或 /收件箱 命令启动。
HamzaYM/reliable-ai-skills/skills/debugging-playbooks/systematic-debugging-playbook Skill
0★ repoUse when debugging any bug, regression, or failing test, before proposing a fix, and especially before editing a file you know is a frequent source of regressions. Establishes ground truth before hypothesizing, and defines the discipline for multi-round fix loops after a review pass finds problems.
EliasAli0720/HIPAA-agent-skill/skills/hipaa-code-review Skill
0★ repoReviews code, diffs, and infrastructure-as-code for HIPAA violations — PHI in logs and URLs, non-BAA analytics and crash SDKs, missing encryption, weak access control and audit logging — and ships a runnable PHI scanner script. Use when asked to review code for HIPAA, scan for PHI, check a diff for PHI leaks, audit a healthcare codebase, or verify a health app's code before release.
Zerif007/Claude_Legal-Bangladesh_Edition/bd-commercial-legal/skills/nda-triage Skill
0★ repoFast GREEN/YELLOW/RED triage of inbound NDAs under Bangladesh law so lawyer time goes only where needed. Use whenever an NDA, confidentiality agreement, or "mutual non-disclosure" lands — including when a business user just asks "can we sign this".
gmmh1/claude-paid-media-skills/skills/creative-performance-analysis Skill
0★ repoDiagnose why a specific ad creative is winning or losing using the generalized hook-hold-click-convert funnel, applicable across any platform. Triggers on 'why is this ad underperforming', 'diagnose my creative', or 'where in the funnel is this ad failing'. Platform-agnostic diagnostic framework — platform-specific versions (meta-ads-creative-analytics) apply this with platform-native metrics.
kalshamsi/fable-discipline-skills/skills/root-cause-before-fixing Skill
0★ repoDiagnose the underlying cause with evidence before proposing or applying any fix. Use this whenever anything is broken, failing, or degraded — bugs, errors, metric drops, missed deadlines, quality problems, process breakdowns, confusing behavior, or any "why is X happening", "X stopped working", "X got worse", "fix this" request. Trigger even when the cause looks obvious or the user has already named a suspect: a symptom that pattern-matches a known failure often has a different cause, and this skill exists precisely for those cases.
kugamon/salesforce-core-skills/plugins/salesforce-core/skills/sf-debug Skill
no license0★ repoCaptures and analyzes Salesforce debug logs through the Tooling API — trace flag setup, log retrieval, parsing for exceptions, SOQL-in-loop detection, CPU/heap/limit analysis, and row-lock diagnosis — all MCP-first against the live org. Use when the user hits an error in Salesforce, mentions debug logs, governor limits, "too many SOQL queries", CPU timeouts, UNABLE_TO_LOCK_ROW, flow errors, or asks why something failed in the org. Usage: /sf-debug [trace|logs|analyze|limits] {user|class|logId} ...
gitsukrit/claude-skills/phi-safe-logging-enforcer Skill
0★ repoEnforce HIPAA Safe Harbor de-identification (45 CFR §164.514(b)(2)) and Security Rule audit controls (45 CFR §164.312(b)) whenever generating Python code that logs, traces, or emits telemetry involving PHI. Use this skill whenever the user asks to build, modify, review, or refactor code that touches Python `logging`, `structlog`, `loguru`, Langfuse, LangSmith, OpenTelemetry, Sentry, Datadog, or any other observability/telemetry surface in a healthcare AI, clinical, patient-facing, or PHI-adjacent context. Also use when the user asks for audit trail implementations, LLM API call logging, error tracking, or any code that will send request/response bodies to a third-party observability service. Do not wait for explicit "HIPAA" framing — trigger on any healthcare-adjacent logging or telemetry request, since PHI leakage into observability tools is one of the most common breach patterns and is invisible in code review without this discipline.
allenlee0430/allenlee-lab-skills/downloads-triage Skill
0★ repoSort and file loose documents in ~/Downloads (and Desktop) into Bowen Li's numbered filing scheme. Use to repeat the auto-organization, file new arrivals, find a misfiled document, or clean up. Triggers on "organize my downloads", "clean up files", "sort my desktop", "file these", "where did X go".
kelsi-bizer/bizer-ai-agent-skills/skills/lead-triage Skill
0★ repoCapture, qualify, and route every incoming lead so none slip through the cracks. Works from whatever the owner gives you — a name they mention, a web-form or social message, a call note, or an inbound email. Dedupes against people already known, records the lead with a fast qualification read, logs one concrete next step, and drafts a first reply. Use when someone reaches out about work, the owner mentions a new prospect, or a pile of inquiries needs sorting.
meturley/trail-marker-geo/skills/extractability-check Skill
0★ repoDiagnose whether an AI retrieval crawler can actually see and cite a candidate's web page. Use whenever someone gives a page URL and asks what an "AI crawler sees," whether their page is "citable," "extractable," "visible to AI," "retrievable," or "AI-readable" — or asks why their content isn't getting cited/surfaced by AI answer engines. Fetches the page as a non-JS-executing bot would (raw server HTML) and reports whether substantive content is present pre-hydration, whether facts are front-loaded, dated, and sourced, whether Person/FAQPage JSON-LD exists, and whether headings are questions/topics vs slogans. Routes each finding to the right fix skill in this suite. Diagnostic only — never modifies the site. Trigger even when the user just pastes a URL and asks "how does this look to AI?"
sayonsom/srib-godot-skills-demo/.claude/skills/srib-triage Skill
0★ repoFront-door triage skill for the SRIB Godot 4.6 Android / 3D SmartThings home view project. Takes a list of feature requests, classifies each as a view (shaders/visuals), model (math/animation/simulation), integration (wiring/Android bridge/signal routing), or design (UX/layout/theming) concern, and routes each to the matching feature-level skill — srib-view, srib-model, srib-integration, or srib-design. Use whenever the user pastes a backlog, says "triage these", "classify these features", "which skill should I use for X", or hands over a batch of ambiguous feature ideas for the SRIB Android app. Note: for Excel-file intake with formal ticket creation, prefer srib-identify instead.
ccpowerpack/claude-code-skills/skills/error-handling Skill
0★ repoDesign an error strategy for a module or service instead of sprinkling try/catch. Use when adding error handling, wrapping a flaky dependency, "make this robust", "handle failures here", reviewing code with catch blocks, or designing retries/timeouts. Refuses to write handlers until every failure source in the diff is classified into a taxonomy with one designated pattern per class.
NorthStar-Analytics-LTD/skill-foundry/skills/build-dashboard-triage Skill
0★ repoSkill builder. Inspects your BI estate metadata, interviews whoever owns governance, then generates a custom /dashboard-triage skill that issues KEEP / MIGRATE / ARCHIVE verdicts with evidence. Use when dashboard sprawl has made self-serve impossible, before a migration, or when nobody can say which of your 140+ dashboards actually matter.
NorthStar-Analytics-LTD/skill-foundry/skills/build-support-triage Skill
0★ repoSkill builder. Maps your support channel, routing structure and escalation paths, then generates a custom /support-triage skill that acts as the first responder in your analytics support channel — classifying incoming questions, attempting first-line diagnosis, routing to the right owner and drafting the reply. Use when your data team's best people spend their days as a service desk, answering 10–30 messages a day.
nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-incident/.claude/skills/incident-response Skill
0★ repoLive incident protocol when production is impacted — triage blast radius and "what changed", mitigate first (rollback / flag / failover), preserve evidence before state-destroying actions, keep a timestamped timeline, diagnose production-safely, fix through normal gates, verify with a monitoring window. Use the moment production impact (users, data, money, security) is detected or imminent; not for ordinary bugs.
nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-lift/.claude/skills/root-cause-debug Skill
0★ repoSystematic root-cause debugging — reset to clean state, exact reproduction, full-evidence reading, differential hypotheses with discriminating experiments, fix at the cause, before/after proof. Use when a bug survives the first fix attempt, when behavior seems impossible or "weird", or before fixing anything you cannot yet explain.
fevra-dev/Subrosa/skills/redact Skill
0★ repoSanitizes documents, text, and code by detecting and removing or masking personally identifiable information (PII) and sensitive data before sharing, logging, or passing to external APIs. Use when user says "redact", "sanitize", "anonymize", "remove PII", "scrub this", "clean this before I share it", "hide personal info", or uploads a file they want checked for sensitive data. Also triggers on requests to prepare content for external use, bug reports, logs, or pastes that may contain credentials, wallet addresses, or personal identifiers.
supermodo/skills/skills/tdd Skill
0★ repoTest-driven work in two modes. Default: real Test-Driven Development — red-green-refactor, one failing test at a time, used while implementing features (and by the work skill). With --debug: test-first debugging — generate all plausible root-cause hypotheses, write tests to validate each before touching production code, fix based on which tests fail, then sweep the codebase for the same pattern. Use for 'tdd', 'test-driven', 'write the test first', implementing with tests leading — and with --debug whenever the user reports a bug, unexpected behavior, or failed fix attempts and the root cause is unclear.
theinterneti/TTA.dev/.claude/skills/gitnexus/gitnexus-debugging Skill
0★ repoUse when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
The same file is in 5 other repositories
songsunny00/MySkills/CoderSkills/.agents/skills/systematic-debugging Skill
no license0★ repoUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
The same file is in 30 other repositories
jovd83/junit5-skill/documentation/root_cause Skill
0★ repoUse when Codex needs to analyze a failing JUnit 5 test run, identify the most likely root cause, and produce a developer-focused diagnosis with concrete next fixes.
planifest/planifest-framework/planifest-framework/external-skills/api-error-handling Skill
0★ repoAPI failure-contract design for status mapping, stable error codes, retryability semantics, and traceable error payloads across sync and async transports. Trigger when error behavior, retry semantics, or debuggability fields change in specs or source, or when those rules remain implicit. Do not use for full resource/schema modeling or version-channel policy definition.
planifest/planifest-framework/planifest-framework/external-skills/debug-root-cause Skill
0★ repoSystematic debugging workflow for isolating software root causes, implementing proportional fixes, and verifying recovery with reproducible evidence. Use when application/runtime failures, regressions, or flaky behavior are observed and the task requires both diagnosis and remediation. When specialized skills are available in the environment, defer GitHub Actions failure triage to `github-fix-ci`, commit-introduction isolation to `git-bisect-debugging`, profiler-led hotspot analysis to `performance-profiling`, active security incident command to `security-incident-response`, and postmortem-only reporting to `incident-postmortem`. Do not use for broad feature implementation or speculative hardening without evidence.
planifest/planifest-framework/planifest-framework/external-skills/debugging-and-error-recovery Skill
0★ repoGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
The same file is in 10 other repositories