[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF0S5Y38G6EKS13FAE495S":3,"skill-same:01M6AF0S5Y38G6EKS13FAE495S":80},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6AF0S5Y38G6EKS13FAE495S","doordash-group-orders",null,"Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request (\"lunch for the team\") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, \"collect orders from the thread\" — or for \u002Fwhose-turn payer rotation questions. Handles paste-a-thread intake: paste a Slack\u002Fchat thread and it builds the order ledger from it.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-group-orders\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"doordash group orders","DoorDash","orders","read","when","request","paste","mkdir","re","people","checkout","line","incident","conflicts","cli","command","coordination","Bash","team","incident-response","dd","collect","intake","slack","2026-11-10 10:12:30",false,"---\nname: doordash-group-orders\ndescription: \"Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request (\\\"lunch for the team\\\") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, \\\"collect orders from the thread\\\" — or for \u002Fwhose-turn payer rotation questions. Handles paste-a-thread intake: paste a Slack\u002Fchat thread and it builds the order ledger from it.\"\nallowed-tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit\nmetadata:\n  tags: [DoorDash, Team Lunch, Group Orders, Cost Split, CLI, Coordination]\n---\n\n# DoorDash Group Orders\n\nCoordinating N people's food is exactly the cross-session state Claude\ndrops: who's vegetarian, who hates cilantro, which cart line is Bob's, whose\nturn it is to pay. This skill keeps a roster, attributes every cart line to\nits eater, splits costs with fees prorated, and remembers payer history.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> Note: dd-cli orders under ONE account — the account owner pays DoorDash;\n> the split is for reimbursement (Venmo\u002Ftransfer), not split payment.\n\n## State\n\n- `team-food.json` (project dir or `~\u002F.claude\u002Fdd-cli\u002F` — committable if the\n  team shares a repo): the roster.\n\n```json\n{\n  \"members\": {\n    \"dani\":  { \"hard\": [\"vegetarian\"], \"allergens\": [{ \"name\": \"peanut\", \"severity\": \"anaphylaxis\" }], \"favorites\": [\"Veggie burrito bowl\"], \"dislikes\": [\"cilantro\"] },\n    \"bob\":   { \"hard\": [], \"allergens\": [], \"favorites\": [\"Spicy chicken sandwich\"], \"dislikes\": [] }\n  }\n}\n```\n\n- `.dd\u002Fround-\u003Cdate>.json` — the active round's ledger:\n\n```json\n{\n  \"date\": \"2026-07-19\",\n  \"cart_uuid\": \"...\",\n  \"restaurant\": \"...\",\n  \"orders\": {\n    \"dani\": [{ \"item\": \"Veggie bowl\", \"cart_item_id\": \"41\", \"price\": 12.5 }],\n    \"bob\":  [{ \"item\": \"Spicy chicken sandwich\", \"cart_item_id\": \"42\", \"price\": 11.0 }]\n  }\n}\n```\n\n- `.dd\u002Frounds.jsonl` — history, one line per completed round:\n  `{\"date\": \"...\", \"order_uuid\": \"...\", \"payer\": \"dani\", \"split\": {\"dani\": 14.1, \"bob\": 12.4}}`\n\n## Flow 1 — Build a round\n\n\"Order lunch for the team\":\n\n1. **Roster check**: load `team-food.json`; missing members → quick\n   interview (hard constraints, allergens + severity, a favorite, dislikes).\n2. **Restaurant**: intersect hard constraints (a vegetarian on the roster =\n   only places with real vegetarian options). `dd-cli search --query \"...\"`\n   → shortlist of 2-3 → let the human pick.\n3. **Per-member choice**: use their `favorites` when the restaurant matches;\n   otherwise ask ONE question per member (or take answers from a pasted\n   thread — Flow 2). Never guess for someone with allergens.\n4. **Build the cart**: `dd-cli cart add-items ...` per member's items (via\n   the dd-guard wrapper when doordash-spend-guard is installed). After each add,\n   run `dd-cli cart show --cart-uuid \u003CX>` and record which cart-item-id\n   belongs to whom in `.dd\u002Fround-\u003Cdate>.json`. This ledger is what makes\n   \"quita lo de Bob\" resolvable later.\n5. **Review**: show the cart grouped by person with per-person subtotals.\n6. **Checkout**: emit the checkout URL (through dd-guard if installed). The\n   group gate hook independently re-checks allergens (see below).\n7. **Close the round**: after the human confirms they ordered, pull the\n   order_uuid from `dd-cli order history`, compute the split, append to\n   `.dd\u002Frounds.jsonl`, and print a share-ready split table.\n\n## Flow 2 — Paste-a-thread intake\n\nThe user pastes a Slack\u002Fchat thread (\"who wants what\"). Parse it into the\nround file: person → requested items. Unknown people → ask if they should\njoin the roster. Ambiguous requests (\"something spicy\") → one clarifying\nquestion, or their favorite if the restaurant matches. Then continue Flow 1\nfrom step 4.\n\n## Flow 3 — Edits by person\n\n\"Bob canceló\" \u002F \"cambia lo de Sam\": look up the person's `cart_item_id`s in\nthe round ledger, `dd-cli cart remove-item --cart-uuid X --cart-item-id N`\nfor each, update the ledger, re-show the grouped cart.\n\n## Cost split\n\n- Item subtotals per person from the round ledger.\n- Fees\u002Ftip\u002Ftax are only final on the payment page: split the known subtotal\n  now, and offer the post-payment fallback — \"tell me the final total and\n  I'll prorate the difference by each person's share.\"\n- `split` = per-person items + prorated share of (final_total − subtotal)\n  when provided.\n\n## \u002Fwhose-turn\n\nRead `.dd\u002Frounds.jsonl`: sum what each member has paid vs. consumed across\nrounds; the next payer is the member with the largest (consumed − paid)\nbalance. Show the balances so the answer explains itself.\n\n## Rules\n\n- Anyone with an `anaphylaxis` allergen gets the same vetting the\n  doordash-allergy-shield skill applies — check their items against hidden-source\n  synonyms, and never guess their order.\n- cart-item-ids come only from real `cart show` output.\n- The round ledger is the source of truth for attribution — keep it updated\n  on every cart mutation, or person-level edits break.\n- Add `.dd\u002F` to `.gitignore` unless the team explicitly wants round history\n  committed (it reveals eating habits).\n","# DoorDash Group Orders\n\nCoordinating N people's food is exactly the cross-session state Claude\ndrops: who's vegetarian, who hates cilantro, which cart line is Bob's, whose\nturn it is to pay. This skill keeps a roster, attributes every cart line to\nits eater, splits costs with fees prorated, and remembers payer history.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> Note: dd-cli orders under ONE account — the account owner pays DoorDash;\n> the split is for reimbursement (Venmo\u002Ftransfer), not split payment.\n\n## State\n\n- `team-food.json` (project dir or `~\u002F.claude\u002Fdd-cli\u002F` — committable if the\n  team shares a repo): the roster.\n\n```json\n{\n  \"members\": {\n    \"dani\":  { \"hard\": [\"vegetarian\"], \"allergens\": [{ \"name\": \"peanut\", \"severity\": \"anaphylaxis\" }], \"favorites\": [\"Veggie burrito bowl\"], \"dislikes\": [\"cilantro\"] },\n    \"bob\":   { \"hard\": [], \"allergens\": [], \"favorites\": [\"Spicy chicken sandwich\"], \"dislikes\": [] }\n  }\n}\n```\n\n- `.dd\u002Fround-\u003Cdate>.json` — the active round's ledger:\n\n```json\n{\n  \"date\": \"2026-07-19\",\n  \"cart_uuid\": \"...\",\n  \"restaurant\": \"...\",\n  \"orders\": {\n    \"dani\": [{ \"item\": \"Veggie bowl\", \"cart_item_id\": \"41\", \"price\": 12.5 }],\n    \"bob\":  [{ \"item\": \"Spicy chicken sandwich\", \"cart_item_id\": \"42\", \"price\": 11.0 }]\n  }\n}\n```\n\n- `.dd\u002Frounds.jsonl` — history, one line per completed round:\n  `{\"date\": \"...\", \"order_uuid\": \"...\", \"payer\": \"dani\", \"split\": {\"dani\": 14.1, \"bob\": 12.4}}`\n\n## Flow 1 — Build a round\n\n\"Order lunch for the team\":\n\n1. **Roster check**: load `team-food.json`; missing members → quick\n   interview (hard constraints, allergens + severity, a favorite, dislikes).\n2. **Restaurant**: intersect hard constraints (a vegetarian on the roster =\n   only places with real vegetarian options). `dd-cli search --query \"...\"`\n   → shortlist of 2-3 → let the human pick.\n3. **Per-member choice**: use their `favorites` when the restaurant matches;\n   otherwise ask ONE question per member (or take answers from a pasted\n   thread — Flow 2). Never guess for someone with allergens.\n4. **Build the cart**: `dd-cli cart add-items ...` per member's items (via\n   the dd-guard wrapper when doordash-spend-guard is installed). After each add,\n   run `dd-cli cart show --cart-uuid \u003CX>` and record which cart-item-id\n   belongs to whom in `.dd\u002Fround-\u003Cdate>.json`. This ledger is what makes\n   \"quita lo de Bob\" resolvable later.\n5. **Review**: show the cart grouped by person with per-person subtotals.\n6. **Checkout**: emit the checkout URL (through dd-guard if installed). The\n   group gate hook independently re-checks allergens (see below).\n7. **Close the round**: after the human confirms they ordered, pull the\n   order_uuid from `dd-cli order history`, compute the split, append to\n   `.dd\u002Frounds.jsonl`, and print a share-ready split table.\n\n## Flow 2 — Paste-a-thread intake\n\nThe user pastes a Slack\u002Fchat thread (\"who wants what\"). Parse it into the\nround file: person → requested items. Unknown people → ask if they should\njoin the roster. Ambiguous requests (\"something spicy\") → one clarifying\nquestion, or their favorite if the restaurant matches. Then continue Flow 1\nfrom step 4.\n\n## Flow 3 — Edits by person\n\n\"Bob canceló\" \u002F \"cambia lo de Sam\": look up the person's `cart_item_id`s in\nthe round ledger, `dd-cli cart remove-item --cart-uuid X --cart-item-id N`\nfor each, update the ledger, re-show the grouped cart.\n\n## Cost split\n\n- Item subtotals per person from the round ledger.\n- Fees\u002Ftip\u002Ftax are only final on the payment page: split the known subtotal\n  now, and offer the post-payment fallback — \"tell me the final total and\n  I'll prorate the difference by each person's share.\"\n- `split` = per-person items + prorated share of (final_total − subtotal)\n  when provided.\n\n## \u002Fwhose-turn\n\nRead `.dd\u002Frounds.jsonl`: sum what each member has paid vs. consumed across\nrounds; the next payer is the member with the largest (consumed − paid)\nbalance. Show the balances so the answer explains itself.\n\n## Rules\n\n- Anyone with an `anaphylaxis` allergen gets the same vetting the\n  doordash-allergy-shield skill applies — check their items against hidden-source\n  synonyms, and never guess their order.\n- cart-item-ids come only from real `cart show` output.\n- The round ledger is the source of truth for attribution — keep it updated\n  on every cart mutation, or person-level edits break.\n- Add `.dd\u002F` to `.gitignore` unless the team explicitly wants round history\n  committed (it reveals eating habits).\n",{"name":5,"metadata":48,"description":7,"allowed-tools":55},{"tags":49},[20,50,51,52,53,54],"Team Lunch","Group Orders","Cost Split","CLI","Coordination","Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-group-orders",3963,"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-15 01:32:48",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add davila7\u002Fclaude-code-templates --skill doordash-group-orders",{"tool":72,"command":73},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill doordash-group-orders",{"tool":75,"command":76},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill doordash-group-orders","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-group-orders\u002FSKILL.md",true,[],[81,112,139,172,207,231],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":43},"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",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,101,23,102,103,104,105,106,107,108,109,110,111],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","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":43},"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":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[120,121,122,123,124,125,126,127,128,129,130,23,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":43},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[155,156,157,158,159,160,161,98,162,163,164,165,166,167,168,101,169,170,23,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":43},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发",[184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,98,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":43},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":181,"categoryName":182,"taxonomyType":90,"taxonomyTypeDesc":91},[219,220,221,222,223,185,224,194,195,225,226,227,228,98,229,103,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":43},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":243,"categoryName":244,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,250,251,252,253,187,254,197,131,255,256,257,258,259,167,260,23,261,262,263,264,265,109,266],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]