[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDB6MKBPYFQY4385E4836B":3,"skill-same:01M6MDB6MKBPYFQY4385E4836B":62},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6MDB6MKBPYFQY4385E4836B","incident-response",null,"Production incident playbook. Use immediately when production is degraded or down. Five phases: detect, contain, diagnose, resolve, post-mortem. Prevents the chaos of uncoordinated response and ensures every incident produces lasting improvements.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fincident-response\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"incident response","incident","diagnose","Production","playbook","use","chaos","production incident","post","detect","contain","down","post-mortem","when","2026-11-10 10:12:30",false,"---\nname: incident-response\ndescription: \"Production incident playbook. Use immediately when production is degraded or down. Five phases: detect, contain, diagnose, resolve, post-mortem. Prevents the chaos of uncoordinated response and ensures every incident produces lasting improvements.\"\n---\n\n# Incident Response\n\n## The Law\n\n```\nCALM IS A SKILL. PANIC IS A CHOICE.\nAn incident is a system behaving unexpectedly. It is solved by evidence, not speed.\nFast wrong fixes extend incidents. Slow correct fixes end them.\n```\n\n## When to Use\n\nUse this skill immediately when:\n- Error rate spikes above baseline\n- Latency exceeds SLA\n- A service is unreachable\n- Data is inconsistent or missing\n- A security event is suspected\n\n## The Five Phases\n\n---\n\n### Phase 1: Detect & Declare (first 5 minutes)\n\n**Assess impact — answer three questions:**\n1. What is broken? (which service, endpoint, feature)\n2. Who is affected? (all users, subset, specific region, specific plan tier)\n3. When did it start? (exact time from monitoring, not \"someone noticed\")\n\n**Declare the incident:**\n- Create an incident channel: `#incident-YYYY-MM-DD-short-description`\n- Post the initial status: service, impact, start time, who is investigating\n- Set the incident severity:\n\n| Severity | Definition |\n|----------|-----------|\n| SEV-1 | Complete service outage or data loss. All hands. |\n| SEV-2 | Critical feature broken, significant user impact. Team leads involved. |\n| SEV-3 | Partial degradation, workaround exists. Engineering only. |\n| SEV-4 | Minor issue, low user impact. Standard ticket. |\n\n**Do not investigate alone for SEV-1\u002FSEV-2.** Assign roles:\n- **Incident Commander** — coordinates response, owns communication\n- **Technical Lead** — drives diagnosis and fix\n- **Comms** — updates status page and stakeholders\n\n---\n\n### Phase 2: Contain (first 15 minutes)\n\n**Stop the bleeding before diagnosing the wound.**\n\nLook for the fastest way to reduce impact — in this order:\n\n1. **Rollback** — was there a recent deploy? Roll it back. Rollback is always faster than a hotfix.\n   ```bash\n   git revert HEAD --no-edit && git push\n   # or\n   kubectl rollout undo deployment\u002Fapi\n   ```\n\n2. **Feature flag off** — can the broken feature be disabled without affecting the whole service?\n\n3. **Circuit breaker \u002F rate limit** — if a downstream service is causing the issue, can you stop calling it temporarily?\n\n4. **Scale up** — if it's a load issue, can you add capacity immediately?\n\n5. **Redirect traffic** — failover to a secondary region or static error page\n\n**Containment does not require knowing the root cause.** Act fast to reduce impact, then diagnose.\n\n---\n\n### Phase 3: Diagnose (parallel with or after containment)\n\nWork from evidence. No guessing.\n\n**Evidence sources in order of reliability:**\n1. Monitoring dashboards — what changed at the incident start time?\n2. Error logs — what errors appear that didn't before?\n3. Recent deploys — what changed in the last 24 hours?\n4. Recent config changes — feature flags, environment variables, infrastructure changes\n5. External dependencies — is a third-party service degraded? Check their status page.\n\n**Diagnostic commands:**\n```bash\n# Recent deploys\ngit log --oneline -20\n\n# Error spike in logs\ngrep ERROR app.log | grep \"$(date +%Y-%m-%dT%H)\" | wc -l\n\n# Slow queries\npsql -c \"SELECT query, mean_exec_time FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10;\"\n\n# Service health\nkubectl get pods --all-namespaces | grep -v Running\nkubectl describe pod \u003Cfailing-pod>\nkubectl logs \u003Cfailing-pod> --previous\n```\n\n**Form a single hypothesis:** \"The incident is caused by X because evidence Y shows Z.\"\nTest it minimally before acting on it.\n\n---\n\n### Phase 4: Resolve\n\nApply the fix with the minimum blast radius.\n\n**Fix principles:**\n- Prefer rollback over hotfix — hotfixes under pressure introduce new bugs\n- Apply to staging first if a \u003C5 minute delay is acceptable\n- Have a rollback plan for the fix itself\n- One change at a time — never apply multiple fixes simultaneously\n\n**After applying fix:**\n- Verify the metric that triggered the incident is recovering\n- Confirm no new errors introduced\n- Keep monitoring for 15 minutes before declaring resolved\n\n**Declare resolved:**\n```\nRESOLVED — [time]\nService restored. Root cause: [one sentence].\nFollow-up actions tracked in post-mortem.\n```\n\n---\n\n### Phase 5: Post-Mortem (within 48 hours)\n\nEvery SEV-1 and SEV-2 gets a written post-mortem. Every SEV-3 gets at least a brief one.\n\n**Template: `docs\u002Fpostmortems\u002FYYYY-MM-DD-short-title.md`**\n\n```markdown\n# Post-Mortem: [Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV-N\n**Duration:** Xh Ym (detected HH:MM → resolved HH:MM)\n**Impact:** [who was affected and how]\n\n## Timeline\n\n| Time | Event |\n|------|-------|\n| HH:MM | First alert triggered |\n| HH:MM | Engineer notified |\n| HH:MM | Incident declared |\n| HH:MM | Containment applied |\n| HH:MM | Root cause identified |\n| HH:MM | Fix deployed |\n| HH:MM | Incident resolved |\n\n## Root Cause\n\n[One clear sentence. Not \"the server crashed\" — why did the server crash.]\n\n## Contributing Factors\n\n- [What made this possible \u002F what made detection slow \u002F what made recovery slow]\n\n## What Went Well\n\n- [Things that helped, even small ones]\n\n## Action Items\n\n| Action | Owner | Due |\n|--------|-------|-----|\n| Add alert for X | @person | YYYY-MM-DD |\n| Fix root cause Y | @person | YYYY-MM-DD |\n| Add runbook for Z | @person | YYYY-MM-DD |\n```\n\n**Post-mortem rules:**\n- Blameless — systems fail, not people\n- Focus on systemic improvements, not individual mistakes\n- Every action item has an owner and a date\n- Action items are tracked as real tickets, not just documented and forgotten\n\n## Communication Templates\n\n**Status page update (during incident):**\n```\n[INVESTIGATING] We are investigating reports of [issue] affecting [scope].\nOur team is actively working on a resolution. Next update in 30 minutes.\n```\n\n**Resolution notice:**\n```\n[RESOLVED] The issue affecting [scope] has been resolved as of [time].\nRoot cause was [brief explanation]. A full post-mortem will be published within 48 hours.\nWe apologise for the inconvenience.\n```\n","# Incident Response\n\n## The Law\n\n```\nCALM IS A SKILL. PANIC IS A CHOICE.\nAn incident is a system behaving unexpectedly. It is solved by evidence, not speed.\nFast wrong fixes extend incidents. Slow correct fixes end them.\n```\n\n## When to Use\n\nUse this skill immediately when:\n- Error rate spikes above baseline\n- Latency exceeds SLA\n- A service is unreachable\n- Data is inconsistent or missing\n- A security event is suspected\n\n## The Five Phases\n\n---\n\n### Phase 1: Detect & Declare (first 5 minutes)\n\n**Assess impact — answer three questions:**\n1. What is broken? (which service, endpoint, feature)\n2. Who is affected? (all users, subset, specific region, specific plan tier)\n3. When did it start? (exact time from monitoring, not \"someone noticed\")\n\n**Declare the incident:**\n- Create an incident channel: `#incident-YYYY-MM-DD-short-description`\n- Post the initial status: service, impact, start time, who is investigating\n- Set the incident severity:\n\n| Severity | Definition |\n|----------|-----------|\n| SEV-1 | Complete service outage or data loss. All hands. |\n| SEV-2 | Critical feature broken, significant user impact. Team leads involved. |\n| SEV-3 | Partial degradation, workaround exists. Engineering only. |\n| SEV-4 | Minor issue, low user impact. Standard ticket. |\n\n**Do not investigate alone for SEV-1\u002FSEV-2.** Assign roles:\n- **Incident Commander** — coordinates response, owns communication\n- **Technical Lead** — drives diagnosis and fix\n- **Comms** — updates status page and stakeholders\n\n---\n\n### Phase 2: Contain (first 15 minutes)\n\n**Stop the bleeding before diagnosing the wound.**\n\nLook for the fastest way to reduce impact — in this order:\n\n1. **Rollback** — was there a recent deploy? Roll it back. Rollback is always faster than a hotfix.\n   ```bash\n   git revert HEAD --no-edit && git push\n   # or\n   kubectl rollout undo deployment\u002Fapi\n   ```\n\n2. **Feature flag off** — can the broken feature be disabled without affecting the whole service?\n\n3. **Circuit breaker \u002F rate limit** — if a downstream service is causing the issue, can you stop calling it temporarily?\n\n4. **Scale up** — if it's a load issue, can you add capacity immediately?\n\n5. **Redirect traffic** — failover to a secondary region or static error page\n\n**Containment does not require knowing the root cause.** Act fast to reduce impact, then diagnose.\n\n---\n\n### Phase 3: Diagnose (parallel with or after containment)\n\nWork from evidence. No guessing.\n\n**Evidence sources in order of reliability:**\n1. Monitoring dashboards — what changed at the incident start time?\n2. Error logs — what errors appear that didn't before?\n3. Recent deploys — what changed in the last 24 hours?\n4. Recent config changes — feature flags, environment variables, infrastructure changes\n5. External dependencies — is a third-party service degraded? Check their status page.\n\n**Diagnostic commands:**\n```bash\n# Recent deploys\ngit log --oneline -20\n\n# Error spike in logs\ngrep ERROR app.log | grep \"$(date +%Y-%m-%dT%H)\" | wc -l\n\n# Slow queries\npsql -c \"SELECT query, mean_exec_time FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10;\"\n\n# Service health\nkubectl get pods --all-namespaces | grep -v Running\nkubectl describe pod \u003Cfailing-pod>\nkubectl logs \u003Cfailing-pod> --previous\n```\n\n**Form a single hypothesis:** \"The incident is caused by X because evidence Y shows Z.\"\nTest it minimally before acting on it.\n\n---\n\n### Phase 4: Resolve\n\nApply the fix with the minimum blast radius.\n\n**Fix principles:**\n- Prefer rollback over hotfix — hotfixes under pressure introduce new bugs\n- Apply to staging first if a \u003C5 minute delay is acceptable\n- Have a rollback plan for the fix itself\n- One change at a time — never apply multiple fixes simultaneously\n\n**After applying fix:**\n- Verify the metric that triggered the incident is recovering\n- Confirm no new errors introduced\n- Keep monitoring for 15 minutes before declaring resolved\n\n**Declare resolved:**\n```\nRESOLVED — [time]\nService restored. Root cause: [one sentence].\nFollow-up actions tracked in post-mortem.\n```\n\n---\n\n### Phase 5: Post-Mortem (within 48 hours)\n\nEvery SEV-1 and SEV-2 gets a written post-mortem. Every SEV-3 gets at least a brief one.\n\n**Template: `docs\u002Fpostmortems\u002FYYYY-MM-DD-short-title.md`**\n\n```markdown\n# Post-Mortem: [Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV-N\n**Duration:** Xh Ym (detected HH:MM → resolved HH:MM)\n**Impact:** [who was affected and how]\n\n## Timeline\n\n| Time | Event |\n|------|-------|\n| HH:MM | First alert triggered |\n| HH:MM | Engineer notified |\n| HH:MM | Incident declared |\n| HH:MM | Containment applied |\n| HH:MM | Root cause identified |\n| HH:MM | Fix deployed |\n| HH:MM | Incident resolved |\n\n## Root Cause\n\n[One clear sentence. Not \"the server crashed\" — why did the server crash.]\n\n## Contributing Factors\n\n- [What made this possible \u002F what made detection slow \u002F what made recovery slow]\n\n## What Went Well\n\n- [Things that helped, even small ones]\n\n## Action Items\n\n| Action | Owner | Due |\n|--------|-------|-----|\n| Add alert for X | @person | YYYY-MM-DD |\n| Fix root cause Y | @person | YYYY-MM-DD |\n| Add runbook for Z | @person | YYYY-MM-DD |\n```\n\n**Post-mortem rules:**\n- Blameless — systems fail, not people\n- Focus on systemic improvements, not individual mistakes\n- Every action item has an owner and a date\n- Action items are tracked as real tickets, not just documented and forgotten\n\n## Communication Templates\n\n**Status page update (during incident):**\n```\n[INVESTIGATING] We are investigating reports of [issue] affecting [scope].\nOur team is actively working on a resolution. Next update in 30 minutes.\n```\n\n**Resolution notice:**\n```\n[RESOLVED] The issue affecting [scope] has been resolved as of [time].\nRoot cause was [brief explanation]. A full post-mortem will be published within 48 hours.\nWe apologise for the inconvenience.\n```\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fincident-response",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill incident-response",{"tool":54,"command":55},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill incident-response",{"tool":57,"command":58},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fincident-response\u002FSKILL.md",true,[],[63,73,81,89,97,105],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":67,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":72},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":72},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":72},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":72},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":72},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]