[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEXW9BDPGWJWJ7KG8C805C":3,"skill-same:01M6AEXW9BDPGWJWJ7KG8C805C":97},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6AEXW9BDPGWJWJ7KG8C805C","workspace-orchestration",null,"Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots\u002F require an active claim.","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\u002Fworkspace-orchestration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fworkspace-orchestration\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31],"orchestration","workspace orchestration","workspace","code","use","claim","active","inheritance","rule","claims","slots","when","2026-11-10 10:12:30",false,"---\nname: workspace-orchestration\ndescription: Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots\u002F require an active claim.\n---\n\n# docko Workspace Orchestration\n\nUse this skill whenever work touches files in `slots\u002F` or when the user asks about workspace coordination.\n\n## Quick Path\n\n1. Run `\u002Fdock-status` or `docko status --brief`. docko walks up to the workspace root on its own, so this works from inside a slot; pass `--root \u003Cworkspace>` only from outside the workspace.\n2. Pass `--session \"$DOCKO_SESSION_ID\"` on every claim, heartbeat, and release. The SessionStart hook exports it for this session.\n3. Prefer `docko slot acquire --session \"$DOCKO_SESSION_ID\" --branch \u003Cbranch> --task \"\u003Ctask>\" --brief` when you want docko to pick a slot. Selection is round-robin, starting after the last slot claimed for that application.\n4. In a workspace with several applications, pass `--application \u003Cid>` so the pick stays inside the right pool.\n5. Add `--prefer \u003Cslot-id>` when a specific slot is the right one (it already has the branch, say). docko takes it when free and rotates normally when it is not.\n6. If every slot is busy and docko asks whether it should create a fresh managed clone, answer explicitly.\n7. Use `docko claim --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot> --branch \u003Cbranch> --task \"\u003Ctask>\"` only when you already know the exact slot.\n8. Do the work inside that slot. On long-running work, keep the claim fresh:\n   `docko heartbeat --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot>`\n9. Release the slot when done:\n   `docko release --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot>`\n\nPrefer slash commands when installed:\n\n- `\u002Fdock-status`\n- `\u002Fdock-claim \u003Cslot> \u003Cbranch> \u003Ctask>`\n- `\u002Fdock-heartbeat \u003Cslot>`\n- `\u002Fdock-release \u003Cslot>`\n- `\u002Fdock-doctor`\n\n## Rules\n\n- Work from the root. Edit code in `slots\u002F*`.\n- If `$DOCKO_SESSION_ID` is empty (plugin hooks not installed, or a different runtime), stop before the first claim and resolve a real session id — never run claim or heartbeat with an empty `--session`. Use `docko session list --brief` or `docko session current` to pick one.\n- Never invent a session id. The PreToolUse hook checks the runtime's own session, so a made-up id claims a slot that then blocks your own writes. Use `$DOCKO_SESSION_ID`, or an id from `docko session list --brief`.\n- `branch` is claim metadata. docko records it and never runs `git checkout`.\n- Claims are slot-scoped. Two sessions cannot share a slot, and one claim does not reserve a branch, a PR, or a file.\n- If a parent session already owns the slot, reuse that authority instead of creating a second claim.\n- Subagents started with the Agent tool share the parent's session id, so they inherit the parent's claim and need no docko call. A separately launched `claude` process gets its own session id and must be delegated: `docko delegate --session \u003Cowner> --child-session \u003Cchild> --resource slot --id \u003Cslot>`.\n- If docko reports `AMBIGUOUS_SESSION`, run the `suggested_command` from the error payload, or retry with an explicit `--session \u003Cid>` from `docko session list --brief`; do not end existing sessions unless the user asked for cleanup.\n- If a write is blocked, read the deny message: it names the slot, the reason (`slot-not-claimed`, `claim-expired`, `unrelated-session`) and the exact command that fixes it.\n- If every slot is busy and the user already approved the fallback, add `--clone-when-busy` to `docko slot acquire`.\n- If `docko` is not runnable, check `DOCKO_BIN`. If it still fails, stop and tell the user.\n- Do not inspect slots one by one or replace the CLI with `docko\u002Fregistry.json` during normal work. Use `docko status --brief --claimed` instead.\n","# docko Workspace Orchestration\n\nUse this skill whenever work touches files in `slots\u002F` or when the user asks about workspace coordination.\n\n## Quick Path\n\n1. Run `\u002Fdock-status` or `docko status --brief`. docko walks up to the workspace root on its own, so this works from inside a slot; pass `--root \u003Cworkspace>` only from outside the workspace.\n2. Pass `--session \"$DOCKO_SESSION_ID\"` on every claim, heartbeat, and release. The SessionStart hook exports it for this session.\n3. Prefer `docko slot acquire --session \"$DOCKO_SESSION_ID\" --branch \u003Cbranch> --task \"\u003Ctask>\" --brief` when you want docko to pick a slot. Selection is round-robin, starting after the last slot claimed for that application.\n4. In a workspace with several applications, pass `--application \u003Cid>` so the pick stays inside the right pool.\n5. Add `--prefer \u003Cslot-id>` when a specific slot is the right one (it already has the branch, say). docko takes it when free and rotates normally when it is not.\n6. If every slot is busy and docko asks whether it should create a fresh managed clone, answer explicitly.\n7. Use `docko claim --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot> --branch \u003Cbranch> --task \"\u003Ctask>\"` only when you already know the exact slot.\n8. Do the work inside that slot. On long-running work, keep the claim fresh:\n   `docko heartbeat --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot>`\n9. Release the slot when done:\n   `docko release --session \"$DOCKO_SESSION_ID\" --resource slot --id \u003Cslot>`\n\nPrefer slash commands when installed:\n\n- `\u002Fdock-status`\n- `\u002Fdock-claim \u003Cslot> \u003Cbranch> \u003Ctask>`\n- `\u002Fdock-heartbeat \u003Cslot>`\n- `\u002Fdock-release \u003Cslot>`\n- `\u002Fdock-doctor`\n\n## Rules\n\n- Work from the root. Edit code in `slots\u002F*`.\n- If `$DOCKO_SESSION_ID` is empty (plugin hooks not installed, or a different runtime), stop before the first claim and resolve a real session id — never run claim or heartbeat with an empty `--session`. Use `docko session list --brief` or `docko session current` to pick one.\n- Never invent a session id. The PreToolUse hook checks the runtime's own session, so a made-up id claims a slot that then blocks your own writes. Use `$DOCKO_SESSION_ID`, or an id from `docko session list --brief`.\n- `branch` is claim metadata. docko records it and never runs `git checkout`.\n- Claims are slot-scoped. Two sessions cannot share a slot, and one claim does not reserve a branch, a PR, or a file.\n- If a parent session already owns the slot, reuse that authority instead of creating a second claim.\n- Subagents started with the Agent tool share the parent's session id, so they inherit the parent's claim and need no docko call. A separately launched `claude` process gets its own session id and must be delegated: `docko delegate --session \u003Cowner> --child-session \u003Cchild> --resource slot --id \u003Cslot>`.\n- If docko reports `AMBIGUOUS_SESSION`, run the `suggested_command` from the error payload, or retry with an explicit `--session \u003Cid>` from `docko session list --brief`; do not end existing sessions unless the user asked for cleanup.\n- If a write is blocked, read the deny message: it names the slot, the reason (`slot-not-claimed`, `claim-expired`, `unrelated-session`) and the exact command that fixes it.\n- If every slot is busy and the user already approved the fallback, add `--clone-when-busy` to `docko slot acquire`.\n- If `docko` is not runnable, check `DOCKO_BIN`. If it still fails, stop and tell the user.\n- Do not inspect slots one by one or replace the CLI with `docko\u002Fregistry.json` during normal work. Use `docko status --brief --claimed` instead.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fworkspace-orchestration",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add davila7\u002Fclaude-code-templates --skill workspace-orchestration",{"tool":53,"command":54},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill workspace-orchestration",{"tool":56,"command":57},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill workspace-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fworkspace-orchestration\u002FSKILL.md",true,[61,67,71,77,81,85,89,93],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"example_usage.sh","SCRIPT","脚本",3052,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002Fexample_usage.sh",{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":16},"LICENSE","许可证",1062,{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"QUICK_REFERENCE.md","REFERENCE","参考文档",4790,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002FQUICK_REFERENCE.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"README.md",8686,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002FREADME.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fbest_practices.md",15910,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002Freferences\u002Fbest_practices.md",{"path":86,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fgenerate_schematic_ai.py",33173,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002Fscripts\u002Fgenerate_schematic_ai.py",{"path":90,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fgenerate_schematic.py",5016,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002Fscripts\u002Fgenerate_schematic.py",{"path":94,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":95,"sourceHtmlUrl":96},"test_ai_generation.py",7653,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-schematics\u002Ftest_ai_generation.py",[98,128,154,187,222,246],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":32},"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",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[110,111,112,113,114,115,116,117,24,31,118,119,120,121,122,123,124,125,126,127],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":32},"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",[134],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[136,137,138,139,140,141,142,143,144,145,146,31,23,147,148,149,150,151,152,153],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":169,"publishedAt":32},"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",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[170,171,172,173,174,175,176,115,177,178,179,180,181,182,183,24,184,185,31,186],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":32},"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",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000009","前端开发",[199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,115,221],"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":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":233,"publishedAt":32},"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",[229,232],{"categoryNo":230,"categoryName":231,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":196,"categoryName":197,"taxonomyType":107,"taxonomyTypeDesc":108},[234,235,236,237,238,200,239,209,210,240,241,242,243,115,244,119,245],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":250,"sourceHtmlUrl":251,"categories":252,"keywords":260,"publishedAt":32},"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",[253,256,257],{"categoryNo":254,"categoryName":255,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":258,"categoryName":259,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000036","内容创作者",[261,262,263,264,265,266,267,268,202,269,212,23,270,271,272,273,274,182,275,31,276,277,29,278,279,125,280],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","argument","assemble","recommendations"]