[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76S09DHTPYMC5B5XZMJ8SWG":3,"skill-same:01M76S09DHTPYMC5B5XZMJ8SWG":56},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M76S09DHTPYMC5B5XZMJ8SWG","triage-incident",null,"Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.","contextosai\u002Fskills","contextosai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250783517?v=4","01M755ZZB3A7TQ0JMXMQ3V9C6A","Piyush","01M755ZZBYNZNFZBVZ2278BSYT",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-incident\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: triage-incident\ndescription: Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.\n---\n\n# Triage an Incident\n\nReduce harm first, preserve the ability to learn why, and keep facts distinct\nfrom hypotheses.\n\n## Protocol\n\n1. Establish whether the event is active. Record start\u002Fdetection time, affected\n   users\u002Fregions\u002Fintents, symptom, severity signals, and current owner. Use\n   absolute timestamps with timezone.\n2. Define impact in user and business terms. Separate confirmed impact from\n   suspected blast radius and monitoring artifacts.\n3. Freeze unnecessary changes and preserve volatile evidence: deploy\u002Fversion\n   identifiers, flags\u002Fconfig, traces, logs, metrics, queue depth, resource state,\n   and recent changes. Redact sensitive data.\n4. Identify the failing boundary and healthy comparison: region, tenant,\n   version, route, dependency, data partition, or time window.\n5. Choose the safest reversible mitigation that reduces harm fastest: disable a\n   feature, shed load, fail closed\u002Fopen according to risk, route traffic,\n   rollback code\u002Fconfig, pause writes, or degrade functionality. State expected\n   signal, abort threshold, and recovery path before acting.\n6. Do not mutate production without explicit authority. When authorized, make\n   one controlled change at a time and timestamp the observation window.\n7. Maintain competing hypotheses and discriminating evidence. Do not let the\n   most senior or most recent theory become fact by repetition.\n8. Reassess impact after mitigation. Watch for silent corruption, backlog,\n   retries, secondary saturation, or delayed consumers after headline metrics\n   recover.\n9. Declare stabilization only when user-impact and system-health signals remain\n   within stated bounds for an appropriate window. Hand off residual recovery,\n   root-cause investigation, and evidence retention explicitly.\n\n## Communication discipline\n\n- Use `references\u002Fincident-record.md` as the shared source of truth.\n- Publish facts, actions, owners, timestamps, and next update time. Avoid raw\n  speculation in stakeholder updates.\n- Mark decisions with rationale and the evidence expected to confirm or reverse\n  them.\n- Never expose credentials, exploit details, private user data, or sensitive\n  internal identifiers in broad updates.\n\n## Exit conditions\n\nEnd triage with current severity, confirmed impact, mitigation state, residual\nrisk, recovery owner, next checkpoint, and whether root-cause work is separate.\nDo not declare resolution merely because alert volume dropped.\n","# Triage an Incident\n\nReduce harm first, preserve the ability to learn why, and keep facts distinct\nfrom hypotheses.\n\n## Protocol\n\n1. Establish whether the event is active. Record start\u002Fdetection time, affected\n   users\u002Fregions\u002Fintents, symptom, severity signals, and current owner. Use\n   absolute timestamps with timezone.\n2. Define impact in user and business terms. Separate confirmed impact from\n   suspected blast radius and monitoring artifacts.\n3. Freeze unnecessary changes and preserve volatile evidence: deploy\u002Fversion\n   identifiers, flags\u002Fconfig, traces, logs, metrics, queue depth, resource state,\n   and recent changes. Redact sensitive data.\n4. Identify the failing boundary and healthy comparison: region, tenant,\n   version, route, dependency, data partition, or time window.\n5. Choose the safest reversible mitigation that reduces harm fastest: disable a\n   feature, shed load, fail closed\u002Fopen according to risk, route traffic,\n   rollback code\u002Fconfig, pause writes, or degrade functionality. State expected\n   signal, abort threshold, and recovery path before acting.\n6. Do not mutate production without explicit authority. When authorized, make\n   one controlled change at a time and timestamp the observation window.\n7. Maintain competing hypotheses and discriminating evidence. Do not let the\n   most senior or most recent theory become fact by repetition.\n8. Reassess impact after mitigation. Watch for silent corruption, backlog,\n   retries, secondary saturation, or delayed consumers after headline metrics\n   recover.\n9. Declare stabilization only when user-impact and system-health signals remain\n   within stated bounds for an appropriate window. Hand off residual recovery,\n   root-cause investigation, and evidence retention explicitly.\n\n## Communication discipline\n\n- Use `references\u002Fincident-record.md` as the shared source of truth.\n- Publish facts, actions, owners, timestamps, and next update time. Avoid raw\n  speculation in stakeholder updates.\n- Mark decisions with rationale and the evidence expected to confirm or reverse\n  them.\n- Never expose credentials, exploit details, private user data, or sensitive\n  internal identifiers in broad updates.\n\n## Exit conditions\n\nEnd triage with current severity, confirmed impact, mitigation state, residual\nrisk, recovery owner, next checkpoint, and whether root-cause work is separate.\nDo not declare resolution merely because alert volume dropped.\n",{"name":5,"description":7},"main","43b8276ae4a34549906dec6c848cbab4ba32f99a","skills\u002Ftriage-incident",0,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills","https:\u002F\u002Fgithub.com\u002Fcontextosai","Local-first AI memory, agentic workflows, and personal knowledge OS for builders.\r\nOpen-source cognitive layer for notes, tools, context, and automation","2026-10-07 00:08:17",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add contextosai\u002Fskills --skill triage-incident",{"tool":38,"command":39},"bunx","bunx skills add contextosai\u002Fskills --skill triage-incident",{"tool":41,"command":42},"pnpm","pnpm dlx skills add contextosai\u002Fskills --skill triage-incident","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-incident\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-incident\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fincident-record.md",1256,"https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-incident\u002Freferences\u002Fincident-record.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M76S0GH6D0VRZ2JFXQF75TY3","template-skill","Replace with a description of what this skill does and when Claude should use it.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M76S0D3VM8XQQFK8RA6YA7R2","verify-change","Design and execute a risk-based verification strategy for a software change, bug fix, refactor, migration, configuration update, or release candidate. Use when Codex needs to prove that a change works, choose proportional tests, investigate whether validation is sufficient, or report what remains unverified. Trace claims to evidence across static checks, focused tests, integration boundaries, and runtime behavior instead of merely running the entire test suite.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-change\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7561WJ328HD8Q6D6R7C6711","review-change","Review a code change for concrete correctness, security, data-integrity, compatibility, concurrency, and operability regressions by reconstructing intent and checking affected invariants and boundary paths. Use for local diffs, commits, branches, patches, or pull requests when the user wants actionable review findings. Report only defects introduced or exposed by the change with precise evidence; do not modify code unless asked to address findings.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freview-change\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7561S5J5V0FY7ND8FBB2C8Q","repo-orient","Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frepo-orient\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7561M6A7D4T3JE315JAB1BG","refactor-safely","Restructure existing code while preserving externally observable behavior through explicit invariants, characterization evidence, small reversible steps, and continuous verification. Use when the user asks to refactor, simplify, extract, reorganize, modularize, deduplicate, split a component, improve architecture, or pay down technical debt without intentionally changing product behavior. Distinguish refactoring from feature work and stop scope drift from hiding inside structural edits.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frefactor-safely\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7561HX5EKDHE9HV7BMXAAND","readme-polish","Improve a project's README for clarity, structure, and completeness without changing its meaning. Use when the user asks to clean up, polish, or improve a README or project documentation.","https:\u002F\u002Fgithub.com\u002Fcontextosai\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freadme-polish\u002FSKILL.md",[],[]]