[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SHYZGHKAB7NPTA42XFRFE":3,"skill-same:01M79SHYZGHKAB7NPTA42XFRFE":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79SHYZGHKAB7NPTA42XFRFE","cloud-incident-response-architect",null,"Architect-level incident response for cloud estates — severity and declaration, roles and communication, blast-radius containment (revoke, isolate, roll back), evidence preservation, and the post-incident design changes that prevent the next one. Use when systems break in production and the response itself must be engineered.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Foperations-architect\u002Fcloud-incident-response-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-incident-response-architect\ndescription: Architect-level incident response for cloud estates — severity and declaration, roles and communication, blast-radius containment (revoke, isolate, roll back), evidence preservation, and the post-incident design changes that prevent the next one. Use when systems break in production and the response itself must be engineered.\nlicense: MIT\ncompatibility: Any cloud; paging, status pages, IAM revocation\nmetadata:\n  crusor-domain: cloud-and-devops-architect\n  crusor-path: cloud-and-devops-architect\u002Foperations-architect\u002Fcloud-incident-response-architect\n  crusor-origin: original\n  crusor-sources: \"sre.google\u002Fsre-book\u002Fmanaging-incidents; aws.amazon.com\u002Fblogs\u002Fmt\u002Faws-security-incident-response-guide; incident.io\u002Fblog\"\n  crusor-triggers: \"incident response, on call, severity, postmortem, outage, rollback, containment, status page, escalation, runbook\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Cloud Incident Response Architect\n\nAn incident is **a coordination problem under uncertainty**. The technical fix is\nusually simple; the reason it takes four hours is unclear roles and missing\ninformation.\n\n## When to use\n\n- Designing on-call, alerting, and escalation.\n- A security incident needs containment without destroying evidence.\n- Post-incident review after a major outage.\n\n## When NOT to use\n\n- A known failure with an existing runbook — just execute it.\n- Pre-launch risk planning → `reliability-architect`.\n\n## Decision 1 — Roles\n\n| Role | Owns |\n|---|---|\n| incident commander | decisions, priorities, declaring severity |\n| communications lead | status page, stakeholders, updates at fixed cadence |\n| operations lead | the actual mitigation work |\n| scribe | timeline, decisions, hypotheses |\n| subject experts | diagnosis in their area |\n\n- One person can hold several roles in small teams — but the commander must not be\n  the person typing commands.\n- Handover protocol for long incidents: written summary, not a verbal chat.\n- Relieving an exhausted responder is a decision, not a failure.\n\n## Decision 2 — Severity and declaration\n\n- Severity by user impact, defined precisely: S1 total outage, S2 major\n  degradation, S3 partial, S4 internal.\n- Anyone can declare; declaring is never punished. Waiting for permission is the\n  expensive mistake.\n- Page on symptoms, not causes; the commander decides severity, not the alert.\n- Status page updates on a fixed cadence even when there is nothing new.\n\n## Decision 3 — Containment\n\n- Stop the bleeding before root cause: roll back, shift traffic, disable the\n  feature flag, scale out.\n- Security incidents: revoke credentials first, then investigate. Preserve logs\n  and snapshots before cleanup.\n- Isolate without destroying evidence: snapshot the instance, capture the process\n  list, keep the network flow logs.\n- Know in advance what you can turn off, and test those switches\n  (`chaos-engineering-architect` game days).\n\n## Decision 4 — Information\n\n- One channel per incident; a shared timeline document that everyone can write to.\n- Timestamps in one timezone, one format.\n- Dashboards annotated at declaration so the timeline survives after the fact.\n- \"What changed recently?\" is the first question: deploys, config, traffic,\n  certificates, provider status.\n\n## Decision 5 — Resolution and review\n\n- Resolution = SLO restored and verified, not \"it stopped paging\".\n- Post-incident review within five days, blameless, focused on system conditions.\n- Outputs: timeline, contributing factors, what worked, action items with owners\n  and dates.\n- Action items are design changes (timeouts, alerts, runbooks, tests); a doc-only\n  outcome means the review failed.\n- Track action completion; publish it — that is how trust is rebuilt.\n\n## Decision 6 — Preparedness\n\n- Runbooks for the top 10 failure modes, each tested in a game day.\n- On-call rotation with escalation and a documented response-time expectation.\n- Tooling tested: paging, status page credentials, break-glass access.\n- Practice a provider-wide outage scenario — many systems share one dependency.\n\n## Failure modes at scale\n\n- Nobody declares for 40 minutes because everyone assumed someone else would.\n- Commander debugging instead of coordinating; no updates for two hours.\n- Rollback attempted without knowing what changed; two more changes layered on top.\n- Security incident: instance terminated before snapshotting.\n- Post-incident actions assigned to nobody, all still open a quarter later.\n\n## Verification receipts\n\n1. Severity matrix with examples and declaration authority.\n2. One incident replayed through the timeline: detection, declaration, mitigation.\n3. Containment switches tested within the last quarter.\n4. Post-incident actions tracked to closure with owners.\n5. On-call contacts and escalation verified by a test page.\n","# Cloud Incident Response Architect\n\nAn incident is **a coordination problem under uncertainty**. The technical fix is\nusually simple; the reason it takes four hours is unclear roles and missing\ninformation.\n\n## When to use\n\n- Designing on-call, alerting, and escalation.\n- A security incident needs containment without destroying evidence.\n- Post-incident review after a major outage.\n\n## When NOT to use\n\n- A known failure with an existing runbook — just execute it.\n- Pre-launch risk planning → `reliability-architect`.\n\n## Decision 1 — Roles\n\n| Role | Owns |\n|---|---|\n| incident commander | decisions, priorities, declaring severity |\n| communications lead | status page, stakeholders, updates at fixed cadence |\n| operations lead | the actual mitigation work |\n| scribe | timeline, decisions, hypotheses |\n| subject experts | diagnosis in their area |\n\n- One person can hold several roles in small teams — but the commander must not be\n  the person typing commands.\n- Handover protocol for long incidents: written summary, not a verbal chat.\n- Relieving an exhausted responder is a decision, not a failure.\n\n## Decision 2 — Severity and declaration\n\n- Severity by user impact, defined precisely: S1 total outage, S2 major\n  degradation, S3 partial, S4 internal.\n- Anyone can declare; declaring is never punished. Waiting for permission is the\n  expensive mistake.\n- Page on symptoms, not causes; the commander decides severity, not the alert.\n- Status page updates on a fixed cadence even when there is nothing new.\n\n## Decision 3 — Containment\n\n- Stop the bleeding before root cause: roll back, shift traffic, disable the\n  feature flag, scale out.\n- Security incidents: revoke credentials first, then investigate. Preserve logs\n  and snapshots before cleanup.\n- Isolate without destroying evidence: snapshot the instance, capture the process\n  list, keep the network flow logs.\n- Know in advance what you can turn off, and test those switches\n  (`chaos-engineering-architect` game days).\n\n## Decision 4 — Information\n\n- One channel per incident; a shared timeline document that everyone can write to.\n- Timestamps in one timezone, one format.\n- Dashboards annotated at declaration so the timeline survives after the fact.\n- \"What changed recently?\" is the first question: deploys, config, traffic,\n  certificates, provider status.\n\n## Decision 5 — Resolution and review\n\n- Resolution = SLO restored and verified, not \"it stopped paging\".\n- Post-incident review within five days, blameless, focused on system conditions.\n- Outputs: timeline, contributing factors, what worked, action items with owners\n  and dates.\n- Action items are design changes (timeouts, alerts, runbooks, tests); a doc-only\n  outcome means the review failed.\n- Track action completion; publish it — that is how trust is rebuilt.\n\n## Decision 6 — Preparedness\n\n- Runbooks for the top 10 failure modes, each tested in a game day.\n- On-call rotation with escalation and a documented response-time expectation.\n- Tooling tested: paging, status page credentials, break-glass access.\n- Practice a provider-wide outage scenario — many systems share one dependency.\n\n## Failure modes at scale\n\n- Nobody declares for 40 minutes because everyone assumed someone else would.\n- Commander debugging instead of coordinating; no updates for two hours.\n- Rollback attempted without knowing what changed; two more changes layered on top.\n- Security incident: instance terminated before snapshotting.\n- Post-incident actions assigned to nobody, all still open a quarter later.\n\n## Verification receipts\n\n1. Severity matrix with examples and declaration authority.\n2. One incident replayed through the timeline: detection, declaration, mitigation.\n3. Containment switches tested within the last quarter.\n4. Post-incident actions tracked to closure with owners.\n5. On-call contacts and escalation verified by a test page.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"cloud-and-devops-architect\u002Foperations-architect\u002Fcloud-incident-response-architect","cloud-and-devops-architect","original","sre.google\u002Fsre-book\u002Fmanaging-incidents; aws.amazon.com\u002Fblogs\u002Fmt\u002Faws-security-incident-response-guide; incident.io\u002Fblog","incident response, on call, severity, postmortem, outage, rollback, containment, status page, escalation, runbook","2026-10-30","Any cloud; paging, status pages, IAM revocation","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcloud-and-devops-architect\u002Foperations-architect\u002Fcloud-incident-response-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill cloud-incident-response-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill cloud-incident-response-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill cloud-incident-response-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Foperations-architect\u002Fcloud-incident-response-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\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":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]