[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF0PVNE44WPBRQ6QX2XWHS":3,"skill-same:01M6AF0PVNE44WPBRQ6QX2XWHS":88},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6AF0PVNE44WPBRQ6QX2XWHS","doordash-allergy-shield",null,"Persistent dietary safety layer for DoorDash CLI (dd-cli) ordering. Stores a personal\u002Fhousehold dietary profile (allergens with severity tiers, diets, dislikes) that every cart is vetted against before checkout, with a deterministic tripwire — the vetting step saves the full cart contents to a vetted-cart dump, and a PreToolUse hook re-greps that dump against the anaphylaxis-severity allergen list before any checkout URL is allowed. Use when the user mentions allergies or dietary restrictions, when ordering food for someone with restrictions, or on every dd-cli cart flow while this skill is installed. A tripwire, not medical-grade — the human checkout page is the final check.","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\u002Fdoordash\u002Fdoordash-allergy-shield\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,44,45,46],"doordash allergy shield","DoorDash","command","when","mkdir","re","URL","cart","checkout","medical","human","edit","write","read","personal","Bash","tripwire","Safety","severity","Guardrails","flow","dd","cli","2026-11-10 10:12:30",false,"---\nname: doordash-allergy-shield\ndescription: Persistent dietary safety layer for DoorDash CLI (dd-cli) ordering. Stores a personal\u002Fhousehold dietary profile (allergens with severity tiers, diets, dislikes) that every cart is vetted against before checkout, with a deterministic tripwire — the vetting step saves the full cart contents to a vetted-cart dump, and a PreToolUse hook re-greps that dump against the anaphylaxis-severity allergen list before any checkout URL is allowed. Use when the user mentions allergies or dietary restrictions, when ordering food for someone with restrictions, or on every dd-cli cart flow while this skill is installed. A tripwire, not medical-grade — the human checkout page is the final check.\nallowed-tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit\nmetadata:\n  tags: [DoorDash, Allergies, Dietary Restrictions, Safety, Guardrails, CLI]\n---\n\n# DoorDash Allergy Shield\n\nClaude has no cross-session memory: tell it \"I'm allergic to peanuts\" today\nand tomorrow it happily adds pad thai. This skill persists a dietary profile\nand makes cart vetting mandatory — with a deterministic hook double-checking\nthe highest-severity allergens before any checkout URL is emitted.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n\n## Honest limits (state these to the user on first use)\n\n- Matching is **heuristic**, against item names\u002Fdescriptions from\n  `cart show` output plus a synonyms table. It cannot see full ingredient\n  lists and knows nothing about cross-contamination in the kitchen.\n- It is a **tripwire against agent mistakes**, not a medical device. The\n  DoorDash payment page — where the human reviews the real order — is the\n  documented final check.\n- False positives are accepted by design: blocking a safe ponzu bowl is\n  cheap; the reverse is not. Hook matching is substring-based (short\n  allergen names like \"oat\" can match inside \"goat cheese\") — annoying,\n  never dangerous.\n- The `references\u002Fallergen-synonyms.md` table is intentionally broader than\n  the compact synonym subset hardcoded in the checkout-gate hooks; adding a\n  synonym to the reference doc alone does not change what the hooks enforce.\n\n## Components in this bundle\n\n| Piece | Role |\n|---|---|\n| this skill | vetting protocol + profile management |\n| `references\u002Fallergen-synonyms.md` | hidden-allergen lookup table |\n| hook `doordash\u002Fdoordash-allergy-checkout-gate` | deterministic re-check at checkout |\n| command `\u002Fdoordash-profile` | manage the dietary profile interactively |\n\n## State\n\n- `~\u002F.claude\u002Fdoordash-profile\u002Fdietary.json` — the profile. Structure:\n\n```json\n{\n  \"people\": {\n    \"me\": {\n      \"allergens\": [\n        { \"name\": \"peanut\", \"severity\": \"anaphylaxis\" },\n        { \"name\": \"shellfish\", \"severity\": \"avoid\" }\n      ],\n      \"diets\": [\"vegetarian\"],\n      \"dislikes\": [\"cilantro\"]\n    },\n    \"sam\": { \"allergens\": [{ \"name\": \"egg\", \"severity\": \"avoid\" }], \"diets\": [], \"dislikes\": [] }\n  }\n}\n```\n\nSeverity tiers: `anaphylaxis` (hook-enforced, never overridable in-session),\n`avoid` (requires explicit human acknowledgment to keep the item),\n`preference` (mention it, don't gate on it).\n\n- `~\u002F.claude\u002Fdoordash-profile\u002Fvetted\u002F\u003Ccart-uuid>.json` — one dump per vetted cart:\n  the **full raw `cart show` output** plus your verdict and a timestamp. The\n  checkout hook greps this artifact — it trusts the dump, not your claim.\n\n## Protocol\n\n### Session start\n\nRead `dietary.json`. Missing → offer to create it interactively (or via\n`\u002Fdoordash-profile`). If the user is ordering for others (\"lunch for me and Sam\"),\nmake sure each eater exists in the profile or ask for their restrictions.\n\n### After EVERY cart mutation (add-items \u002F remove-item \u002F reorder)\n\n1. Run `dd-cli cart show --cart-uuid \u003CX>` and capture the full output.\n2. Check every line against each relevant eater's profile — direct matches\n   AND hidden sources from `references\u002Fallergen-synonyms.md` (satay→peanut,\n   aioli→egg, ponzu→soy+fish, …).\n3. On a conflict:\n   - `anaphylaxis` → remove the item (`dd-cli cart remove-item`) and tell\n     the user why. Do not offer to keep it.\n   - `avoid` → present the conflict; keep only with explicit acknowledgment.\n   - `preference` → mention it in passing.\n4. Items whose name is too opaque to judge (\"Chef's Special #3\") → mark\n   **UNVERIFIED** and require the user's explicit sign-off for eaters with\n   `anaphylaxis` entries.\n5. Write the vetted dump: full `cart show` output + verdict + ISO timestamp\n   to `~\u002F.claude\u002Fdoordash-profile\u002Fvetted\u002F\u003Ccart-uuid>.json`. Without this file the\n   checkout hook blocks — vetting is not optional.\n\n### At checkout\n\nJust run `dd-cli order checkout-url --cart-uuid \u003CX>` (or the dd-guard\nwrapper when doordash-spend-guard is installed — the two gates compose). The hook\nindependently verifies: dump exists, is newer than the last cart mutation it\nsaw, and contains no anaphylaxis-tier keyword. If it blocks, do NOT try to\nwork around it — fix the cart, re-vet, and explain to the user what tripped.\n\n## Rules\n\n- Never edit `dietary.json` from the shell; profile changes go through\n  `\u002Fdoordash-profile` (interactive, confirmed).\n- Never write a vetted dump without actually running `cart show` fresh — the\n  dump IS the audit artifact.\n- When in doubt about an ingredient, doubt is a conflict.\n","# DoorDash Allergy Shield\n\nClaude has no cross-session memory: tell it \"I'm allergic to peanuts\" today\nand tomorrow it happily adds pad thai. This skill persists a dietary profile\nand makes cart vetting mandatory — with a deterministic hook double-checking\nthe highest-severity allergens before any checkout URL is emitted.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n\n## Honest limits (state these to the user on first use)\n\n- Matching is **heuristic**, against item names\u002Fdescriptions from\n  `cart show` output plus a synonyms table. It cannot see full ingredient\n  lists and knows nothing about cross-contamination in the kitchen.\n- It is a **tripwire against agent mistakes**, not a medical device. The\n  DoorDash payment page — where the human reviews the real order — is the\n  documented final check.\n- False positives are accepted by design: blocking a safe ponzu bowl is\n  cheap; the reverse is not. Hook matching is substring-based (short\n  allergen names like \"oat\" can match inside \"goat cheese\") — annoying,\n  never dangerous.\n- The `references\u002Fallergen-synonyms.md` table is intentionally broader than\n  the compact synonym subset hardcoded in the checkout-gate hooks; adding a\n  synonym to the reference doc alone does not change what the hooks enforce.\n\n## Components in this bundle\n\n| Piece | Role |\n|---|---|\n| this skill | vetting protocol + profile management |\n| `references\u002Fallergen-synonyms.md` | hidden-allergen lookup table |\n| hook `doordash\u002Fdoordash-allergy-checkout-gate` | deterministic re-check at checkout |\n| command `\u002Fdoordash-profile` | manage the dietary profile interactively |\n\n## State\n\n- `~\u002F.claude\u002Fdoordash-profile\u002Fdietary.json` — the profile. Structure:\n\n```json\n{\n  \"people\": {\n    \"me\": {\n      \"allergens\": [\n        { \"name\": \"peanut\", \"severity\": \"anaphylaxis\" },\n        { \"name\": \"shellfish\", \"severity\": \"avoid\" }\n      ],\n      \"diets\": [\"vegetarian\"],\n      \"dislikes\": [\"cilantro\"]\n    },\n    \"sam\": { \"allergens\": [{ \"name\": \"egg\", \"severity\": \"avoid\" }], \"diets\": [], \"dislikes\": [] }\n  }\n}\n```\n\nSeverity tiers: `anaphylaxis` (hook-enforced, never overridable in-session),\n`avoid` (requires explicit human acknowledgment to keep the item),\n`preference` (mention it, don't gate on it).\n\n- `~\u002F.claude\u002Fdoordash-profile\u002Fvetted\u002F\u003Ccart-uuid>.json` — one dump per vetted cart:\n  the **full raw `cart show` output** plus your verdict and a timestamp. The\n  checkout hook greps this artifact — it trusts the dump, not your claim.\n\n## Protocol\n\n### Session start\n\nRead `dietary.json`. Missing → offer to create it interactively (or via\n`\u002Fdoordash-profile`). If the user is ordering for others (\"lunch for me and Sam\"),\nmake sure each eater exists in the profile or ask for their restrictions.\n\n### After EVERY cart mutation (add-items \u002F remove-item \u002F reorder)\n\n1. Run `dd-cli cart show --cart-uuid \u003CX>` and capture the full output.\n2. Check every line against each relevant eater's profile — direct matches\n   AND hidden sources from `references\u002Fallergen-synonyms.md` (satay→peanut,\n   aioli→egg, ponzu→soy+fish, …).\n3. On a conflict:\n   - `anaphylaxis` → remove the item (`dd-cli cart remove-item`) and tell\n     the user why. Do not offer to keep it.\n   - `avoid` → present the conflict; keep only with explicit acknowledgment.\n   - `preference` → mention it in passing.\n4. Items whose name is too opaque to judge (\"Chef's Special #3\") → mark\n   **UNVERIFIED** and require the user's explicit sign-off for eaters with\n   `anaphylaxis` entries.\n5. Write the vetted dump: full `cart show` output + verdict + ISO timestamp\n   to `~\u002F.claude\u002Fdoordash-profile\u002Fvetted\u002F\u003Ccart-uuid>.json`. Without this file the\n   checkout hook blocks — vetting is not optional.\n\n### At checkout\n\nJust run `dd-cli order checkout-url --cart-uuid \u003CX>` (or the dd-guard\nwrapper when doordash-spend-guard is installed — the two gates compose). The hook\nindependently verifies: dump exists, is newer than the last cart mutation it\nsaw, and contains no anaphylaxis-tier keyword. If it blocks, do NOT try to\nwork around it — fix the cart, re-vet, and explain to the user what tripped.\n\n## Rules\n\n- Never edit `dietary.json` from the shell; profile changes go through\n  `\u002Fdoordash-profile` (interactive, confirmed).\n- Never write a vetted dump without actually running `cart show` fresh — the\n  dump IS the audit artifact.\n- When in doubt about an ingredient, doubt is a conflict.\n",{"name":5,"metadata":52,"description":7,"allowed-tools":57},{"tags":53},[25,54,55,41,43,56],"Allergies","Dietary Restrictions","CLI","Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add davila7\u002Fclaude-code-templates --skill doordash-allergy-shield",{"tool":74,"command":75},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill doordash-allergy-shield",{"tool":77,"command":78},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill doordash-allergy-shield","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fallergen-synonyms.md","REFERENCE","参考文档",2444,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield\u002Freferences\u002Fallergen-synonyms.md",[89,116,143,176,211,235],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":96,"publishedAt":47},"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",[95],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[97,98,99,100,101,102,103,104,105,27,106,107,108,109,110,111,112,113,114,115],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":47},"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",[122],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,125,126,127,128,129,130,131,132,133,134,27,135,136,137,138,139,140,141,142],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":158,"publishedAt":47},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[149,152,153],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[159,160,161,162,163,164,165,102,166,167,168,169,170,171,172,105,173,174,27,175],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":47},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,102,210],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":222,"publishedAt":47},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[218,221],{"categoryNo":219,"categoryName":220,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},[223,224,225,226,227,189,228,198,199,229,230,231,232,102,233,107,234],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":239,"sourceHtmlUrl":240,"categories":241,"keywords":249,"publishedAt":47},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[242,245,246],{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":247,"categoryName":248,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000036","内容创作者",[250,251,252,253,254,255,256,257,191,258,201,135,259,260,261,262,263,171,264,27,265,266,267,268,269,113,270],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]