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

  • Systematic debugging

    oscarqjh/super-agent-skills/plugins/super-agent-skills/skills/systematic-debugging Skill

    no license2★ repo

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

  • Debugging and error recovery

    vignesh2027/AI-AGENT-SKILLS/skills/debugging-and-error-recovery Skill

    2★ repo

    Systematic root-cause analysis — stop guessing, start isolating

  • Debug

    jvalin17/agent-toolkit/skills/debug Skill

    2★ repo

    Systematic debugging when something is broken. Diagnose by layer, hypothesis-driven, reproduce with test, then fix. Keywords: debug, broken, not working, bug, crash, fix, error, failing, blank page, 0 results, silent failure

  • Fix first then test

    AllanWessels/Bratan/docs/build-skills/fix-first-then-test Skill

    no license2★ repo

    Land every code fix before running the test harness. Use grep + read to debug; the harness is a verifier, not a debugger.

  • Debug

    bonnguyenitc/specship/skills/debug Skill

    2★ repo

    Diagnose and fix a bug methodically, and track the investigation in the owning task. Use when something is broken, a test fails, behavior is wrong, or asked to "debug X", "fix this bug", "why is this failing". Reproduces, finds root cause, fixes minimally, verifies, and records it in tasks/TASK-<ID>/debug.md. Attaches to the spec → plan → coding → review workflow whenever a defect appears.

  • Generalupdate troubleshoot

    GeneralLibrary/generalupdate-skill-codegen/.claude/skills/generalupdate-troubleshoot Skill

    2★ repo

    Complete diagnostic reference for ALL known GeneralUpdate issues — powered by 50+ real GitHub/Gitee issues and full code audit findings (17 critical/high + 14 medium + 10 low). Covers: install failures, dual-process issues, IPC corruption, OSS failures, silent mode bugs, differential patch errors, cross-version (CVP) problems, Bowl crash daemon, SignalR push, file system issues, version comparison, cross-tenant leakage, and AOT compatibility. Provides root causes, fixes, workarounds, and a 6-step universal diagnostic workflow. Triggers on: "update failed", "not working", "error", "bug", "crash", "exception", "升级失败", "失败", "报错", "不行", "不工作", "没反应", "问题", "排查", "method not found", "file locked", "path too long", "Chinese garbled", "乱码", "version incorrect", "版本不对", "infinite loop", "死循环", "bowl not working", "push not working", "signalr error", "IPC error", "AOT trim", "跨租户", "权限", "permission denied", "access denied", "silent mode", "静默", "差分", "增量". Load this skill AUTOMATICALLY when user reports any error, unexpected behavior, or failure symptom — run the diagnostic workflow before escalating.

  • Generalupdate skill codegen

    GeneralLibrary/generalupdate-skill-codegen Skill

    2★

    Complete Claude Code skill suite for integrating GeneralUpdate (.NET auto-update) into any .NET application — desktop (WPF/WinForms/Avalonia/MAUI/console) and mobile (Avalonia.Android/MAUI.Android). Generates dual-project scaffolding (Client+Upgrade), Bootstrap configuration (4 methods), full-state update UI (6 frameworks), 6 strategy implementations (Client-Server/OSS/Silent/Differential/CVP/Push), advanced extension points (IPC replacement, Bowl crash daemon, custom Hooks, AOT), mobile auto-update integration (3-step Avalonia / 2-step MAUI + FileProvider), and deep troubleshooting (50+ known issues). All templates target NuGet v10.5.0-rc.1 API. Triggers on: "GeneralUpdate", "auto update", "自动更新", "update framework", ".NET update", "Claude Code skill suite", "GeneralUpdate Skill CodeGen", "generalupdate-init", "generalupdate-ui", "generalupdate-strategy", "generalupdate-advanced", "generalupdate-troubleshoot", "generalupdate-migration", "generalupdate-security-audit", "generalupdate-mobile", "集成GeneralUpdate", "接入自动更新", "更新技能", "升级框架", ".NET自动更新", "双进程更新", "Bootstrap配置", "WPF update", "Avalonia update", "MAUI update", "WinForms update", "差分更新", "静默更新", "跨版本更新", "OSS更新", "推送更新", "Bowl崩溃守护", "IPC通讯", "NamedPipe", "更新UI界面", "update troubleshooting", "更新失败排查", "升级报错", "GeneralUpdate.Avalonia", "GeneralUpdate.Maui", "Avalonia update", "MAUI update", "Android update", "移动端更新", "安卓更新", "Avalonia自动更新", "MAUI自动更新", "Android自动更新", "mobile auto update", "Avalonia Android update", "MAUI Android update", "集成移动端更新", "接入安卓自动更新", "APK update". Also triggers on common .NET + update combinations. Contains 8 sub-skills: - generalupdate-init: Dual-project scaffolding + Bootstrap config - generalupdate-ui: Full-state update UI for 6 frameworks - generalupdate-strategy: 6 strategy decision tree + examples - generalupdate-advanced: 10+ extension points + Bowl + IPC + AOT - generalupdate-troubleshoot: 50+ known issues diagnosis - generalupdate-migration: v9.x → v10 / dev-branch → stable migration - generalupdate-security-audit: Security audit for update pipeline - generalupdate-mobile: Mobile auto-update for Avalonia.Android & MAUI.Android apps

  • Generalupdate troubleshoot

    GeneralLibrary/generalupdate-skill-codegen/cli/assets/skills/generalupdate-troubleshoot Skill

    2★ repo

    Complete diagnostic reference for ALL known GeneralUpdate issues — powered by 50+ real GitHub/Gitee issues and full code audit findings (17 critical/high + 14 medium + 10 low). Covers: install failures, dual-process issues, IPC corruption, OSS failures, silent mode bugs, differential patch errors, cross-version (CVP) problems, Bowl crash daemon, SignalR push, file system issues, version comparison, cross-tenant leakage, and AOT compatibility. Provides root causes, fixes, workarounds, and a 6-step universal diagnostic workflow. Triggers on: "update failed", "not working", "error", "bug", "crash", "exception", "升级失败", "失败", "报错", "不行", "不工作", "没反应", "问题", "排查", "method not found", "file locked", "path too long", "Chinese garbled", "乱码", "version incorrect", "版本不对", "infinite loop", "死循环", "bowl not working", "push not working", "signalr error", "IPC error", "AOT trim", "跨租户", "权限", "permission denied", "access denied", "silent mode", "静默", "差分", "增量". Load this skill AUTOMATICALLY when user reports any error, unexpected behavior, or failure symptom — run the diagnostic workflow before escalating.

  • Wrong number debugging

    lancegui/causal-powers/skills/wrong-number-debugging Skill

    2★ repo

    Use the moment a computed result looks wrong, surprising, suspicious, or "off" — a total that doesn't reconcile, revenue that tripled after a join, a mean that moved, a coefficient with the wrong sign, a count that's too high or too low, a metric that disagrees with another team's. Bisects the data pipeline to find the exact step where the number went bad, tracing provenance backward instead of guessing-and-patching. Use whenever the user says "this number looks wrong", "why is this so high", "these don't match", "the totals are off", "that can't be right", or when a `data-contracts` reconciliation fails — in R, Julia, Python, or Stata.

  • Error handling

    kimtth/agent-skill-100-lines-or-less/skills/error-handling Skill

    no license2★ repo

    Use when: design error handling so failures are explicit, recoverable, and never silently swallowed.

  • Git bisect

    kimtth/agent-skill-100-lines-or-less/skills/git-bisect Skill

    no license2★ repo

    Use when: find the commit that introduced a bug with a binary search over history.

  • Structured logging

    kimtth/agent-skill-100-lines-or-less/skills/structured-logging Skill

    no license2★ repo

    Use when: emit structured, queryable logs with the right levels, context, and no sensitive data.

  • Systematic debugging

    kimtth/agent-skill-100-lines-or-less/skills/systematic-debugging Skill

    no license2★ repo

    Use when: a bug is unclear and you need a hypothesis-driven loop instead of random edits.

  • Postgres queue health

    zacharygcook/agent-skills/skills/postgres-queue-health Skill

    2★ repo

    Review and diagnose Postgres-backed job queues for MVCC dead tuples, index bloat, autovacuum lag, long transactions, claim-query performance, retention, and SKIP LOCKED safety. Use when implementing, debugging, reviewing, or scaling database queues and their dashboards.

  • Triage stale pull requests

    zacharygcook/agent-skills/skills/triage-stale-pull-requests Skill

    2★ repo

    A curated collection of practical, evidence-backed skills for coding agents.

  • Apify actor development

    Pyfagorass/bookofspells/skills/apify/apify-actor-development Skill

    no license2★ repo

    Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing. Use when creating new Actors, modifying existing ones, or troubleshooting Actor code.

  • Azure resource health diagnose

    Pyfagorass/bookofspells/skills/githubcopilot/azure-resource-health-diagnose Skill

    no license2★ repo

    Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.

  • Creating oracle to postgres migration bug report

    Pyfagorass/bookofspells/skills/githubcopilot/creating-oracle-to-postgres-migration-bug-report Skill

    no license2★ repo

    Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

  • Flowstudio power automate debug

    Pyfagorass/bookofspells/skills/githubcopilot/flowstudio-power-automate-debug Skill

    no license2★ repo

    Debug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-level inputs and outputs to find the actual root cause. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app

  • Flowstudio power automate monitoring

    Pyfagorass/bookofspells/skills/githubcopilot/flowstudio-power-automate-monitoring Skill

    no license2★ repo

    Pro+ subscription required. Tenant-wide Power Automate monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use flowstudio-power-automate-mcp, flowstudio-power-automate-debug, or the server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+.

  • Power bi performance troubleshooting

    Pyfagorass/bookofspells/skills/githubcopilot/power-bi-performance-troubleshooting Skill

    no license2★ repo

    Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.

  • Gcloud

    Pyfagorass/bookofspells/skills/google/gcloud Skill

    no license2★ repo

    Interacts with Google Cloud services using the gcloud CLI safely and efficiently. Covers command validation, data reduction, safety guardrails with a denylist, and workflows for discovery and investigation. You MUST read this skill before invoking any gcloud command. Use when managing cloud resources, querying configurations, or troubleshooting issues via gcloud. Don't use when writing or debugging Google Cloud client library code or raw REST/gRPC API interactions.

  • Gws gmail triage

    Pyfagorass/bookofspells/skills/gworkspace/gws-gmail-triage Skill

    no license2★ repo

    Gmail: Show unread inbox summary (sender, subject, date).

  • Diagnose

    Pyfagorass/bookofspells/skills/mattpocock/diagnose Skill

    no license2★ repo

    Disciplined 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.

  • Triage

    Pyfagorass/bookofspells/skills/mattpocock/triage Skill

    no license2★ repo

    Triage 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.

  • Azure compute

    Pyfagorass/bookofspells/skills/microsoft/azure-compute Skill

    no license2★ repo

    Azure VM and VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, capacity reservations, and Essential Machine Management. WHEN: Azure VM, VMSS, scale set, recommend, compare, server, website, burstable, lightweight, VM family, workload, GPU, learning, simulation, dev/test, backend, autoscale, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, connect, refused, Linux, black screen, reset password, reach VM, port 3389, NSG, troubleshoot, capacity reservation, CRG, reserve VMs, guarantee capacity, pre-provision capacity, CRG association, CRG disassociation, essential machine management, EMM, machine enrollment.

  • Azure diagnostics

    Pyfagorass/bookofspells/skills/microsoft/azure-diagnostics Skill

    no license2★ repo

    Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, service bus dead letter.

  • Azure messaging

    Pyfagorass/bookofspells/skills/microsoft/azure-messaging Skill

    no license2★ repo

    Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.

  • Analyze root cause

    Pyfagorass/bookofspells/skills/montecarlo/analyze-root-cause Skill

    no license2★ repo

    Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling. Activates when a user asks about data issues, incidents, alerts, or why data looks wrong.

  • Automated triage

    Pyfagorass/bookofspells/skills/montecarlo/automated-triage Skill

    no license2★ repo

    Triage Monte Carlo alerts interactively or build an automated workflow. Fetch, score, and troubleshoot alerts using MCP tools now, or design a reusable workflow that runs on a schedule.

  • Sentry

    Pyfagorass/bookofspells/skills/openai/sentry Skill

    no license2★ repo

    Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command.

  • Debugging

    Pyfagorass/bookofspells/skills/qdrant/debugging Skill

    no license2★ repo

    Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.

  • Debugging

    Pyfagorass/bookofspells/skills/qdrant/qdrant-monitoring/debugging Skill

    no license2★ repo

    Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.

  • Customer support command desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/customer-support-command-desk Skill

    2★ repo

    orchestrate customer support work across ticket intake and entitlement checks, triage and routing, severity and sla clocks, troubleshooting and diagnosis, reproduction and bug intake, engineering escalation, macro and response quality, resolution and closure, customer-facing incident communication and status page updates, post-incident follow-up and outage letters, knowledge base authoring, self-service deflection, queue and backlog health, workforce coverage and staffing, helpdesk tooling and automation, qa review and calibration, contact driver analysis, and support metrics reporting. use when a ticket needs triage or a severity, an sla is about to breach, a customer reports something nobody can reproduce, a bug needs filing to engineering, an escalation needs raising, a backlog is aging, csat or first response time is being explained, a macro or help center article needs writing, deflection is being measured, an outage needs customer comms and an outage letter, or staffing is being planned against forecast volume.

  • Diagnostic troubleshooting desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/diagnostic-troubleshooting-desk Skill

    2★ repo

    take a support symptom to a cause by carrying hypotheses with the observation that would confirm or eliminate each, building an evidence inventory from logs, traces, har captures, configuration exports, and diagnostic bundles with collection times and retention limits, separating product defect from configuration from integration from customer environment from expected behavior, and stating the cause at the confidence it was established. use for troubleshooting, log and trace analysis, known error matching, workarounds, and root cause isolation on a live ticket.

  • Severity sla desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/severity-sla-desk Skill

    2★ repo

    set support severity from customer impact and run every sla clock against the executed agreement, computing first response, next update, restoration, and resolution targets on the contractual calendar and timezone, pausing only under the written pause rule, and reporting the at-risk and breached position with the credit exposure behind it. use for severity assignment and disputes, sla target calculation, business-hours and follow-the-sun coverage, clock pauses on pending-customer, breach reporting, and service credit exposure.

  • Ticket triage desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/ticket-triage-desk Skill

    2★ repo

    route and order support tickets by naming the queue, tier, and skill each contact requires, setting priority from the ordering rule in force and keeping it distinct from contractual severity, identifying spam, duplicates, machine-generated tickets, and misrouted work with the evidence for each, and separating contacts a published answer already resolves from contacts that need diagnosis. use for queue assignment, tier escalation criteria, skill-based routing, priority disputes, bounce-back loops, and misrouting patterns worth fixing in the rules.

  • Contract intake triage desk

    MadewellRD/skills-lab/dist/skills/legal-contracts-command-desk/contract-intake-triage-desk Skill

    2★ repo

    triage inbound contract requests by classifying matter type, posture, and whose paper the draft arrived on, scoring the risk tier against the named triage rubric, selecting review lanes, checking the repository for an existing agreement over the same scope, and assigning legal owner and committed turnaround. use for new contract requests, nda queues, vendor onboarding packages, quote-to-contract intake, deal desk escalations, renewal intake, self-serve template deflection, and legal front door routing.

  • Intake triage desk

    MadewellRD/skills-lab/dist/skills/procurement-vendor-management-command-desk/intake-triage-desk Skill

    2★ repo

    triage a purchase requisition by classifying the need as a capability rather than a product name, checking duplicates and overlap against existing agreements and licensed tools, converting a monthly or per-seat quote into annual and total contract value including renewal terms, testing the urgency claim against what actually creates the date, and routing to the sourcing method risk path and lead time the request requires. use for new purchase requests, intake queues, duplicate tool checks, total contract value calculations, emergency purchase claims, and requests where a team has already signed or already told a supplier.

  • Ci failure desk

    MadewellRD/skills-lab/dist/skills/sdlc-command-desk/ci-failure-desk Skill

    2★ repo

    create connector-grounded ci/cd failure triage and pipeline-health artifacts for software delivery. use when the assistant needs to diagnose github actions or build failures, classify flaky tests, inspect logs and workflow runs, decide rerun versus fix, identify failing checks, map ci failures to code changes or infrastructure, or prepare downstream handoff notes for review-quality-desk, verification-desk, release-operations-desk, incident-response-desk, issue-planning-desk, or implementation-handoff-desk workflows.

  • Incident response desk

    MadewellRD/skills-lab/dist/skills/sdlc-command-desk/incident-response-desk Skill

    2★ repo

    create connector-grounded incident response, bug triage, severity classification, root cause analysis, hotfix handoff, follow-up issue, post-incident review, and production-support artifacts from incidents, alerts, logs, metrics, traces, recent deploys, github issues, pull requests, ci evidence, runbooks, and stakeholder updates. use when the assistant needs to triage a production failure, summarize an incident, draft an rca, plan a hotfix, map remediation work, or prepare downstream handoff notes for implementation-handoff-desk, ci-failure-desk, deployment-desk, observability-readiness-desk, release-operations-desk, verification-desk, or docs-traceability-desk workflows.

  • Customer support command desk

    MadewellRD/skills-lab/dist/vendor/anthropic/customer-support-command-desk/customer-support-command-desk Skill

    2★ repo

    orchestrate customer support work across ticket intake and entitlement checks, triage and routing, severity and sla clocks, troubleshooting and diagnosis, reproduction and bug intake, engineering escalation, macro and response quality, resolution and closure, customer-facing incident communication and status page updates, post-incident follow-up and outage letters, knowledge base authoring, self-service deflection, queue and backlog health, workforce coverage and staffing, helpdesk tooling and automation, qa review and calibration, contact driver analysis, and support metrics reporting. use when a ticket needs triage or a severity, an sla is about to breach, a customer reports something nobody can reproduce, a bug needs filing to engineering, an escalation needs raising, a backlog is aging, csat or first response time is being explained, a macro or help center article needs writing, deflection is being measured, an outage needs customer comms and an outage letter, or staffing is being planned against forecast volume.

  • Diagnostic troubleshooting desk

    MadewellRD/skills-lab/dist/vendor/anthropic/customer-support-command-desk/diagnostic-troubleshooting-desk Skill

    2★ repo

    take a support symptom to a cause by carrying hypotheses with the observation that would confirm or eliminate each, building an evidence inventory from logs, traces, har captures, configuration exports, and diagnostic bundles with collection times and retention limits, separating product defect from configuration from integration from customer environment from expected behavior, and stating the cause at the confidence it was established. use for troubleshooting, log and trace analysis, known error matching, workarounds, and root cause isolation on a live ticket.

  • Severity sla desk

    MadewellRD/skills-lab/dist/vendor/anthropic/customer-support-command-desk/severity-sla-desk Skill

    2★ repo

    set support severity from customer impact and run every sla clock against the executed agreement, computing first response, next update, restoration, and resolution targets on the contractual calendar and timezone, pausing only under the written pause rule, and reporting the at-risk and breached position with the credit exposure behind it. use for severity assignment and disputes, sla target calculation, business-hours and follow-the-sun coverage, clock pauses on pending-customer, breach reporting, and service credit exposure.

  • Ticket triage desk

    MadewellRD/skills-lab/dist/vendor/anthropic/customer-support-command-desk/ticket-triage-desk Skill

    2★ repo

    route and order support tickets by naming the queue, tier, and skill each contact requires, setting priority from the ordering rule in force and keeping it distinct from contractual severity, identifying spam, duplicates, machine-generated tickets, and misrouted work with the evidence for each, and separating contacts a published answer already resolves from contacts that need diagnosis. use for queue assignment, tier escalation criteria, skill-based routing, priority disputes, bounce-back loops, and misrouting patterns worth fixing in the rules.

  • Contract intake triage desk

    MadewellRD/skills-lab/dist/vendor/anthropic/legal-contracts-command-desk/contract-intake-triage-desk Skill

    2★ repo

    triage inbound contract requests by classifying matter type, posture, and whose paper the draft arrived on, scoring the risk tier against the named triage rubric, selecting review lanes, checking the repository for an existing agreement over the same scope, and assigning legal owner and committed turnaround. use for new contract requests, nda queues, vendor onboarding packages, quote-to-contract intake, deal desk escalations, renewal intake, self-serve template deflection, and legal front door routing.

  • Intake triage desk

    MadewellRD/skills-lab/dist/vendor/anthropic/procurement-vendor-management-command-desk/intake-triage-desk Skill

    2★ repo

    triage a purchase requisition by classifying the need as a capability rather than a product name, checking duplicates and overlap against existing agreements and licensed tools, converting a monthly or per-seat quote into annual and total contract value including renewal terms, testing the urgency claim against what actually creates the date, and routing to the sourcing method risk path and lead time the request requires. use for new purchase requests, intake queues, duplicate tool checks, total contract value calculations, emergency purchase claims, and requests where a team has already signed or already told a supplier.

  • Ci failure desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/ci-failure-desk Skill

    2★ repo

    create connector-grounded ci/cd failure triage and pipeline-health artifacts for software delivery. use when Claude needs to diagnose github actions or build failures, classify flaky tests, inspect logs and workflow runs, decide rerun versus fix, identify failing checks, map ci failures to code changes or infrastructure, or prepare downstream handoff notes for review-quality-desk, verification-desk, release-operations-desk, incident-response-desk, issue-planning-desk, or implementation-handoff-desk workflows.

  • Incident response desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/incident-response-desk Skill

    2★ repo

    create connector-grounded incident response, bug triage, severity classification, root cause analysis, hotfix handoff, follow-up issue, post-incident review, and production-support artifacts from incidents, alerts, logs, metrics, traces, recent deploys, github issues, pull requests, ci evidence, runbooks, and stakeholder updates. use when Claude needs to triage a production failure, summarize an incident, draft an rca, plan a hotfix, map remediation work, or prepare downstream handoff notes for implementation-handoff-desk, ci-failure-desk, deployment-desk, observability-readiness-desk, release-operations-desk, verification-desk, or docs-traceability-desk workflows.

  • Customer support command desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/customer-support-command-desk Skill

    2★ repo

    orchestrate customer support work across ticket intake and entitlement checks, triage and routing, severity and sla clocks, troubleshooting and diagnosis, reproduction and bug intake, engineering escalation, macro and response quality, resolution and closure, customer-facing incident communication and status page updates, post-incident follow-up and outage letters, knowledge base authoring, self-service deflection, queue and backlog health, workforce coverage and staffing, helpdesk tooling and automation, qa review and calibration, contact driver analysis, and support metrics reporting. use when a ticket needs triage or a severity, an sla is about to breach, a customer reports something nobody can reproduce, a bug needs filing to engineering, an escalation needs raising, a backlog is aging, csat or first response time is being explained, a macro or help center article needs writing, deflection is being measured, an outage needs customer comms and an outage letter, or staffing is being planned against forecast volume.

  • Diagnostic troubleshooting desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/diagnostic-troubleshooting-desk Skill

    2★ repo

    take a support symptom to a cause by carrying hypotheses with the observation that would confirm or eliminate each, building an evidence inventory from logs, traces, har captures, configuration exports, and diagnostic bundles with collection times and retention limits, separating product defect from configuration from integration from customer environment from expected behavior, and stating the cause at the confidence it was established. use for troubleshooting, log and trace analysis, known error matching, workarounds, and root cause isolation on a live ticket.

  • Severity sla desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/severity-sla-desk Skill

    2★ repo

    set support severity from customer impact and run every sla clock against the executed agreement, computing first response, next update, restoration, and resolution targets on the contractual calendar and timezone, pausing only under the written pause rule, and reporting the at-risk and breached position with the credit exposure behind it. use for severity assignment and disputes, sla target calculation, business-hours and follow-the-sun coverage, clock pauses on pending-customer, breach reporting, and service credit exposure.

  • Ticket triage desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/ticket-triage-desk Skill

    2★ repo

    route and order support tickets by naming the queue, tier, and skill each contact requires, setting priority from the ordering rule in force and keeping it distinct from contractual severity, identifying spam, duplicates, machine-generated tickets, and misrouted work with the evidence for each, and separating contacts a published answer already resolves from contacts that need diagnosis. use for queue assignment, tier escalation criteria, skill-based routing, priority disputes, bounce-back loops, and misrouting patterns worth fixing in the rules.

  • Contract intake triage desk

    MadewellRD/skills-lab/dist/vendor/google/legal-contracts-command-desk/contract-intake-triage-desk Skill

    2★ repo

    triage inbound contract requests by classifying matter type, posture, and whose paper the draft arrived on, scoring the risk tier against the named triage rubric, selecting review lanes, checking the repository for an existing agreement over the same scope, and assigning legal owner and committed turnaround. use for new contract requests, nda queues, vendor onboarding packages, quote-to-contract intake, deal desk escalations, renewal intake, self-serve template deflection, and legal front door routing.

  • Intake triage desk

    MadewellRD/skills-lab/dist/vendor/google/procurement-vendor-management-command-desk/intake-triage-desk Skill

    2★ repo

    triage a purchase requisition by classifying the need as a capability rather than a product name, checking duplicates and overlap against existing agreements and licensed tools, converting a monthly or per-seat quote into annual and total contract value including renewal terms, testing the urgency claim against what actually creates the date, and routing to the sourcing method risk path and lead time the request requires. use for new purchase requests, intake queues, duplicate tool checks, total contract value calculations, emergency purchase claims, and requests where a team has already signed or already told a supplier.

  • Ci failure desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/ci-failure-desk Skill

    2★ repo

    create connector-grounded ci/cd failure triage and pipeline-health artifacts for software delivery. use when Gemini needs to diagnose github actions or build failures, classify flaky tests, inspect logs and workflow runs, decide rerun versus fix, identify failing checks, map ci failures to code changes or infrastructure, or prepare downstream handoff notes for review-quality-desk, verification-desk, release-operations-desk, incident-response-desk, issue-planning-desk, or implementation-handoff-desk workflows.

  • Incident response desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/incident-response-desk Skill

    2★ repo

    create connector-grounded incident response, bug triage, severity classification, root cause analysis, hotfix handoff, follow-up issue, post-incident review, and production-support artifacts from incidents, alerts, logs, metrics, traces, recent deploys, github issues, pull requests, ci evidence, runbooks, and stakeholder updates. use when Gemini needs to triage a production failure, summarize an incident, draft an rca, plan a hotfix, map remediation work, or prepare downstream handoff notes for implementation-handoff-desk, ci-failure-desk, deployment-desk, observability-readiness-desk, release-operations-desk, verification-desk, or docs-traceability-desk workflows.

  • Customer support command desk

    MadewellRD/skills-lab/dist/vendor/openai/customer-support-command-desk/customer-support-command-desk Skill

    2★ repo

    orchestrate customer support work across ticket intake and entitlement checks, triage and routing, severity and sla clocks, troubleshooting and diagnosis, reproduction and bug intake, engineering escalation, macro and response quality, resolution and closure, customer-facing incident communication and status page updates, post-incident follow-up and outage letters, knowledge base authoring, self-service deflection, queue and backlog health, workforce coverage and staffing, helpdesk tooling and automation, qa review and calibration, contact driver analysis, and support metrics reporting. use when a ticket needs triage or a severity, an sla is about to breach, a customer reports something nobody can reproduce, a bug needs filing to engineering, an escalation needs raising, a backlog is aging, csat or first response time is being explained, a macro or help center article needs writing, deflection is being measured, an outage needs customer comms and an outage letter, or staffing is being planned against forecast volume.

  • Diagnostic troubleshooting desk

    MadewellRD/skills-lab/dist/vendor/openai/customer-support-command-desk/diagnostic-troubleshooting-desk Skill

    2★ repo

    take a support symptom to a cause by carrying hypotheses with the observation that would confirm or eliminate each, building an evidence inventory from logs, traces, har captures, configuration exports, and diagnostic bundles with collection times and retention limits, separating product defect from configuration from integration from customer environment from expected behavior, and stating the cause at the confidence it was established. use for troubleshooting, log and trace analysis, known error matching, workarounds, and root cause isolation on a live ticket.

  • Severity sla desk

    MadewellRD/skills-lab/dist/vendor/openai/customer-support-command-desk/severity-sla-desk Skill

    2★ repo

    set support severity from customer impact and run every sla clock against the executed agreement, computing first response, next update, restoration, and resolution targets on the contractual calendar and timezone, pausing only under the written pause rule, and reporting the at-risk and breached position with the credit exposure behind it. use for severity assignment and disputes, sla target calculation, business-hours and follow-the-sun coverage, clock pauses on pending-customer, breach reporting, and service credit exposure.