[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F15GWV3CNRSCZ8TKAC3EHT":3,"skill-same:01M7F15GWV3CNRSCZ8TKAC3EHT":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F15GWV3CNRSCZ8TKAC3EHT","incident-runbook-templates",null,"Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts; onboarding new on-call engineers who need step-by-step recovery guides written for a 3 AM brain; or standardizing escalation matrices across multiple engineering teams.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-response\u002Fskills\u002Fincident-runbook-templates\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: incident-runbook-templates\ndescription: Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts; onboarding new on-call engineers who need step-by-step recovery guides written for a 3 AM brain; or standardizing escalation matrices across multiple engineering teams.\n---\n\n# Incident Runbook Templates\n\nProduction-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication.\n\n## When to Use This Skill\n\n- Creating incident response procedures\n- Building service-specific runbooks\n- Establishing escalation paths\n- Documenting recovery procedures\n- Responding to active incidents\n- Onboarding on-call engineers\n\n## Core Concepts\n\n### 1. Incident Severity Levels\n\n| Severity | Impact                     | Response Time     | Example                 |\n| -------- | -------------------------- | ----------------- | ----------------------- |\n| **SEV1** | Complete outage, data loss | 15 min            | Production down         |\n| **SEV2** | Major degradation          | 30 min            | Critical feature broken |\n| **SEV3** | Minor impact               | 2 hours           | Non-critical bug        |\n| **SEV4** | Minimal impact             | Next business day | Cosmetic issue          |\n\n### 2. Runbook Structure\n\n```\n1. Overview & Impact\n2. Detection & Alerts\n3. Initial Triage\n4. Mitigation Steps\n5. Root Cause Investigation\n6. Resolution Procedures\n7. Verification & Rollback\n8. Communication Templates\n9. Escalation Matrix\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices\n\n### Do's\n- **Keep runbooks updated** - Review after every incident\n- **Test runbooks regularly** - Game days, chaos engineering\n- **Include rollback steps** - Always have an escape hatch\n- **Document assumptions** - What must be true for steps to work\n- **Link to dashboards** - Quick access during stress\n\n### Don'ts\n- **Don't assume knowledge** - Write for 3 AM brain\n- **Don't skip verification** - Confirm each step worked\n- **Don't forget communication** - Keep stakeholders informed\n- **Don't work alone** - Escalate early\n- **Don't skip postmortems** - Learn from every incident\n\n## Troubleshooting\n\n### Runbook steps work in staging but fail during a real incident\n\nSteps often assume preconditions that are true in a healthy environment but not during an outage. For each command in your runbook, add a prerequisite check and a \"what to do if this command fails\" note:\n\n```bash\n# Step: Check pod status\nkubectl get pods -n payments\n\n# Prerequisites: kubectl configured, kubeconfig points to correct cluster\n# If this fails: run `aws eks update-kubeconfig --name prod-cluster --region us-east-1`\n# Expected output: pods in Running state\n```\n\n### On-call engineer panics and skips steps out of order\n\nAdd a numbered checklist at the top of the runbook that mirrors the section numbers, so responders can track progress under stress without reading the full document:\n\n```markdown\n## Quick Checklist\n- [ ] 1. Declare incident severity and open war room\n- [ ] 2. Check service health (Section 4.1)\n- [ ] 3. Check recent deployments (Section 4.1)\n- [ ] 4. Roll back if deploy is suspect (Section 4.1)\n- [ ] 5. Post initial notification to #payments-incidents\n- [ ] 6. Escalate if > 15 min unresolved\n```\n\n### Runbook is outdated — commands reference old cluster names or endpoints\n\nRunbooks rot because they're updated manually. Include a \"Last Verified\" date and owner at the top, and add a CI check that validates all `curl` endpoints and `kubectl` context names are still valid:\n\n```markdown\n## Runbook Metadata\n| Field | Value |\n|---|---|\n| Last verified | 2024-11-15 |\n| Owner | @platform-team |\n| Review cadence | After every SEV1\u002FSEV2 |\n```\n\n### Stakeholder communication is delayed while engineers are heads-down\n\nAssign a dedicated incident communicator role (separate from the incident commander) whose only job is to post status updates. Add a standing agenda in the communication template:\n\n```\nUpdate every 15 minutes (even if no new information):\n- Current status (Investigating \u002F Mitigating \u002F Monitoring)\n- Impact (what is broken, who is affected, % of traffic)\n- What we are doing right now\n- Next update in: 15 minutes\n```\n\n### Database runbook commands cause additional downtime when run incorrectly\n\nAdd explicit warnings before destructive SQL commands and require a dry-run output check before executing:\n\n```sql\n-- WARNING: This terminates active connections. Verify count first.\n-- DRY RUN (check count before terminating):\nSELECT count(*) FROM pg_stat_activity WHERE state = 'idle' AND query_start \u003C now() - interval '10 minutes';\n\n-- EXECUTE only after verifying count is reasonable (\u003C 50):\nSELECT pg_terminate_backend(pid) FROM pg_stat_activity\nWHERE state = 'idle' AND query_start \u003C now() - interval '10 minutes';\n```\n\n## Related Skills\n\n- `postmortem-writing` - After resolving an incident, use postmortem templates to capture root cause and preventive actions\n- `on-call-handoff-patterns` - Structure shift handoffs so the incoming responder has full context on active incidents","# Incident Runbook Templates\n\nProduction-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication.\n\n## When to Use This Skill\n\n- Creating incident response procedures\n- Building service-specific runbooks\n- Establishing escalation paths\n- Documenting recovery procedures\n- Responding to active incidents\n- Onboarding on-call engineers\n\n## Core Concepts\n\n### 1. Incident Severity Levels\n\n| Severity | Impact                     | Response Time     | Example                 |\n| -------- | -------------------------- | ----------------- | ----------------------- |\n| **SEV1** | Complete outage, data loss | 15 min            | Production down         |\n| **SEV2** | Major degradation          | 30 min            | Critical feature broken |\n| **SEV3** | Minor impact               | 2 hours           | Non-critical bug        |\n| **SEV4** | Minimal impact             | Next business day | Cosmetic issue          |\n\n### 2. Runbook Structure\n\n```\n1. Overview & Impact\n2. Detection & Alerts\n3. Initial Triage\n4. Mitigation Steps\n5. Root Cause Investigation\n6. Resolution Procedures\n7. Verification & Rollback\n8. Communication Templates\n9. Escalation Matrix\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices\n\n### Do's\n- **Keep runbooks updated** - Review after every incident\n- **Test runbooks regularly** - Game days, chaos engineering\n- **Include rollback steps** - Always have an escape hatch\n- **Document assumptions** - What must be true for steps to work\n- **Link to dashboards** - Quick access during stress\n\n### Don'ts\n- **Don't assume knowledge** - Write for 3 AM brain\n- **Don't skip verification** - Confirm each step worked\n- **Don't forget communication** - Keep stakeholders informed\n- **Don't work alone** - Escalate early\n- **Don't skip postmortems** - Learn from every incident\n\n## Troubleshooting\n\n### Runbook steps work in staging but fail during a real incident\n\nSteps often assume preconditions that are true in a healthy environment but not during an outage. For each command in your runbook, add a prerequisite check and a \"what to do if this command fails\" note:\n\n```bash\n# Step: Check pod status\nkubectl get pods -n payments\n\n# Prerequisites: kubectl configured, kubeconfig points to correct cluster\n# If this fails: run `aws eks update-kubeconfig --name prod-cluster --region us-east-1`\n# Expected output: pods in Running state\n```\n\n### On-call engineer panics and skips steps out of order\n\nAdd a numbered checklist at the top of the runbook that mirrors the section numbers, so responders can track progress under stress without reading the full document:\n\n```markdown\n## Quick Checklist\n- [ ] 1. Declare incident severity and open war room\n- [ ] 2. Check service health (Section 4.1)\n- [ ] 3. Check recent deployments (Section 4.1)\n- [ ] 4. Roll back if deploy is suspect (Section 4.1)\n- [ ] 5. Post initial notification to #payments-incidents\n- [ ] 6. Escalate if > 15 min unresolved\n```\n\n### Runbook is outdated — commands reference old cluster names or endpoints\n\nRunbooks rot because they're updated manually. Include a \"Last Verified\" date and owner at the top, and add a CI check that validates all `curl` endpoints and `kubectl` context names are still valid:\n\n```markdown\n## Runbook Metadata\n| Field | Value |\n|---|---|\n| Last verified | 2024-11-15 |\n| Owner | @platform-team |\n| Review cadence | After every SEV1\u002FSEV2 |\n```\n\n### Stakeholder communication is delayed while engineers are heads-down\n\nAssign a dedicated incident communicator role (separate from the incident commander) whose only job is to post status updates. Add a standing agenda in the communication template:\n\n```\nUpdate every 15 minutes (even if no new information):\n- Current status (Investigating \u002F Mitigating \u002F Monitoring)\n- Impact (what is broken, who is affected, % of traffic)\n- What we are doing right now\n- Next update in: 15 minutes\n```\n\n### Database runbook commands cause additional downtime when run incorrectly\n\nAdd explicit warnings before destructive SQL commands and require a dry-run output check before executing:\n\n```sql\n-- WARNING: This terminates active connections. Verify count first.\n-- DRY RUN (check count before terminating):\nSELECT count(*) FROM pg_stat_activity WHERE state = 'idle' AND query_start \u003C now() - interval '10 minutes';\n\n-- EXECUTE only after verifying count is reasonable (\u003C 50):\nSELECT pg_terminate_backend(pid) FROM pg_stat_activity\nWHERE state = 'idle' AND query_start \u003C now() - interval '10 minutes';\n```\n\n## Related Skills\n\n- `postmortem-writing` - After resolving an incident, use postmortem templates to capture root cause and preventive actions\n- `on-call-handoff-patterns` - Structure shift handoffs so the incoming responder has full context on active incidents",{"name":5,"description":7},"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fincident-response\u002Fskills\u002Fincident-runbook-templates","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill incident-runbook-templates",{"tool":38,"command":39},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill incident-runbook-templates",{"tool":41,"command":42},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill incident-runbook-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-response\u002Fskills\u002Fincident-runbook-templates\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdetails.md","REFERENCE","参考文档",8761,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-response\u002Fskills\u002Fincident-runbook-templates\u002Freferences\u002Fdetails.md",[53,59,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]