agentsclimarketplace

Debug & triage

5,150 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

  • Root cause analysis

    Noorkhalel/saas-ai-skills/skills/root-cause-analysis Skill

    2★ repo

    Produce a systemic, evidence-based incident RCA/postmortem after a failure: timeline, causal chain, contributing conditions, corrective actions, and prevention. Use when recurrence prevention and organizational learning are primary. Do not use as a generic live debugger.

  • Build and run

    matejformanek/postgres-claude/.claude/skills/build-and-run Skill

    2★ repo

    Build, install, initdb, and start PostgreSQL from source in the `dev/` clone for backend hacking — covers meson setup (PG ≥ 16 default) with cassert + debug flags, the autoconf ./configure fallback, ninja install, initdb + pg_ctl start / stop, PGDATA / PATH wiring, single-user mode for postmaster startup debugging, attaching gdb / lldb under the per-connection fork model, and -O0 -g3 debug builds. Use whenever a task involves compiling PG from source in dev/, running ninja install on the dev clone, initdb-ing a fresh data directory, starting or stopping the dev cluster via pg_ctl, picking between the debug profile (5432) and ASan profile (5433), or attaching a debugger to a forked backend. Skip for brew / apt / yum / Docker / k8s installation of release PG, Aurora / Cloud SQL / Supabase / Neon-managed PG provisioning, generic CMake / make / Bazel build questions, Linux-kernel builds, Node.js / Python / Go application builds, and pgAdmin / DBeaver client installation.

  • Debugging

    matejformanek/postgres-claude/.claude/skills/debugging Skill

    2★ repo

    Debug a running PostgreSQL backend with lldb / gdb — covers attaching to the right forked backend via pg_backend_pid, single-user mode for postmaster / InitPostgres startup paths, breakpoints in ExecInitNode / heap_update / LWLockAcquire, elog(LOG, ...) printf-debugging, macOS / Linux core-dump configuration, and SQL-level inspection via pg_buffercache / pageinspect / pg_visibility. Use whenever the user wants to step through backend C code, attach lldb / gdb to a specific dev-cluster backend, chase a SIGSEGV / hang / loop / assertion-failure in PG, instrument with elog, inspect shmem / buffer / lock state at runtime, or read a PG core dump. Skip for app-level debugging in Node.js / Python / Ruby / Go / Rust (use language-specific debuggers), JVM hprof / jstack, browser DevTools, Chrome Tracing, application performance profiling, and production PG tuning (autovacuum / shared_buffers — that's DBA work).

  • Error handling

    matejformanek/postgres-claude/.claude/skills/error-handling Skill

    2★ repo

    Write or review a PostgreSQL backend ereport / elog call — covers ereport vs elog, picking a SQLSTATE from errcodes.txt, errcode_for_file_access, errmsg / errdetail / errhint capitalisation rules, soft errors via escontext, PG_TRY / PG_CATCH longjmp-safe cleanup blocks, and the DEBUG / LOG / NOTICE / WARNING / ERROR / FATAL / PANIC elevel ladder. Use whenever a PG patch adds, edits, or reviews C in source/src/backend or contrib/ that reports an error or logs a message — picking elevel, choosing a SQLSTATE, formatting errmsg, wiring PG_TRY/PG_CATCH around a longjmp-unsafe block, or migrating a call to soft-error style. Skip for Python try/except, Go error returns, Rust Result / anyhow / thiserror, C++ exceptions, Java checked exceptions, Sentry / pino / Winston / log4j application logging, Oracle ORA-* / MySQL error codes, and general error-handling philosophy questions.

  • Psql

    matejformanek/postgres-claude/.claude/skills/psql Skill

    2★ repo

    Drive `psql` against the LOCAL dev cluster built from source in this workspace (Unix socket `/tmp`, trust auth, db `postgres`, ports 5432 debug / 5433 asan). Covers the connection idiom, high-yield meta-commands (`\d+`, `\df+`, `\sf`, `\timing`, `\watch`, `\gexec`, `\errverbose`), session-only debug GUCs (`client_min_messages`, `log_min_messages`, `EXPLAIN (ANALYZE, BUFFERS, WAL)`, `enable_seqscan`/`enable_hashjoin`/etc.), runtime introspection of *this* postmaster (`pg_stat_activity`, `pg_backend_memory_contexts`, `pg_locks`, `pg_log_backend_memory_contexts`), the held-PID handoff to lldb (`PGAPPNAME=hold` + `pg_sleep`), and what's safe vs not on a disposable dev cluster. **Use this skill proactively whenever the user wants to run SQL interactively or by script against the locally-built Postgres, reproduce a backend bug on the dev cluster, watch a backend's memory contexts grow, capture a backend PID for the debugger, force a specific plan shape via `SET enable_*`, run `EXPLAIN ANALYZE` against the dev DB, time a query with `\timing`, get the connection string for the dev cluster, or do any psql-driven exploration of an internals-flavored question — even when the user doesn't say the word "psql".** Skip for: questions about production / managed PostgreSQL instances at someone else's company; SQL written for app frameworks (Django/Rails/SQLAlchemy/Prisma/JDBC ORM/`models.py`/migration files); pure "how does pg_class / OID work" catalog-structure questions (use `catalog-conventions`); subsystem-internals questions answered from source code (cost_hashjoin, XLogInsert, deadlock detector, LWLock — use `executor-and-planner` / `wal-and-xlog` / `locking`); first-time build-from-source or start/stop lifecycle (use `build-and-run`); lldb/gdb stepping itself, single-user mode, sanitizer setup (use `debugging`); and one-shot read-only agent queries that should go through the `postgres-dev` MCP at `.mcp.json` instead of psql.

  • Morning bd triage

    cleatai/agent-skills/skills/morning-bd-triage Skill

    2★ repo

    Triage overnight government contract opportunities in CLEATUS. Pull AI-ranked recommendations, qualify by fit, add winners to the pipeline with a rationale, and flag near deadlines. Run every weekday morning.

  • Optimization

    Growth-Today/claude-skills/gt-linkedin-ads/.claude/skills/optimization Skill

    2★ repo

    Troubleshoot and optimize LinkedIn Ads campaigns for better performance. Use when the user asks about LinkedIn ads not working, low CTR, high CPL, creative fatigue, LinkedIn ads troubleshooting, campaign optimization, LinkedIn ads performance issues, or competitive research. Triggers on "LinkedIn ads not working", "low CTR", "high CPL", "creative fatigue", "optimize LinkedIn ads", "troubleshoot LinkedIn", "ads underperforming", "competitive research", "LinkedIn Ads Library". Do NOT use for initial campaign setup (use campaign-setup) or audience building (use audiences).

  • Opencode troubleshooting

    Timmy6942025/opencode-builder-skill/skills/opencode-troubleshooting Skill

    2★ repo

    Use this skill when diagnosing and resolving issues with OpenCode Desktop or CLI. Covers log inspection, storage locations, desktop app troubleshooting (plugins, cache, server connection, Wayland/X11, WebView2, notifications, storage reset), common errors (startup failures, authentication, model not found, ProviderInitError, AI_APICallError, copy/paste on Linux), and CLI debugging tools. Trigger on: troubleshooting, debugging, logs, won't start, error, crash, blank screen, connection failed, provider error, auth error, copy paste linux.

  • Systematic debugging

    WhiteMuush/Your-Claude-DevOps-Teacher/skills/systematic-debugging Skill

    no license2★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 8 other repositories

  • Triage validation

    Mikacr1138/claude-bug-bounty/skills/triage-validation Skill

    2★ repo

    Finding validation before writing any report — 7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist. Use BEFORE writing any report. One wrong answer = kill the finding and move on. Saves N/A ratio.

  • Debug

    nicodiansk/turbocharge/skills/debug Skill

    2★ repo

    Use when encountering any bug, test failure, or unexpected behavior. Enforces systematic root-cause investigation before proposing fixes. Prevents guess-and-check debugging.

  • Org health diagnostic

    OpenSIN-AI/OpenSIN-Skills/c-level-advisor/org-health-diagnostic Skill

    no license2★ repo

    Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.

    The same file is in 1 other repository

  • Analytics tracking

    OpenSIN-AI/OpenSIN-Skills/marketing-skill/analytics-tracking Skill

    no license2★ repo

    Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.

    The same file is in 1 other repository

  • Enterprise deep debug

    OpenSIN-AI/OpenSIN-Skills/operations/planning/enterprise-deep-debug Skill

    no license2★ repo

    Ultimate enterprise debugging workflow: facts-first RCA, cross-tool intent discovery, parallel subagents, web validation, minimal safe fix, and persistent knowledge flush.

  • Learn

    WhatIfWeDigDeeper/agent-skills/skills/learn Skill

    2★ repo

    My Agent Skills I've created for Claude Code and can, in principle, be used with other coding assistants

  • Span of control diagnostic

    trycomp-io/comp-skills/skills/span-of-control-diagnostic Skill

    2★ repo

    Diagnóstico de Span of Intelligence, evolução do span of control tradicional. Lê CSV/XLSX da org (employee, manager, opcionalmente ai_agents + automation_pct) e gera relatório HTML com classificação dos gestores em Tradicional / Híbrido / Orquestração / Subutilizado / Sobrecarregado-sem-IA. Recomendações reframed (em vez de "quebre time grande", sugere "automatize ou senior-ize"). Baseado no artigo Comp na Cajuína. Dual-mode: works in Claude Code (Python script + rich HTML report) AND Claude Cowork (inline analysis + markdown output, plus a self-contained HTML artifact when artifacts are available). Trigger em "span of control", "span of intelligence", "diagnóstico organizacional", "análise de org", "estrutura organizacional", "camadas", "manager-to-IC ratio", "layers". Mantida pela Comp.

  • Mcmc debugger

    rudrathegreat/Astronomy-AI-Toolkit/skills/inference/emcee/mcmc_debugger Skill

    no license2★ repo

    A catered AI toolkit for astronomers

  • Enterprise debugger

    rudrathegreat/Astronomy-AI-Toolkit/skills/inference/enterprise/enterprise_debugger Skill

    no license2★ repo

    A catered AI toolkit for astronomers

  • Systematic troubleshooting

    jeonnoin-alt/Eureka/skills/systematic-troubleshooting Skill

    2★ repo

    Use when experiments produce unexpected results, analyses fail, or findings contradict expectations — before proposing explanations or re-running

  • Performance optimization

    rampstackco/claude-skills-starter/skills/performance-optimization Skill

    2★ repo

    Diagnose and fix web performance issues including Core Web Vitals (LCP, INP, CLS), bundle size, asset optimization, render performance, and runtime efficiency. Use this skill whenever the user wants to improve page speed, fix Core Web Vitals, optimize assets, reduce bundle size, debug slow renders, or systematically improve a site's performance. Triggers on performance, page speed, Core Web Vitals, LCP, INP, CLS, FID, TTFB, bundle size, code splitting, image optimization, lazy loading, render blocking, slow page, performance audit, Lighthouse score. Also triggers when traffic or conversion is dropping due to perceived slowness.

    The same file is in 1 other repository

  • Debug

    christyjacob4/claude-tricks/skills/debug Skill

    2★ repo

    Debug and fix failing tests or errors

  • Investigate

    christyjacob4/claude-tricks/skills/investigate Skill

    2★ repo

    Deep investigation of bugs, performance issues, or unexpected behavior. TRIGGER THIS SKILL when users report bugs, errors, performance regressions, unexpected behavior, or ask to investigate, debug, diagnose, or find the root cause of any issue — whether they say "why is this broken", "investigate this bug", "find the root cause", "debug this issue", "this is failing and I don't know why", "performance degraded", or share error messages and stack traces. Do NOT trigger for feature requests, code reviews, refactoring, or general code questions.

  • Bug report writer

    ShreyasBh02/AI-Skills-Collection/bug-report-writer Skill

    no license2★ repo

    Converts rough notes, casual descriptions, console errors, or quick observations into professional, complete bug reports — exported as a formatted Excel (.xlsx) file ready for Excel, Google Sheets, Jira, or Azure DevOps. Use this skill whenever the user mentions: "write a bug report", "log a bug", "report this issue", "found a defect", "something is broken", "create a bug ticket", "fill bug report", "document this bug", "file a ticket", "issue log", "defect report", "bug tracker", "something's wrong with", or pastes rough notes, console errors, or stack traces about unexpected behavior. Always trigger even for vague inputs like "the button doesn't work" or "this is broken" — the skill will infer details via smart assumptions and produce a professional output regardless. Trigger for single bugs AND multiple bugs described in one message.

  • Log to bug report converter

    ShreyasBh02/AI-Skills-Collection/log-to-bug-report-converter Skill

    no license2★ repo

    Parses error logs, stack traces, and test failures into production-ready bug reports.

  • Speckit.debug

    wedabro/bro-skills/.agent/skills/speckit.debug Skill

    2★ repo

    Systematic Debugger - Diagnose problems, find individual root causes, and recommend fix plans.

  • Speckit.debug

    wedabro/bro-skills/.agents/skills/speckit.debug Skill

    2★ repo

    Systematic Debugger - Diagnose problems, find individual root causes, and recommend fix plans.

  • Triage board

    mostafa-drz/claude-skills/code/triage-board Skill

    2★ repo

    Generates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown" action that produces a GitHub/Linear/Notion-ready ticket block. Stateless — triage state lives in the user's ticket system, not in the viewer. Use after a beginner-mind audit, QA exploration, code review, or any session where the user accumulated discrete findings worth handing off. Triggers: "generate test report", "create triage doc", "extract findings", "export this audit", "make a viewer", "save findings for review".

  • Obs guardian

    mturac/hermes-supercode-skills/skills/obs-guardian Skill

    2★ repo

    Builds observability, monitoring, alerting, and incident visibility for production systems. Covers OpenTelemetry instrumentation for traces, metrics, and logs; structured logging with JSON, correlation IDs, and sampling; Prometheus and Grafana scrape configs, dashboards, and recording rules; distributed tracing with Jaeger and Tempo; SLO/SLA definition, error budgets, burn-rate alerts; PagerDuty and OpsGenie alerting rules; and on-call runbook templates. Use this skill when the user says "set up monitoring," "instrument with OpenTelemetry," "add structured logging," "set up Grafana dashboards," "define SLOs," "no visibility into my app," "tracing across microservices," "alerting rules," or "production incident with no logs."

  • Quantum debugger

    mturac/hermes-supercode-skills/skills/quantum-debugger Skill

    2★ repo

    Debugs complex, hard-to-reproduce issues: race conditions, memory leaks, deadlocks, performance regressions, heisenbugs, and crash analysis. Uses scientific debugging methodology with hypothesis generation, systematic testing, and root cause isolation. Use this skill when the user reports intermittent crashes, performance degradation, memory leaks, thread-safety issues, deadlocks, or any bug that's hard to reproduce. Also triggers on "debug this," "why is this crashing," "performance regression," "memory leak," "race condition," "segfault," "service hangs intermittently," or even "this works on my machine but not in production."

  • Root cause debugging

    yuchi-chang/no-cape/skills/root-cause-debugging Skill

    no license2★ repo

    Use when encountering a bug, test failure, regression, flaky test, or unexpected behavior — before proposing or applying any fix

  • Start

    psenger/catholic-ai-skills/.claude/skills/start Skill

    2★ repo

    Begins a new piece of work in the ai-agent-skills repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL — fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing — classifies as feature or bug, drafts a structured requirement using the repo's issue template, confirms with the user, creates the GitHub issue, then cuts the branch). Always checks GitHub auth first and confirms user identity. Use when the user says "start work on #14", "begin issue", "start a new feature", "I need to build X", "create an issue for Y", or passes a GitHub issue URL. Load the `conventions` skill for branch naming rules.

  • Debug rules

    stuartshields/claude-setup/skills/debug-rules Skill

    2★ repo

    Diagnose which rules loaded, which didn't, and why. Reads the InstructionsLoaded audit log and compares against expected rules.

  • Debug wp

    stuartshields/claude-setup/skills/debug-wp Skill

    2★ repo

    Starts a structured interview to diagnose WordPress issues, then proposes a ranked list of solutions.

  • Debugging

    stuartshields/claude-setup/skills/debugging Skill

    2★ repo

    Structured debugging protocol. Use when investigating a bug, failing test, regression, unexpected behavior, or any scenario where code is not doing what it should. Trigger phrases include "broken", "not working", "bug", "error", "it worked before", "still broken", "why is this failing", "trace", or "/trace".

  • Issue triage

    risadams/skills/issue-triage Skill

    no license2★ repo

    Triage a bug or issue by gathering context (Jira ticket or free-form description), mapping the suspected code area via codebase-explain, hypothesizing root causes via clarity-council, and producing a structured triage report with ranked root-cause candidates and proposed solution paths. Read-only by default; the user may opt in at the end to publish the report as a Jira comment. Use when user says "triage this", "triage [TICKET-KEY]", "what's causing this bug", "help me find the root cause", or invokes /issue-triage with a ticket key or issue description.

  • Nestjs error handling

    FilippoDeSilva/skills/skills/nestjs/nestjs-error-handling Skill

    no license2★ repo

    Implement Global Exception Filters and standard error formats in NestJS. Use when implementing global exception filters or standardizing error responses in NestJS.

  • Nestjs observability

    FilippoDeSilva/skills/skills/nestjs/nestjs-observability Skill

    no license2★ repo

    Configure structured logging with Pino, Prometheus metrics, and health checks for NestJS services. Use when adding JSON logging, request tracing with correlation IDs, Prometheus metric endpoints, or liveness/readiness health checks.

  • Datadog

    fworks-tech/agenthood/skills/datadog Skill

    2★ repo

    Monitor infrastructure and applications via Datadog API and CLI. Use when querying metrics, logs, or managing monitors.

  • Debugging and error recovery

    fworks-tech/agenthood/skills/debugging-and-error-recovery Skill

    2★ repo

    Diagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior.

  • Sentry

    fworks-tech/agenthood/skills/sentry Skill

    2★ repo

    Monitor and debug application errors via the Sentry CLI. Use when triaging production errors or managing releases.

  • The debugger

    fworks-tech/agenthood/skills/the-debugger Skill

    2★ repo

    Diagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior. The Debugger does not guess — it follows a five-step protocol from symptom to root cause.

  • Cisco device health

    vahagn-madatyan/netsec-skills-suite/skills/cisco-device-health Skill

    2★ repo

    Cisco IOS-XE and NX-OS device health check and triage procedure. Use when troubleshooting Cisco routers, switches, or Nexus platforms — assessing CPU, memory, interfaces, routing, and environment. Covers both IOS-XE (ISR, ASR, Catalyst 9K) and NX-OS (Nexus 3K/5K/7K/9K) with platform-specific commands, thresholds, and decision trees that account for IOS-XE QFP/RP architecture and NX-OS VDC isolation.

  • Example device health

    vahagn-madatyan/netsec-skills-suite/skills/example-device-health Skill

    2★ repo

    Cisco IOS-XE device health check and triage procedure. Use when troubleshooting Cisco IOS-XE routers or switches, checking CPU utilization, memory usage, interface error counters, routing table health, or performing rapid device triage during an outage. Covers show commands, threshold interpretation, escalation decision trees, and structured report output for handoff.

  • Incident response lifecycle

    vahagn-madatyan/netsec-skills-suite/skills/incident-response-lifecycle Skill

    2★ repo

    Incident response process management following the NIST 800-61 lifecycle. Covers severity classification, escalation matrices, role assignment, communication management, phased recovery coordination, blameless post-mortem facilitation, and 5-whys root cause analysis. Scoped to the process and coordination layer — for network-level evidence collection and forensic analysis, use incident-response-network instead.

    The same file is in 1 other repository

  • Juniper device health

    vahagn-madatyan/netsec-skills-suite/skills/juniper-device-health Skill

    2★ repo

    Juniper JunOS device health check and triage procedure. Use when troubleshooting Juniper MX, SRX, EX, QFX, or PTX platforms — assessing Routing Engine health, Packet Forwarding Engine state, chassis alarms, system resources, and environment. Covers dual-RE failover detection, alarm severity triage, PFE statistics analysis, and commit-correlated diagnostics. Procedure begins with RE mastership verification — health data from the wrong RE produces incorrect assessments.

  • Network log analysis

    vahagn-madatyan/netsec-skills-suite/skills/network-log-analysis Skill

    2★ repo

    Device-level network log analysis using raw syslog data without SIEM platforms. Guides forensic timeline construction from rsyslog/syslog-ng collectors, device console logs, and SNMP trap data. Covers syslog pattern recognition across Cisco IOS-XE, Juniper JunOS, and Arista EOS message formats, multi-device event correlation using grep/awk/sort, anomaly detection via baseline deviation, and chronological timeline reconstruction with NTP-aware timestamp normalization.

  • Siem log analysis

    vahagn-madatyan/netsec-skills-suite/skills/siem-log-analysis Skill

    2★ repo

    Network-security-focused SIEM log analysis across Splunk, ELK, and QRadar platforms. Guides forensic timeline construction from network device syslog events — firewall denies, authentication failures, configuration changes, interface events, VPN tunnel state, and lateral movement indicators. Provides platform-independent diagnostic reasoning with platform-specific query syntax using [Splunk]/[ELK]/[QRadar] inline labels.

  • Vpn ipsec troubleshooting

    vahagn-madatyan/netsec-skills-suite/skills/vpn-ipsec-troubleshooting Skill

    2★ repo

    IPSec/IKE VPN troubleshooting with IKE state machine diagnosis, crypto parameter verification, and tunnel health assessment. Multi-vendor coverage for Cisco IOS-XE, Juniper JunOS, Palo Alto PAN-OS, and FortiGate FortiOS with FSM-driven diagnostic reasoning.

  • Animation principles troubleshooting

    t4sh/dotfiles/agents/skills/animation-principles-troubleshooting Skill

    no license2★ repo

    Use when animation feels wrong and you need to diagnose which principle is failing or being misapplied

  • Debug

    t4sh/dotfiles/agents/skills/debug Skill

    no license2★ repo

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    The same file is in 3 other repositories

  • Diagnosing bugs

    t4sh/dotfiles/agents/skills/diagnosing-bugs Skill

    no license2★ repo

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    The same file is in 17 other repositories

  • Implementation debugging

    t4sh/dotfiles/agents/skills/implementation-debugging Skill

    no license2★ repo

    Use when animation doesn't work as expected, has bugs, or behaves inconsistently

  • Problem diagnosis

    t4sh/dotfiles/agents/skills/problem-diagnosis Skill

    no license2★ repo

    Use when animation "feels wrong" but you can't pinpoint why—debugging floaty movement, stiff characters, unclear action, or any motion that isn't working and needs systematic troubleshooting.

  • Systematic debugging

    t4sh/dotfiles/agents/skills/systematic-debugging Skill

    no license2★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 8 other repositories

  • Triage

    t4sh/dotfiles/agents/skills/triage Skill

    no license2★ repo

    Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

    The same file is in 13 other repositories

  • Stack istack

    nanxiaoyao/network-huawei-skills/stack-istack Skill

    2★ repo

    This skill should be used when the user asks to configure or troubleshoot Huawei S-series switch stacking (iStack). Covers stack establishment via stack-port or service-port mode, master/slave/standby election, member join/leave, dual-active detection (DAD/MAD), stack split & merge, in-service upgrade, and stack troubleshooting. Applicable platforms S/CE switches: S1720/S2700/S5700/S6720 V200R011C10+ (iStack) and CloudEngine 5800-9800 V200R022C00+ (Stack).

  • Observability modeling

    jacob-balslev/skills/skills/data-engineering/observability-modeling Skill

    2★ repo

    Use when designing telemetry semantics before or during implementation: logs, metrics, traces, events, spans, attributes, correlation IDs, SLOs, alert signals, and diagnostic questions. Do NOT use for domain/business event contracts (use `event-contract-design`), configuring an error tracker alone (use `error-tracking`), performance optimization (use `performance-engineering`), or debugging a current incident (use `debugging`).

  • Lint overlay

    jacob-balslev/skills/skills/quality-assurance/lint-overlay Skill

    2★ repo

    Use when adding or enforcing lint rules as part of a test or verification plan. Extends testing-strategy with lint-specific guidance: rule selection, gate placement, failure triage, and migration planning when introducing rules to an existing codebase. Do NOT use standalone — load the base testing-strategy skill alongside it — and do NOT use for chasing a specific lint failure in one file (that is debugging).

  • Secrets management

    jacob-balslev/skills/skills/quality-assurance/secrets-management Skill

    2★ repo

    Managing the full lifecycle of sensitive credentials — API keys, database passwords, tokens, certificates, signing keys, and encryption keys — so they are never exposed in code, logs, images, or version history. Covers the secret lifecycle (generation, storage, distribution, use, rotation, revocation, audit), the cardinal rule of never hardcoding secrets, externalizing values out of source into a secrets manager or vault, encryption at rest and in transit, least-privilege scoping per consumer, short-lived dynamically-issued credentials over long-lived static ones, automated rotation and emergency revocation, workload identity (OIDC/SPIFFE) to eliminate standing credentials, environment-variable and .env pitfalls, secret scanning and leak detection in commits and CI, blast-radius containment when a secret leaks, and audit logging of secret access. Tool-agnostic across HashiCorp Vault, cloud secret managers, and KMS-backed stores.

  • Debugging

    jacob-balslev/skills/skills/software-engineering-method/debugging Skill

    2★ repo

    Use when behavior is broken, a test is failing, or runtime output contradicts expectations. Covers failure reproduction, scope reduction by bisection, evidence capture at the moment of failure, root-cause isolation (not symptom patching), fix verification against the same evidence path, and regression-test creation. Do NOT use for feature planning, architectural design, or behavior-preserving refactor.