[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEB378Z2Q0WWCG1SPHK6BK":3,"skill-same:01M6AEB378Z2Q0WWCG1SPHK6BK":82},{"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":26,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6AEB378Z2Q0WWCG1SPHK6BK","agent-md-refactor",null,"Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.","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\u002Fagent-md-refactor\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34],"refactor","agent md refactor","documentation","files","monolithic","principles","splits","progressive disclosure","2026-11-10 10:12:30",false,"---\nname: agent-md-refactor\ndescription: Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.\nlicense: MIT\n---\n\n# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n","# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n",{"name":5,"license":15,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add davila7\u002Fclaude-code-templates --skill agent-md-refactor",{"tool":56,"command":57},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill agent-md-refactor",{"tool":59,"command":60},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill agent-md-refactor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor\u002FSKILL.md",true,[64,70,74,78],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",282,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-mvp-designer\u002Fagents\u002Fopenai.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"README.md",7326,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fagent-md-refactor\u002FREADME.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fexperiment-template.md",159,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-mvp-designer\u002Freferences\u002Fexperiment-template.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fmvp-patterns.md",256,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-mvp-designer\u002Freferences\u002Fmvp-patterns.md",[83,111,138,171,206,230],{"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":90,"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",[89],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"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",[117],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,125,126,127,128,129,100,130,131,132,133,134,135,136,137],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":153,"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",[144,147,148],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[154,155,156,157,158,159,160,96,161,162,163,164,165,166,167,99,168,169,100,170],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":182,"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",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,96,205],"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":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":217,"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",[213,216],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,220,221,222,184,223,193,194,224,225,226,227,96,228,102,229],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":234,"sourceHtmlUrl":235,"categories":236,"keywords":244,"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",[237,240,241],{"categoryNo":238,"categoryName":239,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":242,"categoryName":243,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000036","内容创作者",[245,246,247,248,249,250,251,252,186,253,196,130,254,255,256,257,258,166,259,100,260,261,262,263,264,108,265],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]