[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEFVRE9V5PSX8Y3ESV5HN8":3,"skill-same:01M6AEFVRE9V5PSX8Y3ESV5HN8":91},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6AEFVRE9V5PSX8Y3ESV5HN8","command-creator",null,"This skill should be used when creating a Claude Code slash command. Use when users ask to \"create a command\", \"make a slash command\", \"add a command\", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.","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\u002Fcommand-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"creator","command creator","command","structure","when","for","make","users","add","as","essential","commands","workflow","document","reusable","use","ask","best practices","code","create","2026-11-10 10:12:30",false,"---\nname: command-creator\ndescription: This skill should be used when creating a Claude Code slash command. Use when users ask to \"create a command\", \"make a slash command\", \"add a command\", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.\n---\n\n# Command Creator\n\nThis skill guides the creation of Claude Code slash commands - reusable workflows that can be invoked with `\u002Fcommand-name` in Claude Code conversations.\n\n## About Slash Commands\n\nSlash commands are markdown files stored in `.claude\u002Fcommands\u002F` (project-level) or `~\u002F.claude\u002Fcommands\u002F` (global\u002Fuser-level) that get expanded into prompts when invoked. They're ideal for:\n\n- Repetitive workflows (code review, PR submission, CI fixing)\n- Multi-step processes that need consistency\n- Agent delegation patterns\n- Project-specific automation\n\n## When to Use This Skill\n\nInvoke this skill when users:\n\n- Ask to \"create a command\" or \"make a slash command\"\n- Want to automate a repetitive workflow\n- Need to document a consistent process for reuse\n- Say \"I keep doing X, can we make a command for it?\"\n- Want to create project-specific or global commands\n\n## Bundled Resources\n\nThis skill includes reference documentation for detailed guidance:\n\n- **references\u002Fpatterns.md** - Command patterns (workflow automation, iterative fixing, agent delegation, simple execution)\n- **references\u002Fexamples.md** - Real command examples with full source (submit-stack, ensure-ci, create-implementation-plan)\n- **references\u002Fbest-practices.md** - Quality checklist, common pitfalls, writing guidelines, template structure\n\nLoad these references as needed when creating commands to understand patterns, see examples, or ensure quality.\n\n## Command Structure Overview\n\nEvery slash command is a markdown file with:\n\n```markdown\n---\ndescription: Brief description shown in \u002Fhelp (required)\nargument-hint: \u003Cplaceholder> (optional, if command takes arguments)\n---\n\n# Command Title\n\n[Detailed instructions for the agent to execute autonomously]\n```\n\n## Command Creation Workflow\n\n### Step 1: Determine Location\n\n**Auto-detect the appropriate location:**\n\n1. Check git repository status: `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n2. Default location:\n   - If in git repo → Project-level: `.claude\u002Fcommands\u002F`\n   - If not in git repo → Global: `~\u002F.claude\u002Fcommands\u002F`\n3. Allow user override:\n   - If user explicitly mentions \"global\" or \"user-level\" → Use `~\u002F.claude\u002Fcommands\u002F`\n   - If user explicitly mentions \"project\" or \"project-level\" → Use `.claude\u002Fcommands\u002F`\n\nReport the chosen location to the user before proceeding.\n\n### Step 2: Show Command Patterns\n\nHelp the user understand different command types. Load **references\u002Fpatterns.md** to see available patterns:\n\n- **Workflow Automation** - Analyze → Act → Report (e.g., submit-stack)\n- **Iterative Fixing** - Run → Parse → Fix → Repeat (e.g., ensure-ci)\n- **Agent Delegation** - Context → Delegate → Iterate (e.g., create-implementation-plan)\n- **Simple Execution** - Run command with args (e.g., codex-review)\n\nAsk the user: \"Which pattern is closest to what you want to create?\" This helps frame the conversation.\n\n### Step 3: Gather Command Information\n\nAsk the user for key information:\n\n#### A. Command Name and Purpose\n\nAsk:\n\n- \"What should the command be called?\" (for filename)\n- \"What does this command do?\" (for description field)\n\nGuidelines:\n\n- Command names MUST be kebab-case (hyphens, NOT underscores)\n  - ✅ CORRECT: `submit-stack`, `ensure-ci`, `create-from-plan`\n  - ❌ WRONG: `submit_stack`, `ensure_ci`, `create_from_plan`\n- File names match command names: `my-command.md` → invoked as `\u002Fmy-command`\n- Description should be concise, action-oriented (appears in `\u002Fhelp` output)\n\n#### B. Arguments\n\nAsk:\n\n- \"Does this command take any arguments?\"\n- \"Are arguments required or optional?\"\n- \"What should arguments represent?\"\n\nIf command takes arguments:\n\n- Add `argument-hint: \u003Cplaceholder>` to frontmatter\n- Use `\u003Cangle-brackets>` for required arguments\n- Use `[square-brackets]` for optional arguments\n\n#### C. Workflow Steps\n\nAsk:\n\n- \"What are the specific steps this command should follow?\"\n- \"What order should they happen in?\"\n- \"What tools or commands should be used?\"\n\nGather details about:\n\n- Initial analysis or checks to perform\n- Main actions to take\n- How to handle results\n- Success criteria\n- Error handling approach\n\n#### D. Tool Restrictions and Guidance\n\nAsk:\n\n- \"Should this command use any specific agents or tools?\"\n- \"Are there any tools or operations it should avoid?\"\n- \"Should it read any specific files for context?\"\n\n### Step 4: Generate Optimized Command\n\nCreate the command file with agent-optimized instructions. Load **references\u002Fbest-practices.md** for:\n\n- Template structure\n- Best practices for agent execution\n- Writing style guidelines\n- Quality checklist\n\nKey principles:\n\n- Use imperative\u002Finfinitive form (verb-first instructions)\n- Be explicit and specific\n- Include expected outcomes\n- Provide concrete examples\n- Define clear error handling\n\n### Step 5: Create the Command File\n\n1. Determine full file path:\n   - Project: `.claude\u002Fcommands\u002F[command-name].md`\n   - Global: `~\u002F.claude\u002Fcommands\u002F[command-name].md`\n\n2. Ensure directory exists:\n\n   ```bash\n   mkdir -p [directory-path]\n   ```\n\n3. Write the command file using the Write tool\n\n4. Confirm with user:\n   - Report the file location\n   - Summarize what the command does\n   - Explain how to use it: `\u002Fcommand-name [arguments]`\n\n### Step 6: Test and Iterate (Optional)\n\nIf the user wants to test:\n\n1. Suggest testing: `You can test this command by running: \u002Fcommand-name [arguments]`\n2. Be ready to iterate based on feedback\n3. Update the file with improvements as needed\n\n## Quick Tips\n\n**For detailed guidance, load the bundled references:**\n\n- Load **references\u002Fpatterns.md** when designing the command workflow\n- Load **references\u002Fexamples.md** to see how existing commands are structured\n- Load **references\u002Fbest-practices.md** before finalizing to ensure quality\n\n**Common patterns to remember:**\n\n- Use Bash tool for `pytest`, `pyright`, `ruff`, `prettier`, `make`, `gt` commands\n- Use Task tool to invoke subagents for specialized tasks\n- Check for specific files first (e.g., `.PLAN.md`) before proceeding\n- Mark todos complete immediately, not in batches\n- Include explicit error handling instructions\n- Define clear success criteria\n\n## Summary\n\nWhen creating a command:\n\n1. **Detect location** (project vs global)\n2. **Show patterns** to frame the conversation\n3. **Gather information** (name, purpose, arguments, steps, tools)\n4. **Generate optimized command** with agent-executable instructions\n5. **Create file** at appropriate location\n6. **Confirm and iterate** as needed\n\nFocus on creating commands that agents can execute autonomously, with clear steps, explicit tool usage, and proper error handling.\n","# Command Creator\n\nThis skill guides the creation of Claude Code slash commands - reusable workflows that can be invoked with `\u002Fcommand-name` in Claude Code conversations.\n\n## About Slash Commands\n\nSlash commands are markdown files stored in `.claude\u002Fcommands\u002F` (project-level) or `~\u002F.claude\u002Fcommands\u002F` (global\u002Fuser-level) that get expanded into prompts when invoked. They're ideal for:\n\n- Repetitive workflows (code review, PR submission, CI fixing)\n- Multi-step processes that need consistency\n- Agent delegation patterns\n- Project-specific automation\n\n## When to Use This Skill\n\nInvoke this skill when users:\n\n- Ask to \"create a command\" or \"make a slash command\"\n- Want to automate a repetitive workflow\n- Need to document a consistent process for reuse\n- Say \"I keep doing X, can we make a command for it?\"\n- Want to create project-specific or global commands\n\n## Bundled Resources\n\nThis skill includes reference documentation for detailed guidance:\n\n- **references\u002Fpatterns.md** - Command patterns (workflow automation, iterative fixing, agent delegation, simple execution)\n- **references\u002Fexamples.md** - Real command examples with full source (submit-stack, ensure-ci, create-implementation-plan)\n- **references\u002Fbest-practices.md** - Quality checklist, common pitfalls, writing guidelines, template structure\n\nLoad these references as needed when creating commands to understand patterns, see examples, or ensure quality.\n\n## Command Structure Overview\n\nEvery slash command is a markdown file with:\n\n```markdown\n---\ndescription: Brief description shown in \u002Fhelp (required)\nargument-hint: \u003Cplaceholder> (optional, if command takes arguments)\n---\n\n# Command Title\n\n[Detailed instructions for the agent to execute autonomously]\n```\n\n## Command Creation Workflow\n\n### Step 1: Determine Location\n\n**Auto-detect the appropriate location:**\n\n1. Check git repository status: `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n2. Default location:\n   - If in git repo → Project-level: `.claude\u002Fcommands\u002F`\n   - If not in git repo → Global: `~\u002F.claude\u002Fcommands\u002F`\n3. Allow user override:\n   - If user explicitly mentions \"global\" or \"user-level\" → Use `~\u002F.claude\u002Fcommands\u002F`\n   - If user explicitly mentions \"project\" or \"project-level\" → Use `.claude\u002Fcommands\u002F`\n\nReport the chosen location to the user before proceeding.\n\n### Step 2: Show Command Patterns\n\nHelp the user understand different command types. Load **references\u002Fpatterns.md** to see available patterns:\n\n- **Workflow Automation** - Analyze → Act → Report (e.g., submit-stack)\n- **Iterative Fixing** - Run → Parse → Fix → Repeat (e.g., ensure-ci)\n- **Agent Delegation** - Context → Delegate → Iterate (e.g., create-implementation-plan)\n- **Simple Execution** - Run command with args (e.g., codex-review)\n\nAsk the user: \"Which pattern is closest to what you want to create?\" This helps frame the conversation.\n\n### Step 3: Gather Command Information\n\nAsk the user for key information:\n\n#### A. Command Name and Purpose\n\nAsk:\n\n- \"What should the command be called?\" (for filename)\n- \"What does this command do?\" (for description field)\n\nGuidelines:\n\n- Command names MUST be kebab-case (hyphens, NOT underscores)\n  - ✅ CORRECT: `submit-stack`, `ensure-ci`, `create-from-plan`\n  - ❌ WRONG: `submit_stack`, `ensure_ci`, `create_from_plan`\n- File names match command names: `my-command.md` → invoked as `\u002Fmy-command`\n- Description should be concise, action-oriented (appears in `\u002Fhelp` output)\n\n#### B. Arguments\n\nAsk:\n\n- \"Does this command take any arguments?\"\n- \"Are arguments required or optional?\"\n- \"What should arguments represent?\"\n\nIf command takes arguments:\n\n- Add `argument-hint: \u003Cplaceholder>` to frontmatter\n- Use `\u003Cangle-brackets>` for required arguments\n- Use `[square-brackets]` for optional arguments\n\n#### C. Workflow Steps\n\nAsk:\n\n- \"What are the specific steps this command should follow?\"\n- \"What order should they happen in?\"\n- \"What tools or commands should be used?\"\n\nGather details about:\n\n- Initial analysis or checks to perform\n- Main actions to take\n- How to handle results\n- Success criteria\n- Error handling approach\n\n#### D. Tool Restrictions and Guidance\n\nAsk:\n\n- \"Should this command use any specific agents or tools?\"\n- \"Are there any tools or operations it should avoid?\"\n- \"Should it read any specific files for context?\"\n\n### Step 4: Generate Optimized Command\n\nCreate the command file with agent-optimized instructions. Load **references\u002Fbest-practices.md** for:\n\n- Template structure\n- Best practices for agent execution\n- Writing style guidelines\n- Quality checklist\n\nKey principles:\n\n- Use imperative\u002Finfinitive form (verb-first instructions)\n- Be explicit and specific\n- Include expected outcomes\n- Provide concrete examples\n- Define clear error handling\n\n### Step 5: Create the Command File\n\n1. Determine full file path:\n   - Project: `.claude\u002Fcommands\u002F[command-name].md`\n   - Global: `~\u002F.claude\u002Fcommands\u002F[command-name].md`\n\n2. Ensure directory exists:\n\n   ```bash\n   mkdir -p [directory-path]\n   ```\n\n3. Write the command file using the Write tool\n\n4. Confirm with user:\n   - Report the file location\n   - Summarize what the command does\n   - Explain how to use it: `\u002Fcommand-name [arguments]`\n\n### Step 6: Test and Iterate (Optional)\n\nIf the user wants to test:\n\n1. Suggest testing: `You can test this command by running: \u002Fcommand-name [arguments]`\n2. Be ready to iterate based on feedback\n3. Update the file with improvements as needed\n\n## Quick Tips\n\n**For detailed guidance, load the bundled references:**\n\n- Load **references\u002Fpatterns.md** when designing the command workflow\n- Load **references\u002Fexamples.md** to see how existing commands are structured\n- Load **references\u002Fbest-practices.md** before finalizing to ensure quality\n\n**Common patterns to remember:**\n\n- Use Bash tool for `pytest`, `pyright`, `ruff`, `prettier`, `make`, `gt` commands\n- Use Task tool to invoke subagents for specialized tasks\n- Check for specific files first (e.g., `.PLAN.md`) before proceeding\n- Mark todos complete immediately, not in batches\n- Include explicit error handling instructions\n- Define clear success criteria\n\n## Summary\n\nWhen creating a command:\n\n1. **Detect location** (project vs global)\n2. **Show patterns** to frame the conversation\n3. **Gather information** (name, purpose, arguments, steps, tools)\n4. **Generate optimized command** with agent-executable instructions\n5. **Create file** at appropriate location\n6. **Confirm and iterate** as needed\n\nFocus on creating commands that agents can execute autonomously, with clear steps, explicit tool usage, and proper error handling.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add davila7\u002Fclaude-code-templates --skill command-creator",{"tool":65,"command":66},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill command-creator",{"tool":68,"command":69},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill command-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator\u002FSKILL.md",true,[73,79,83,87],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"README.md","REFERENCE","参考文档",15507,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator\u002FREADME.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fbest-practices.md",13806,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator\u002Freferences\u002Fbest-practices.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fexamples.md",15806,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator\u002Freferences\u002Fexamples.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fpatterns.md",9002,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fcommand-creator\u002Freferences\u002Fpatterns.md",[92,117,143,176,211,235],{"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":99,"publishedAt":44},"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",[98],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[100,101,102,103,104,29,105,106,39,28,107,108,109,110,111,112,113,114,115,116],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":44},"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",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127,128,129,130,131,132,133,134,135,28,42,136,137,138,139,140,141,142],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":158,"publishedAt":44},"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",[149,152,153],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[159,160,161,162,163,164,165,29,166,167,168,169,170,171,172,39,173,174,28,175],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":44},"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",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,29,210],"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":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":222,"publishedAt":44},"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",[218,221],{"categoryNo":219,"categoryName":220,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},[223,224,225,226,227,189,228,198,199,229,230,231,232,29,233,108,234],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":239,"sourceHtmlUrl":240,"categories":241,"keywords":249,"publishedAt":44},"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",[242,245,246],{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":247,"categoryName":248,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000036","内容创作者",[250,251,252,253,254,255,256,257,191,258,201,42,259,260,261,262,263,171,264,28,265,266,267,268,269,114,270],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]