[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEJWV89VC3XYSCC3QSKCW9":3,"skill-same:01M6AEJWV89VC3XYSCC3QSKCW9":98},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6AEJWV89VC3XYSCC3QSKCW9","git-commit-helper",null,"Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.","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\u002Fgit-commit-helper\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"commit","git commit","commit helper","git","helper","git commit helper","Bash","when","for","message","Echo","log","diff","command","commit messages","writing","analyzing","messages","commit message","help","generate","diffs","2026-11-10 10:12:30",false,"---\nname: git-commit-helper\ndescription: Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.\nhooks:\n  PostToolUse:\n    - matcher: \"Bash\"\n      hooks:\n        - type: command\n          command: \"echo \\\"[$(date)] Git Commit Helper: Analyzed git diff for commit message\\\" >> ~\u002F.claude\u002Fgit-commit-helper.log\"\n---\n\n# Git Commit Helper\n\n## Quick start\n\nAnalyze staged changes and generate commit message:\n\n```bash\n# View staged changes\ngit diff --staged\n\n# Generate commit message based on changes\n# (Claude will analyze the diff and suggest a message)\n```\n\n## Commit message format\n\nFollow conventional commits format:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n```\n\n### Types\n\n- **feat**: New feature\n- **fix**: Bug fix\n- **docs**: Documentation changes\n- **style**: Code style changes (formatting, missing semicolons)\n- **refactor**: Code refactoring\n- **test**: Adding or updating tests\n- **chore**: Maintenance tasks\n\n### Examples\n\n**Feature commit:**\n```\nfeat(auth): add JWT authentication\n\nImplement JWT-based authentication system with:\n- Login endpoint with token generation\n- Token validation middleware\n- Refresh token support\n```\n\n**Bug fix:**\n```\nfix(api): handle null values in user profile\n\nPrevent crashes when user profile fields are null.\nAdd null checks before accessing nested properties.\n```\n\n**Refactor:**\n```\nrefactor(database): simplify query builder\n\nExtract common query patterns into reusable functions.\nReduce code duplication in database layer.\n```\n\n## Analyzing changes\n\nReview what's being committed:\n\n```bash\n# Show files changed\ngit status\n\n# Show detailed changes\ngit diff --staged\n\n# Show statistics\ngit diff --staged --stat\n\n# Show changes for specific file\ngit diff --staged path\u002Fto\u002Ffile\n```\n\n## Commit message guidelines\n\n**DO:**\n- Use imperative mood (\"add feature\" not \"added feature\")\n- Keep first line under 50 characters\n- Capitalize first letter\n- No period at end of summary\n- Explain WHY not just WHAT in body\n\n**DON'T:**\n- Use vague messages like \"update\" or \"fix stuff\"\n- Include technical implementation details in summary\n- Write paragraphs in summary line\n- Use past tense\n\n## Multi-file commits\n\nWhen committing multiple related changes:\n\n```\nrefactor(core): restructure authentication module\n\n- Move auth logic from controllers to service layer\n- Extract validation into separate validators\n- Update tests to use new structure\n- Add integration tests for auth flow\n\nBreaking change: Auth service now requires config object\n```\n\n## Scope examples\n\n**Frontend:**\n- `feat(ui): add loading spinner to dashboard`\n- `fix(form): validate email format`\n\n**Backend:**\n- `feat(api): add user profile endpoint`\n- `fix(db): resolve connection pool leak`\n\n**Infrastructure:**\n- `chore(ci): update Node version to 20`\n- `feat(docker): add multi-stage build`\n\n## Breaking changes\n\nIndicate breaking changes clearly:\n\n```\nfeat(api)!: restructure API response format\n\nBREAKING CHANGE: All API responses now follow JSON:API spec\n\nPrevious format:\n{ \"data\": {...}, \"status\": \"ok\" }\n\nNew format:\n{ \"data\": {...}, \"meta\": {...} }\n\nMigration guide: Update client code to handle new response structure\n```\n\n## Template workflow\n\n1. **Review changes**: `git diff --staged`\n2. **Identify type**: Is it feat, fix, refactor, etc.?\n3. **Determine scope**: What part of the codebase?\n4. **Write summary**: Brief, imperative description\n5. **Add body**: Explain why and what impact\n6. **Note breaking changes**: If applicable\n\n## Interactive commit helper\n\nUse `git add -p` for selective staging:\n\n```bash\n# Stage changes interactively\ngit add -p\n\n# Review what's staged\ngit diff --staged\n\n# Commit with message\ngit commit -m \"type(scope): description\"\n```\n\n## Amending commits\n\nFix the last commit message:\n\n```bash\n# Amend commit message only\ngit commit --amend\n\n# Amend and add more changes\ngit add forgotten-file.js\ngit commit --amend --no-edit\n```\n\n## Best practices\n\n1. **Atomic commits** - One logical change per commit\n2. **Test before commit** - Ensure code works\n3. **Reference issues** - Include issue numbers if applicable\n4. **Keep it focused** - Don't mix unrelated changes\n5. **Write for humans** - Future you will read this\n\n## Commit message checklist\n\n- [ ] Type is appropriate (feat\u002Ffix\u002Fdocs\u002Fetc.)\n- [ ] Scope is specific and clear\n- [ ] Summary is under 50 characters\n- [ ] Summary uses imperative mood\n- [ ] Body explains WHY not just WHAT\n- [ ] Breaking changes are clearly marked\n- [ ] Related issue numbers are included\n","# Git Commit Helper\n\n## Quick start\n\nAnalyze staged changes and generate commit message:\n\n```bash\n# View staged changes\ngit diff --staged\n\n# Generate commit message based on changes\n# (Claude will analyze the diff and suggest a message)\n```\n\n## Commit message format\n\nFollow conventional commits format:\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer]\n```\n\n### Types\n\n- **feat**: New feature\n- **fix**: Bug fix\n- **docs**: Documentation changes\n- **style**: Code style changes (formatting, missing semicolons)\n- **refactor**: Code refactoring\n- **test**: Adding or updating tests\n- **chore**: Maintenance tasks\n\n### Examples\n\n**Feature commit:**\n```\nfeat(auth): add JWT authentication\n\nImplement JWT-based authentication system with:\n- Login endpoint with token generation\n- Token validation middleware\n- Refresh token support\n```\n\n**Bug fix:**\n```\nfix(api): handle null values in user profile\n\nPrevent crashes when user profile fields are null.\nAdd null checks before accessing nested properties.\n```\n\n**Refactor:**\n```\nrefactor(database): simplify query builder\n\nExtract common query patterns into reusable functions.\nReduce code duplication in database layer.\n```\n\n## Analyzing changes\n\nReview what's being committed:\n\n```bash\n# Show files changed\ngit status\n\n# Show detailed changes\ngit diff --staged\n\n# Show statistics\ngit diff --staged --stat\n\n# Show changes for specific file\ngit diff --staged path\u002Fto\u002Ffile\n```\n\n## Commit message guidelines\n\n**DO:**\n- Use imperative mood (\"add feature\" not \"added feature\")\n- Keep first line under 50 characters\n- Capitalize first letter\n- No period at end of summary\n- Explain WHY not just WHAT in body\n\n**DON'T:**\n- Use vague messages like \"update\" or \"fix stuff\"\n- Include technical implementation details in summary\n- Write paragraphs in summary line\n- Use past tense\n\n## Multi-file commits\n\nWhen committing multiple related changes:\n\n```\nrefactor(core): restructure authentication module\n\n- Move auth logic from controllers to service layer\n- Extract validation into separate validators\n- Update tests to use new structure\n- Add integration tests for auth flow\n\nBreaking change: Auth service now requires config object\n```\n\n## Scope examples\n\n**Frontend:**\n- `feat(ui): add loading spinner to dashboard`\n- `fix(form): validate email format`\n\n**Backend:**\n- `feat(api): add user profile endpoint`\n- `fix(db): resolve connection pool leak`\n\n**Infrastructure:**\n- `chore(ci): update Node version to 20`\n- `feat(docker): add multi-stage build`\n\n## Breaking changes\n\nIndicate breaking changes clearly:\n\n```\nfeat(api)!: restructure API response format\n\nBREAKING CHANGE: All API responses now follow JSON:API spec\n\nPrevious format:\n{ \"data\": {...}, \"status\": \"ok\" }\n\nNew format:\n{ \"data\": {...}, \"meta\": {...} }\n\nMigration guide: Update client code to handle new response structure\n```\n\n## Template workflow\n\n1. **Review changes**: `git diff --staged`\n2. **Identify type**: Is it feat, fix, refactor, etc.?\n3. **Determine scope**: What part of the codebase?\n4. **Write summary**: Brief, imperative description\n5. **Add body**: Explain why and what impact\n6. **Note breaking changes**: If applicable\n\n## Interactive commit helper\n\nUse `git add -p` for selective staging:\n\n```bash\n# Stage changes interactively\ngit add -p\n\n# Review what's staged\ngit diff --staged\n\n# Commit with message\ngit commit -m \"type(scope): description\"\n```\n\n## Amending commits\n\nFix the last commit message:\n\n```bash\n# Amend commit message only\ngit commit --amend\n\n# Amend and add more changes\ngit add forgotten-file.js\ngit commit --amend --no-edit\n```\n\n## Best practices\n\n1. **Atomic commits** - One logical change per commit\n2. **Test before commit** - Ensure code works\n3. **Reference issues** - Include issue numbers if applicable\n4. **Keep it focused** - Don't mix unrelated changes\n5. **Write for humans** - Future you will read this\n\n## Commit message checklist\n\n- [ ] Type is appropriate (feat\u002Ffix\u002Fdocs\u002Fetc.)\n- [ ] Scope is specific and clear\n- [ ] Summary is under 50 characters\n- [ ] Summary uses imperative mood\n- [ ] Body explains WHY not just WHAT\n- [ ] Breaking changes are clearly marked\n- [ ] Related issue numbers are included\n",{"name":5,"hooks":46,"description":7},{"PostToolUse":47},[48],{"hooks":49,"matcher":25},[50],{"type":32,"command":51},"echo \"[$(date)] Git Commit Helper: Analyzed git diff for commit message\" >> ~\u002F.claude\u002Fgit-commit-helper.log","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgit-commit-helper",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add davila7\u002Fclaude-code-templates --skill git-commit-helper",{"tool":68,"command":69},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill git-commit-helper",{"tool":71,"command":72},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill git-commit-helper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgit-commit-helper\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Ffilters_preprocessing.md","REFERENCE","参考文档",12700,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhistolab\u002Freferences\u002Ffilters_preprocessing.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fslide_management.md",4701,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhistolab\u002Freferences\u002Fslide_management.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ftile_extraction.md",11297,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhistolab\u002Freferences\u002Ftile_extraction.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Ftissue_masks.md",7232,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhistolab\u002Freferences\u002Ftissue_masks.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fvisualization.md",13970,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhistolab\u002Freferences\u002Fvisualization.md",[99,129,156,189,224,248],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":110,"publishedAt":41},"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",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[111,112,113,114,115,27,116,117,118,26,119,120,121,122,123,124,125,126,127,128],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":41},"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",[135],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},[137,138,139,140,141,142,143,144,145,146,147,26,148,149,150,151,152,153,154,155],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":171,"publishedAt":41},"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",[162,165,166],{"categoryNo":163,"categoryName":164,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[172,173,174,175,176,177,178,27,179,180,181,182,183,184,185,118,186,187,26,188],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":200,"publishedAt":41},"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",[197],{"categoryNo":198,"categoryName":199,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000009","前端开发",[201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,27,223],"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":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":228,"sourceHtmlUrl":229,"categories":230,"keywords":235,"publishedAt":41},"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",[231,234],{"categoryNo":232,"categoryName":233,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":198,"categoryName":199,"taxonomyType":108,"taxonomyTypeDesc":109},[236,237,238,239,240,202,241,211,212,242,243,244,245,27,246,120,247],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":252,"sourceHtmlUrl":253,"categories":254,"keywords":262,"publishedAt":41},"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",[255,258,259],{"categoryNo":256,"categoryName":257,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},{"categoryNo":260,"categoryName":261,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000036","内容创作者",[263,264,265,38,266,267,268,34,204,269,214,148,270,271,272,273,274,184,275,26,276,277,278,279,280,126,281],"discernment nudge","nudge","interpretation","run","reasoning","data","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]