[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEGE8GHB6FCPPQPMAW4PNE":3,"skill-same:01M6AEGE8GHB6FCPPQPMAW4PNE":66},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6AEGE8GHB6FCPPQPMAW4PNE","create-plan",null,"Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.","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\u002Fdevelopment\u002Fcreate-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"create","create plan","plan","coding","user","use","task","concise","for","when","2026-11-10 10:12:30",false,"---\nname: create-plan\ndescription: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.\nmetadata:\n  short-description: Create a plan\n---\n\n# Create Plan\n\n## Goal\n\nTurn a user prompt into a **single, actionable plan** delivered in the final assistant message.\n\n## Minimal workflow\n\nThroughout the entire workflow, operate in read-only mode. Do not write or update files.\n\n1. **Scan context quickly**\n   - Read `README.md` and any obvious docs (`docs\u002F`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).\n   - Skim relevant files (the ones most likely touched).\n   - Identify constraints (language, frameworks, CI\u002Ftest commands, deployment shape).\n\n2. **Ask follow-ups only if blocking**\n   - Ask **at most 1–2 questions**.\n   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.\n   - If unsure but not blocked, make a reasonable assumption and proceed.\n\n3. **Create a plan using the template below**\n   - Start with **1 short paragraph** describing the intent and approach.\n   - Clearly call out what is **in scope** and what is **not in scope** in short.\n   - Then provide a **small checklist** of action items (default 6–10 items).\n      - Each checklist item should be a concrete action and, when helpful, mention files\u002Fcommands.\n      - **Make items atomic and ordered**: discovery → changes → tests → rollout.\n      - **Verb-first**: \"Add…\", \"Refactor…\", \"Verify…\", \"Ship…\".\n   - Include at least one item for **tests\u002Fvalidation** and one for **edge cases\u002Frisk** when applicable.\n   - If there are unknowns, include a tiny **Open questions** section (max 3).\n\n4. **Do not preface the plan with meta explanations; output only the plan as per template**\n\n## Plan template (follow exactly)\n\n```markdown\n# Plan\n\n\u003C1–3 sentences: what we're doing, why, and the high-level approach.>\n\n## Scope\n- In:\n- Out:\n\n## Action items\n[ ] \u003CStep 1>\n[ ] \u003CStep 2>\n[ ] \u003CStep 3>\n[ ] \u003CStep 4>\n[ ] \u003CStep 5>\n[ ] \u003CStep 6>\n\n## Open questions\n- \u003CQuestion 1>\n- \u003CQuestion 2>\n- \u003CQuestion 3>\n```\n\n## Checklist item guidance\nGood checklist items:\n- Point to likely files\u002Fmodules: src\u002F..., app\u002F..., services\u002F...\n- Name concrete validation: \"Run npm test\", \"Add unit tests for X\"\n- Include safe rollout when relevant: feature flag, migration plan, rollback note\n\nAvoid:\n- Vague steps (\"handle backend\", \"do auth\")\n- Too many micro-steps\n- Writing code snippets (keep the plan implementation-agnostic)\n","# Create Plan\n\n## Goal\n\nTurn a user prompt into a **single, actionable plan** delivered in the final assistant message.\n\n## Minimal workflow\n\nThroughout the entire workflow, operate in read-only mode. Do not write or update files.\n\n1. **Scan context quickly**\n   - Read `README.md` and any obvious docs (`docs\u002F`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).\n   - Skim relevant files (the ones most likely touched).\n   - Identify constraints (language, frameworks, CI\u002Ftest commands, deployment shape).\n\n2. **Ask follow-ups only if blocking**\n   - Ask **at most 1–2 questions**.\n   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.\n   - If unsure but not blocked, make a reasonable assumption and proceed.\n\n3. **Create a plan using the template below**\n   - Start with **1 short paragraph** describing the intent and approach.\n   - Clearly call out what is **in scope** and what is **not in scope** in short.\n   - Then provide a **small checklist** of action items (default 6–10 items).\n      - Each checklist item should be a concrete action and, when helpful, mention files\u002Fcommands.\n      - **Make items atomic and ordered**: discovery → changes → tests → rollout.\n      - **Verb-first**: \"Add…\", \"Refactor…\", \"Verify…\", \"Ship…\".\n   - Include at least one item for **tests\u002Fvalidation** and one for **edge cases\u002Frisk** when applicable.\n   - If there are unknowns, include a tiny **Open questions** section (max 3).\n\n4. **Do not preface the plan with meta explanations; output only the plan as per template**\n\n## Plan template (follow exactly)\n\n```markdown\n# Plan\n\n\u003C1–3 sentences: what we're doing, why, and the high-level approach.>\n\n## Scope\n- In:\n- Out:\n\n## Action items\n[ ] \u003CStep 1>\n[ ] \u003CStep 2>\n[ ] \u003CStep 3>\n[ ] \u003CStep 4>\n[ ] \u003CStep 5>\n[ ] \u003CStep 6>\n\n## Open questions\n- \u003CQuestion 1>\n- \u003CQuestion 2>\n- \u003CQuestion 3>\n```\n\n## Checklist item guidance\nGood checklist items:\n- Point to likely files\u002Fmodules: src\u002F..., app\u002F..., services\u002F...\n- Name concrete validation: \"Run npm test\", \"Add unit tests for X\"\n- Include safe rollout when relevant: feature flag, migration plan, rollback note\n\nAvoid:\n- Vague steps (\"handle backend\", \"do auth\")\n- Too many micro-steps\n- Writing code snippets (keep the plan implementation-agnostic)\n",{"name":5,"metadata":34,"description":7},{"short-description":35},"Create a plan","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcreate-plan",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add davila7\u002Fclaude-code-templates --skill create-plan",{"tool":52,"command":53},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill create-plan",{"tool":55,"command":56},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill create-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcreate-plan\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fapi_reference.md","REFERENCE","参考文档",13339,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fena-database\u002Freferences\u002Fapi_reference.md",[67,96,122,155,190,214],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":29},"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,80,81,82,83,27,84,85,24,28,86,87,88,89,90,91,92,93,94,95],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":29},"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",[102],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},[104,105,106,107,108,109,110,111,112,113,114,28,115,116,117,21,118,119,120,121],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","focus","signals","audit","dependency",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":137,"publishedAt":29},"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",[128,131,132],{"categoryNo":129,"categoryName":130,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[138,139,140,141,142,143,144,27,145,146,147,148,149,150,151,24,152,153,28,154],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":159,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":29},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000009","前端开发",[167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,27,189],"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":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":159,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":201,"publishedAt":29},"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",[197,200],{"categoryNo":198,"categoryName":199,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":164,"categoryName":165,"taxonomyType":76,"taxonomyTypeDesc":77},[202,203,204,205,206,168,207,177,178,208,209,210,211,27,212,87,213],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":159,"licenseFileUrl":218,"sourceHtmlUrl":219,"categories":220,"keywords":228,"publishedAt":29},"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",[221,224,225],{"categoryNo":222,"categoryName":223,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":226,"categoryName":227,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000036","内容创作者",[229,230,231,232,233,234,235,236,170,237,180,115,238,239,240,241,242,150,243,28,244,245,246,247,248,93,249],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]