[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS2ZRRWP8V2RXC2AMSNCDW":3,"skill-same:01M7CS2ZRRWP8V2RXC2AMSNCDW":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CS2ZRRWP8V2RXC2AMSNCDW","incident-response",null,"How to work a production incident remediation task. Use when the task title starts with \"Incident:\" or its description carries an incident id and a suggest\u002Fauto_fix policy.","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fincident-response\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-response\ncategory: operations\ndescription: How to work a production incident remediation task. Use when the task title starts with \"Incident:\" or its description carries an incident id and a suggest\u002Fauto_fix policy.\n---\n# Incident response\n\nA task titled `Incident: …` is a live production problem, assigned to you by the system. Its description carries an **incident id** and a first-pass hypothesis produced by the rules engine, plus the policy in force (`suggest` or `auto_fix`). That hypothesis is a starting point, not a verdict.\n\n## Order of work\n\n1. **Read the incident first.** `get_incident` with the id from the task description: raw alert payload, timeline, occurrence count, current remedy hypothesis.\n2. **Correlate with the tools you hold.** `get_environment` for the affected environment (provider, health URL, binding status), then `list_deployments` — \"what changed?\" answers most incidents. `list_runtime_errors` with `new: true` tells you whether the error group started with the most recent deploy. `query_runtime_logs` with `text:` set to the error reads what the running service actually did.\n3. **Classify.** Config\u002Fcredentials, dependency, capacity, or code defect. The classes need different fixes, and guessing the class wrong wastes the whole investigation.\n4. **Write the remedy.** `propose_incident_remedy` with a summary (root cause + fix), concrete steps — each as *command → expected output → if it fails: …* — the evidence you relied on, and an honest confidence. Set `rollback: true` when \"redeploy the last good release\" is the fix: you hold no rollback tool yourself, so under `suggest` the human decides from this proposal and under `auto_fix` the release engineer acts on it. If you are not sure, say so with a low confidence and name what you would need to check next — an honest \"here is what I would check\" is useful; a confident guess is not.\n5. **Act per policy.**\n   - **suggest** (default): do NOT change production code. The proposal is the deliverable — move the task to `human_uat` with no code change and say in your closing message that the remedy awaits a human decision.\n   - **auto_fix**: implement the remedy and take it through the normal pipeline — TDD, the standing acceptance criteria, all of it. A hotfix that skips them causes the next incident.\n6. **Resolve only after verifying recovery.** `resolve_incident` only after `get_environment` \u002F `list_runtime_errors` show the environment is actually healthy again, with the note naming that evidence. Never mark an incident resolved because you shipped a fix — shipping and recovering are different facts.\n\n## Rules\n\n- A recurring incident (occurrences > 1, or a prior resolved incident with the same fingerprint) means the previous fix did not hold: fix the cause, not the symptom, and say explicitly why this time is different.\n- Never write a remedy you cannot execute step by step. \"Investigate the database\" is not a remedy; \"connection pool is capped at 10 while the new worker opens 25 — raise `DB_MAX_CONNS` to 40 in the prod config\" is.\n- If the incident payload is not enough to conclude anything, say what specific log, metric or access you need. Do not invent a cause to have something to write.\n","# Incident response\n\nA task titled `Incident: …` is a live production problem, assigned to you by the system. Its description carries an **incident id** and a first-pass hypothesis produced by the rules engine, plus the policy in force (`suggest` or `auto_fix`). That hypothesis is a starting point, not a verdict.\n\n## Order of work\n\n1. **Read the incident first.** `get_incident` with the id from the task description: raw alert payload, timeline, occurrence count, current remedy hypothesis.\n2. **Correlate with the tools you hold.** `get_environment` for the affected environment (provider, health URL, binding status), then `list_deployments` — \"what changed?\" answers most incidents. `list_runtime_errors` with `new: true` tells you whether the error group started with the most recent deploy. `query_runtime_logs` with `text:` set to the error reads what the running service actually did.\n3. **Classify.** Config\u002Fcredentials, dependency, capacity, or code defect. The classes need different fixes, and guessing the class wrong wastes the whole investigation.\n4. **Write the remedy.** `propose_incident_remedy` with a summary (root cause + fix), concrete steps — each as *command → expected output → if it fails: …* — the evidence you relied on, and an honest confidence. Set `rollback: true` when \"redeploy the last good release\" is the fix: you hold no rollback tool yourself, so under `suggest` the human decides from this proposal and under `auto_fix` the release engineer acts on it. If you are not sure, say so with a low confidence and name what you would need to check next — an honest \"here is what I would check\" is useful; a confident guess is not.\n5. **Act per policy.**\n   - **suggest** (default): do NOT change production code. The proposal is the deliverable — move the task to `human_uat` with no code change and say in your closing message that the remedy awaits a human decision.\n   - **auto_fix**: implement the remedy and take it through the normal pipeline — TDD, the standing acceptance criteria, all of it. A hotfix that skips them causes the next incident.\n6. **Resolve only after verifying recovery.** `resolve_incident` only after `get_environment` \u002F `list_runtime_errors` show the environment is actually healthy again, with the note naming that evidence. Never mark an incident resolved because you shipped a fix — shipping and recovering are different facts.\n\n## Rules\n\n- A recurring incident (occurrences > 1, or a prior resolved incident with the same fingerprint) means the previous fix did not hold: fix the cause, not the symptom, and say explicitly why this time is different.\n- Never write a remedy you cannot execute step by step. \"Investigate the database\" is not a remedy; \"connection pool is capped at 10 while the new worker opens 25 — raise `DB_MAX_CONNS` to 40 in the prod config\" is.\n- If the incident payload is not enough to conclude anything, say what specific log, metric or access you need. Do not invent a cause to have something to write.\n",{"name":5,"category":24,"description":7},"operations","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fincident-response",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill incident-response",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill incident-response",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Fincident-response\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]