[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADWN4GFACVYTPDTENM8DW1":3,"skill-same:01M6ADWN4GFACVYTPDTENM8DW1":86},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6ADWN4GFACVYTPDTENM8DW1","parallel-agents",null,"Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fparallel-agents\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],"parallel agents","parallel","use","when","expertise","can","with","multi","orchestration patterns","domain","patterns","agent orchestration","orchestration","read","perspectives","grep","multi-agent","analysis","run","tasks","2026-11-10 10:12:30",false,"---\nname: parallel-agents\ndescription: Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.\nallowed-tools: Read, Glob, Grep\n---\n\n# Native Parallel Agents\n\n> Orchestration through Claude Code's built-in Agent Tool\n\n## Overview\n\nThis skill enables coordinating multiple specialized agents through Claude Code's native agent system. Unlike external scripts, this approach keeps all orchestration within Claude's control.\n\n## When to Use Orchestration\n\n✅ **Good for:**\n- Complex tasks requiring multiple expertise domains\n- Code analysis from security, performance, and quality perspectives\n- Comprehensive reviews (architecture + security + testing)\n- Feature implementation needing backend + frontend + database work\n\n❌ **Not for:**\n- Simple, single-domain tasks\n- Quick fixes or small changes\n- Tasks where one agent suffices\n\n---\n\n## Native Agent Invocation\n\n### Single Agent\n```\nUse the security-auditor agent to review authentication\n```\n\n### Sequential Chain\n```\nFirst, use the explorer-agent to discover project structure.\nThen, use the backend-specialist to review API endpoints.\nFinally, use the test-engineer to identify test gaps.\n```\n\n### With Context Passing\n```\nUse the frontend-specialist to analyze React components.\nBased on those findings, have the test-engineer generate component tests.\n```\n\n### Resume Previous Work\n```\nResume agent [agentId] and continue with additional requirements.\n```\n\n---\n\n## Orchestration Patterns\n\n### Pattern 1: Comprehensive Analysis\n```\nAgents: explorer-agent → [domain-agents] → synthesis\n\n1. explorer-agent: Map codebase structure\n2. security-auditor: Security posture\n3. backend-specialist: API quality\n4. frontend-specialist: UI\u002FUX patterns\n5. test-engineer: Test coverage\n6. Synthesize all findings\n```\n\n### Pattern 2: Feature Review\n```\nAgents: affected-domain-agents → test-engineer\n\n1. Identify affected domains (backend? frontend? both?)\n2. Invoke relevant domain agents\n3. test-engineer verifies changes\n4. Synthesize recommendations\n```\n\n### Pattern 3: Security Audit\n```\nAgents: security-auditor → penetration-tester → synthesis\n\n1. security-auditor: Configuration and code review\n2. penetration-tester: Active vulnerability testing\n3. Synthesize with prioritized remediation\n```\n\n---\n\n## Available Agents\n\n| Agent | Expertise | Trigger Phrases |\n|-------|-----------|-----------------|\n| `orchestrator` | Coordination | \"comprehensive\", \"multi-perspective\" |\n| `security-auditor` | Security | \"security\", \"auth\", \"vulnerabilities\" |\n| `penetration-tester` | Security Testing | \"pentest\", \"red team\", \"exploit\" |\n| `backend-specialist` | Backend | \"API\", \"server\", \"Node.js\", \"Express\" |\n| `frontend-specialist` | Frontend | \"React\", \"UI\", \"components\", \"Next.js\" |\n| `test-engineer` | Testing | \"tests\", \"coverage\", \"TDD\" |\n| `devops-engineer` | DevOps | \"deploy\", \"CI\u002FCD\", \"infrastructure\" |\n| `database-architect` | Database | \"schema\", \"Prisma\", \"migrations\" |\n| `mobile-developer` | Mobile | \"React Native\", \"Flutter\", \"mobile\" |\n| `api-designer` | API Design | \"REST\", \"GraphQL\", \"OpenAPI\" |\n| `debugger` | Debugging | \"bug\", \"error\", \"not working\" |\n| `explorer-agent` | Discovery | \"explore\", \"map\", \"structure\" |\n| `documentation-writer` | Documentation | \"write docs\", \"create README\", \"generate API docs\" |\n| `performance-optimizer` | Performance | \"slow\", \"optimize\", \"profiling\" |\n| `project-planner` | Planning | \"plan\", \"roadmap\", \"milestones\" |\n| `seo-specialist` | SEO | \"SEO\", \"meta tags\", \"search ranking\" |\n| `game-developer` | Game Development | \"game\", \"Unity\", \"Godot\", \"Phaser\" |\n\n---\n\n## Claude Code Built-in Agents\n\nThese work alongside custom agents:\n\n| Agent | Model | Purpose |\n|-------|-------|---------|\n| **Explore** | Haiku | Fast read-only codebase search |\n| **Plan** | Sonnet | Research during plan mode |\n| **General-purpose** | Sonnet | Complex multi-step modifications |\n\nUse **Explore** for quick searches, **custom agents** for domain expertise.\n\n---\n\n## Synthesis Protocol\n\nAfter all agents complete, synthesize:\n\n```markdown\n## Orchestration Synthesis\n\n### Task Summary\n[What was accomplished]\n\n### Agent Contributions\n| Agent | Finding |\n|-------|---------|\n| security-auditor | Found X |\n| backend-specialist | Identified Y |\n\n### Consolidated Recommendations\n1. **Critical**: [Issue from Agent A]\n2. **Important**: [Issue from Agent B]\n3. **Nice-to-have**: [Enhancement from Agent C]\n\n### Action Items\n- [ ] Fix critical security issue\n- [ ] Refactor API endpoint\n- [ ] Add missing tests\n```\n\n---\n\n## Best Practices\n\n1. **Available agents** - 17 specialized agents can be orchestrated\n2. **Logical order** - Discovery → Analysis → Implementation → Testing\n3. **Share context** - Pass relevant findings to subsequent agents\n4. **Single synthesis** - One unified report, not separate outputs\n5. **Verify changes** - Always include test-engineer for code modifications\n\n---\n\n## Key Benefits\n\n- ✅ **Single session** - All agents share context\n- ✅ **AI-controlled** - Claude orchestrates autonomously\n- ✅ **Native integration** - Works with built-in Explore, Plan agents\n- ✅ **Resume support** - Can continue previous agent work\n- ✅ **Context passing** - Findings flow between agents\n","# Native Parallel Agents\n\n> Orchestration through Claude Code's built-in Agent Tool\n\n## Overview\n\nThis skill enables coordinating multiple specialized agents through Claude Code's native agent system. Unlike external scripts, this approach keeps all orchestration within Claude's control.\n\n## When to Use Orchestration\n\n✅ **Good for:**\n- Complex tasks requiring multiple expertise domains\n- Code analysis from security, performance, and quality perspectives\n- Comprehensive reviews (architecture + security + testing)\n- Feature implementation needing backend + frontend + database work\n\n❌ **Not for:**\n- Simple, single-domain tasks\n- Quick fixes or small changes\n- Tasks where one agent suffices\n\n---\n\n## Native Agent Invocation\n\n### Single Agent\n```\nUse the security-auditor agent to review authentication\n```\n\n### Sequential Chain\n```\nFirst, use the explorer-agent to discover project structure.\nThen, use the backend-specialist to review API endpoints.\nFinally, use the test-engineer to identify test gaps.\n```\n\n### With Context Passing\n```\nUse the frontend-specialist to analyze React components.\nBased on those findings, have the test-engineer generate component tests.\n```\n\n### Resume Previous Work\n```\nResume agent [agentId] and continue with additional requirements.\n```\n\n---\n\n## Orchestration Patterns\n\n### Pattern 1: Comprehensive Analysis\n```\nAgents: explorer-agent → [domain-agents] → synthesis\n\n1. explorer-agent: Map codebase structure\n2. security-auditor: Security posture\n3. backend-specialist: API quality\n4. frontend-specialist: UI\u002FUX patterns\n5. test-engineer: Test coverage\n6. Synthesize all findings\n```\n\n### Pattern 2: Feature Review\n```\nAgents: affected-domain-agents → test-engineer\n\n1. Identify affected domains (backend? frontend? both?)\n2. Invoke relevant domain agents\n3. test-engineer verifies changes\n4. Synthesize recommendations\n```\n\n### Pattern 3: Security Audit\n```\nAgents: security-auditor → penetration-tester → synthesis\n\n1. security-auditor: Configuration and code review\n2. penetration-tester: Active vulnerability testing\n3. Synthesize with prioritized remediation\n```\n\n---\n\n## Available Agents\n\n| Agent | Expertise | Trigger Phrases |\n|-------|-----------|-----------------|\n| `orchestrator` | Coordination | \"comprehensive\", \"multi-perspective\" |\n| `security-auditor` | Security | \"security\", \"auth\", \"vulnerabilities\" |\n| `penetration-tester` | Security Testing | \"pentest\", \"red team\", \"exploit\" |\n| `backend-specialist` | Backend | \"API\", \"server\", \"Node.js\", \"Express\" |\n| `frontend-specialist` | Frontend | \"React\", \"UI\", \"components\", \"Next.js\" |\n| `test-engineer` | Testing | \"tests\", \"coverage\", \"TDD\" |\n| `devops-engineer` | DevOps | \"deploy\", \"CI\u002FCD\", \"infrastructure\" |\n| `database-architect` | Database | \"schema\", \"Prisma\", \"migrations\" |\n| `mobile-developer` | Mobile | \"React Native\", \"Flutter\", \"mobile\" |\n| `api-designer` | API Design | \"REST\", \"GraphQL\", \"OpenAPI\" |\n| `debugger` | Debugging | \"bug\", \"error\", \"not working\" |\n| `explorer-agent` | Discovery | \"explore\", \"map\", \"structure\" |\n| `documentation-writer` | Documentation | \"write docs\", \"create README\", \"generate API docs\" |\n| `performance-optimizer` | Performance | \"slow\", \"optimize\", \"profiling\" |\n| `project-planner` | Planning | \"plan\", \"roadmap\", \"milestones\" |\n| `seo-specialist` | SEO | \"SEO\", \"meta tags\", \"search ranking\" |\n| `game-developer` | Game Development | \"game\", \"Unity\", \"Godot\", \"Phaser\" |\n\n---\n\n## Claude Code Built-in Agents\n\nThese work alongside custom agents:\n\n| Agent | Model | Purpose |\n|-------|-------|---------|\n| **Explore** | Haiku | Fast read-only codebase search |\n| **Plan** | Sonnet | Research during plan mode |\n| **General-purpose** | Sonnet | Complex multi-step modifications |\n\nUse **Explore** for quick searches, **custom agents** for domain expertise.\n\n---\n\n## Synthesis Protocol\n\nAfter all agents complete, synthesize:\n\n```markdown\n## Orchestration Synthesis\n\n### Task Summary\n[What was accomplished]\n\n### Agent Contributions\n| Agent | Finding |\n|-------|---------|\n| security-auditor | Found X |\n| backend-specialist | Identified Y |\n\n### Consolidated Recommendations\n1. **Critical**: [Issue from Agent A]\n2. **Important**: [Issue from Agent B]\n3. **Nice-to-have**: [Enhancement from Agent C]\n\n### Action Items\n- [ ] Fix critical security issue\n- [ ] Refactor API endpoint\n- [ ] Add missing tests\n```\n\n---\n\n## Best Practices\n\n1. **Available agents** - 17 specialized agents can be orchestrated\n2. **Logical order** - Discovery → Analysis → Implementation → Testing\n3. **Share context** - Pass relevant findings to subsequent agents\n4. **Single synthesis** - One unified report, not separate outputs\n5. **Verify changes** - Always include test-engineer for code modifications\n\n---\n\n## Key Benefits\n\n- ✅ **Single session** - All agents share context\n- ✅ **AI-controlled** - Claude orchestrates autonomously\n- ✅ **Native integration** - Works with built-in Explore, Plan agents\n- ✅ **Resume support** - Can continue previous agent work\n- ✅ **Context passing** - Findings flow between agents\n",{"name":5,"description":7,"allowed-tools":49},"Read, Glob, Grep","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fparallel-agents",3911,"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-11 21:38:31",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill parallel-agents",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill parallel-agents",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill parallel-agents","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fparallel-agents\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"memory.md","REFERENCE","参考文档",11983,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fsetup-gbrain\u002Fmemory.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"SKILL.md.tmpl","OTHER","其他",45322,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fsetup-gbrain\u002FSKILL.md.tmpl",[87,112,139,172,207,231],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"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",[93],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,97,98,99,100,101,102,26,27,103,30,104,105,106,107,108,109,110,111],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"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",[118],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,125,126,127,128,129,130,27,131,132,133,134,135,136,137,138],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":154,"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",[145,148,149],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[155,156,157,158,159,160,161,100,162,163,164,165,166,167,168,26,169,170,27,171],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":183,"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",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,100,206],"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":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":218,"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",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,222,223,185,224,194,195,225,226,227,228,100,229,30,230],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":235,"sourceHtmlUrl":236,"categories":237,"keywords":245,"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",[238,241,242],{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,42,250,251,252,187,253,197,131,254,255,256,257,258,167,259,27,260,41,261,262,263,109,264],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]