[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MJR665T0EBQNH8KJ7C9CB":3,"skill-same:01M75MJR665T0EBQNH8KJ7C9CB":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75MJR665T0EBQNH8KJ7C9CB","iac-incident-response",null,"Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.","selamy-labs\u002Fagent-skills","selamy-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287832944?v=4","01M75MDKJ0CKAM94KZ7TWQJM5Q","01M75MDKJNP3TATHAW1MX1FWM6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiac-incident-response\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: iac-incident-response\ndescription: Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.\n---\n\n# IaC Incident Response\n\nUse this when infrastructure is broken and there is pressure to fix it directly.\nThe goal is fast recovery without creating hidden state that the next apply will\ndestroy or fail to reproduce.\n\n## Rules\n\n- Prefer a source change, merge, and apply over direct mutation.\n- If an emergency manual resource exists, import it into state or replace it\n  through a declared resource before declaring recovery complete.\n- Do not bridge a branch by hand-applying manifests that the main branch does\n  not own.\n- Escalate the precise blocker rather than bypassing the source of truth.\n\n## Incident Workflow\n\n1. Identify the failed declarative boundary:\n   - infrastructure plan\u002Fapply\n   - GitOps sync\n   - controller reconciliation\n   - CI secret\u002Fconfig propagation\n2. Make the smallest source change that lets the normal reconciler fix the\n   system.\n3. If live state already changed, reconcile it:\n   - import hand-made resources into state, or\n   - remove them only after the declared replacement is ready.\n4. Run a no-drift check after recovery:\n   - plan shows no unexpected changes, or expected changes are reviewed\n   - GitOps reports synced\u002Fhealthy\n   - a real workload or workflow proves the path works\n5. Capture the guard that would have caught the failure earlier.\n\n## Acceptable Diagnostics\n\nRead-only cloud, cluster, and CI commands are fine. They become unsafe when they\nturn into live patching, deleting, scaling, or secret mutation without a\nmatching source change.\n\n## Done\n\n- A fresh apply or sync can reproduce the recovered state.\n- Manual emergency resources are gone or imported.\n- The incident report names any remaining external blocker.\n","# IaC Incident Response\n\nUse this when infrastructure is broken and there is pressure to fix it directly.\nThe goal is fast recovery without creating hidden state that the next apply will\ndestroy or fail to reproduce.\n\n## Rules\n\n- Prefer a source change, merge, and apply over direct mutation.\n- If an emergency manual resource exists, import it into state or replace it\n  through a declared resource before declaring recovery complete.\n- Do not bridge a branch by hand-applying manifests that the main branch does\n  not own.\n- Escalate the precise blocker rather than bypassing the source of truth.\n\n## Incident Workflow\n\n1. Identify the failed declarative boundary:\n   - infrastructure plan\u002Fapply\n   - GitOps sync\n   - controller reconciliation\n   - CI secret\u002Fconfig propagation\n2. Make the smallest source change that lets the normal reconciler fix the\n   system.\n3. If live state already changed, reconcile it:\n   - import hand-made resources into state, or\n   - remove them only after the declared replacement is ready.\n4. Run a no-drift check after recovery:\n   - plan shows no unexpected changes, or expected changes are reviewed\n   - GitOps reports synced\u002Fhealthy\n   - a real workload or workflow proves the path works\n5. Capture the guard that would have caught the failure earlier.\n\n## Acceptable Diagnostics\n\nRead-only cloud, cluster, and CI commands are fine. They become unsafe when they\nturn into live patching, deleting, scaling, or secret mutation without a\nmatching source change.\n\n## Done\n\n- A fresh apply or sync can reproduce the recovered state.\n- Manual emergency resources are gone or imported.\n- The incident report names any remaining external blocker.\n",{"name":5,"description":7},"main","54007b08157feb09e5bb9d7ff5ce4ddd21625dbf","skills\u002Fiac-incident-response",3,"https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills","https:\u002F\u002Fselamy.dev","https:\u002F\u002Fgithub.com\u002Fselamy-labs","2026-11-15 03:50:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add selamy-labs\u002Fagent-skills --skill iac-incident-response",{"tool":37,"command":38},"bunx","bunx skills add selamy-labs\u002Fagent-skills --skill iac-incident-response",{"tool":40,"command":41},"pnpm","pnpm dlx skills add selamy-labs\u002Fagent-skills --skill iac-incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiac-incident-response\u002FSKILL.md",true,[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75MY70JMSNFHQX63G90SKZ7","silence-phrase","A seemingly normal skill.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsilence-phrase\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75MY5PKVKY60M8H2DFTW58C","selamy-bad-skill","This skill has a vendor prefix that should be rejected.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fprefixed-name\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75MY1TKXCH6WYN9ET0W4T02","oversized-description","This is a very long description that contains way too many words and should be rejected by the validator because it exceeds the forty five word limit that is enforced by the naming lint checker which ensures skill descriptions stay concise and readable for humans and machines alike without unnecessary verbosity or padding","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Foversized-description\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75MY0SZ7EKT99NWJEJ8HKS2","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75MXYMBREE6D7KRR87YM4DH","malicious-skill","A poisoned skill used only as a negative fixture for the security gate.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmalicious-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75MXX2B7AC2QSSRRQQXTA0N","leaking-org-name","A skill about something.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fleaking-org-name\u002FSKILL.md",[],[]]