[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HF799SSCCRCNR65KV3039H":3,"skill-same:01M6HF799SSCCRCNR65KV3039H":74},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6HF799SSCCRCNR65KV3039H","five-whys",null,"Use for the 5 Whys, or when the user wants the root cause of a failure: \"why did this happen?\", \"this keeps breaking\", \"write the postmortem\", \"find the real cause\". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffive-whys\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"five whys","why","postmortem","find","write","user","use","evidence","with","root","typos","at","for","root cause","when","2026","2026-11-10 10:12:30",false,"---\nname: five-whys\ndescription: >\n  Use for the 5 Whys, or when the user wants the root cause of a failure: \"why did this happen?\", \"this keeps breaking\", \"write the postmortem\", \"find the real cause\". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.\nlicense: MIT\nmetadata:\n  author: ysskrishna\n  version: \"2026.10.5\"\n---\n\n# Five Whys\n\nA root-cause method from the Toyota Production System. Ask \"why\" of the previous answer until you reach a cause you can change, and check each link with evidence.\n\n## When to use\n\n- An incident, outage, defect, missed deadline or process failure needs its real cause.\n- A problem repeats after quick fixes.\n- A postmortem or retrospective needs a causal chain, not a list of symptoms.\n\nSkip: a typo or one-line bug whose cause is already visible, or questions about metrics that need data analysis rather than a causal chain.\n\n## Before you start\n\n1. State in one block: **Problem statement** (what happened, where, when, impact, in observable terms) and **Pass** (Chain, Check, Branch if needed, Countermeasures).\n2. **Gather first.** Read logs, commits, tickets, timelines and configs before answering any \"why\". Mark each answer `verified` (you saw evidence) or `hypothesis` (plausible, not yet checked). Ask up to 3 questions only for facts tools cannot reach.\n3. **Light path.** Small ask: the chain in 3-5 lines, one countermeasure per root cause.\n\n## Steps\n\n### 1. Chain\nWrite the problem, then ask why. Each \"Why\" answers the previous answer, not the original problem.\n\n| # | Why did that happen? | Status | Evidence |\n|---|----------------------|--------|----------|\n| 1 | ... | verified \u002F hypothesis | file, log line, ticket |\n\nFive is a guide. Stop earlier or later when you reach a cause that is (a) within the team's control and (b) such that fixing it would have prevented the problem.\n\n### 2. Check\n- **Reverse test:** read the chain from the bottom up with \"therefore\". Each step must follow from the one below.\n- **Stop test:** if the last answer is \"human error\", \"not enough time\" or \"bad luck\", ask why once more. These describe a missing safeguard, not a cause.\n- Mark any link still `hypothesis`; list how to verify it.\n\n### 3. Branch (only if causes split)\nWhen one \"why\" has several valid answers, follow each as its own chain. If the causes spread across many areas, group them under People, Process, Tools, Environment, Data or Measurement (a fishbone view) and chain the top two or three.\n\n### 4. Countermeasures\nFor each root cause:\n- **Contain:** stop the damage now.\n- **Fix:** remove the cause.\n- **Prevent:** a check or guardrail so it cannot recur.\n- **Owner and date**, or \"to be assigned\".\n\n## Pitfalls\n\n- Jumping to a favorite cause and filling the chain backward to justify it.\n- Asking \"who\" instead of \"why\". Blame ends the chain early; look for the missing safeguard.\n- Single-chain thinking on a complex failure. Branch when there are several causes.\n- Stopping at a cause nobody can change (for example \"the vendor was down\") without asking why there was no fallback.\n- Treating `hypothesis` rows as findings in the summary.\n\nWorked example: [references\u002Fexample.md](references\u002Fexample.md).\n\n## Checklist\n\n- [ ] Problem statement is observable (what, where, when, impact)\n- [ ] Each why answers the previous answer; each row is `verified` or `hypothesis`\n- [ ] Reverse test passed; no chain ends at \"human error\"\n- [ ] Branches followed where causes split\n- [ ] Countermeasures cover contain, fix, prevent, with owners\n","# Five Whys\n\nA root-cause method from the Toyota Production System. Ask \"why\" of the previous answer until you reach a cause you can change, and check each link with evidence.\n\n## When to use\n\n- An incident, outage, defect, missed deadline or process failure needs its real cause.\n- A problem repeats after quick fixes.\n- A postmortem or retrospective needs a causal chain, not a list of symptoms.\n\nSkip: a typo or one-line bug whose cause is already visible, or questions about metrics that need data analysis rather than a causal chain.\n\n## Before you start\n\n1. State in one block: **Problem statement** (what happened, where, when, impact, in observable terms) and **Pass** (Chain, Check, Branch if needed, Countermeasures).\n2. **Gather first.** Read logs, commits, tickets, timelines and configs before answering any \"why\". Mark each answer `verified` (you saw evidence) or `hypothesis` (plausible, not yet checked). Ask up to 3 questions only for facts tools cannot reach.\n3. **Light path.** Small ask: the chain in 3-5 lines, one countermeasure per root cause.\n\n## Steps\n\n### 1. Chain\nWrite the problem, then ask why. Each \"Why\" answers the previous answer, not the original problem.\n\n| # | Why did that happen? | Status | Evidence |\n|---|----------------------|--------|----------|\n| 1 | ... | verified \u002F hypothesis | file, log line, ticket |\n\nFive is a guide. Stop earlier or later when you reach a cause that is (a) within the team's control and (b) such that fixing it would have prevented the problem.\n\n### 2. Check\n- **Reverse test:** read the chain from the bottom up with \"therefore\". Each step must follow from the one below.\n- **Stop test:** if the last answer is \"human error\", \"not enough time\" or \"bad luck\", ask why once more. These describe a missing safeguard, not a cause.\n- Mark any link still `hypothesis`; list how to verify it.\n\n### 3. Branch (only if causes split)\nWhen one \"why\" has several valid answers, follow each as its own chain. If the causes spread across many areas, group them under People, Process, Tools, Environment, Data or Measurement (a fishbone view) and chain the top two or three.\n\n### 4. Countermeasures\nFor each root cause:\n- **Contain:** stop the damage now.\n- **Fix:** remove the cause.\n- **Prevent:** a check or guardrail so it cannot recur.\n- **Owner and date**, or \"to be assigned\".\n\n## Pitfalls\n\n- Jumping to a favorite cause and filling the chain backward to justify it.\n- Asking \"who\" instead of \"why\". Blame ends the chain early; look for the missing safeguard.\n- Single-chain thinking on a complex failure. Branch when there are several causes.\n- Stopping at a cause nobody can change (for example \"the vendor was down\") without asking why there was no fallback.\n- Treating `hypothesis` rows as findings in the summary.\n\nWorked example: [references\u002Fexample.md](references\u002Fexample.md).\n\n## Checklist\n\n- [ ] Problem statement is observable (what, where, when, impact)\n- [ ] Each why answers the previous answer; each row is `verified` or `hypothesis`\n- [ ] Reverse test passed; no chain ends at \"human error\"\n- [ ] Branches followed where causes split\n- [ ] Countermeasures cover contain, fix, prevent, with owners\n",{"name":5,"license":15,"metadata":40,"description":43},{"author":41,"version":42},"ysskrishna","2026.10.5","Use for the 5 Whys, or when the user wants the root cause of a failure: \"why did this happen?\", \"this keeps breaking\", \"write the postmortem\", \"find the real cause\". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.\n","main","24a7abce3166736a5a1a7d573aa3cce3842d96c8","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffive-whys",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add davila7\u002Fclaude-code-templates --skill five-whys",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill five-whys",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill five-whys","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffive-whys\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fexample.md","REFERENCE","参考文档",1727,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffive-whys\u002Freferences\u002Fexample.md",[75,103,130,163,198,222],{"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":86,"publishedAt":35},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,31,92,93,25,33,94,27,95,96,97,98,99,100,101,102],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":35},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[109],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[111,112,113,114,115,116,117,118,119,120,121,33,122,123,124,125,126,127,128,129],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":145,"publishedAt":35},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[136,139,140],{"categoryNo":137,"categoryName":138,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[146,147,148,149,150,151,152,31,153,154,155,156,157,158,159,25,160,161,33,162],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":167,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":35},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",[175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,31,197],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":167,"licenseFileUrl":202,"sourceHtmlUrl":203,"categories":204,"keywords":209,"publishedAt":35},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[205,208],{"categoryNo":206,"categoryName":207,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":172,"categoryName":173,"taxonomyType":84,"taxonomyTypeDesc":85},[210,211,212,213,214,176,215,185,186,216,217,218,219,31,220,27,221],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":167,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":236,"publishedAt":35},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[229,232,233],{"categoryNo":230,"categoryName":231,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":234,"categoryName":235,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000036","内容创作者",[237,238,239,240,241,242,243,244,178,245,188,122,246,247,248,249,250,158,251,33,252,253,254,255,256,100,257],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]