[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF0ZJ34Z6BBT0XA33P0D07":3,"skill-same:01M6AF0ZJ34Z6BBT0XA33P0D07":123},{"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":28,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6AF0ZJ34Z6BBT0XA33P0D07","doordash-spend-guard",null,"Hard spending policy for agent-driven DoorDash ordering through the DoorDash CLI (dd-cli). Per-order ceiling, daily\u002Fweekly\u002Fmonthly caps, cooldown between orders, and blocked hours — enforced deterministically by routing every cart-mutation and checkout through the dd-guard wrapper script, which prices the cart, checks the policy against a persistent spend ledger, and refuses out-of-policy checkouts with exit code 2. Use when the user wants budget limits on agent food ordering, asks \"how much have I spent on DoorDash\", wants to set spending caps, or whenever building carts \u002F checking out with dd-cli while this skill is installed. Pairs with a PreToolUse hook that denies raw dd-cli checkout calls that bypass the wrapper.","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-spend-guard\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"doordash spend guard","guard","how","when","limits","weekly","prices","which","mkdir","checkout","scripts","mutation","read","command","Bash","cli","Safety","Spending Limits","Budget","DoorDash","SET","Guardrails","dd","code","routing","policy","2026-11-10 10:12:30",false,"---\nname: doordash-spend-guard\ndescription: Hard spending policy for agent-driven DoorDash ordering through the DoorDash CLI (dd-cli). Per-order ceiling, daily\u002Fweekly\u002Fmonthly caps, cooldown between orders, and blocked hours — enforced deterministically by routing every cart-mutation and checkout through the dd-guard wrapper script, which prices the cart, checks the policy against a persistent spend ledger, and refuses out-of-policy checkouts with exit code 2. Use when the user wants budget limits on agent food ordering, asks \"how much have I spent on DoorDash\", wants to set spending caps, or whenever building carts \u002F checking out with dd-cli while this skill is installed. Pairs with a PreToolUse hook that denies raw dd-cli checkout calls that bypass the wrapper.\nallowed-tools: Bash(dd-cli:*), Bash(bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read\ntags: [DoorDash, Budget, Spending Limits, Guardrails, CLI, Safety]\n---\n\n# DoorDash Spend Guard\n\nA budget stated in a prompt is advisory — the model can forget it mid-session\nand prompt injection can override it. This skill makes the budget\n**deterministic**: every checkout and cart mutation goes through one audited\nwrapper (`dd-guard.sh`) that prices the cart, checks the policy, and refuses\nout-of-policy actions with a machine exit code. The companion PreToolUse hook\n(`doordash-spend-guard` hook component) denies raw `dd-cli order checkout-url` \u002F\n`dd-cli cart add-items` calls that try to bypass the wrapper.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> Requires `dd-cli` installed and logged in. Wrapper needs `python3`.\n\n## Honest scope\n\n- Caps apply to the **pre-fee subtotal** that `cart show` exposes; fees, tip\n  and tax land on the DoorDash payment page. Documented headroom, not\n  loopholes.\n- The ledger records **intent** when a checkout URL is issued; the human may\n  abandon the page. `\u002Fdoordash-budget` reconciles intents against\n  `dd-cli order history`, marking entries `paid` or `abandoned`.\n- Enforcement teeth come from the hook + wrapper combo. Install both; the\n  skill alone is guidance.\n\n## Components in this bundle\n\n| Piece | Role |\n|---|---|\n| this skill | protocol: always route through dd-guard, report headroom |\n| `scripts\u002Fdd-guard.sh` → installs to `.claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh` | the deterministic gate |\n| hook `doordash\u002Fdoordash-spend-guard` | denies bypasses of the wrapper |\n| command `\u002Fdoordash-budget` | view\u002Fedit policy, reconcile ledger |\n\n## State (created on first run)\n\n- `~\u002F.claude\u002Fdd-guard\u002Flimits.json` — policy. **Human-edited only.** Never\n  edit this file yourself; when the user asks for a change, direct them to\n  `\u002Fdoordash-budget` which confirms interactively.\n\n```json\n{\n  \"per_order_max\": 40,\n  \"daily_max\": 60,\n  \"weekly_max\": 150,\n  \"monthly_max\": 400,\n  \"cooldown_minutes\": 45,\n  \"allowed_hours\": { \"start\": 7, \"end\": 23 }\n}\n```\n\n- `~\u002F.claude\u002Fdd-guard\u002Fledger.jsonl` — one line per priced action:\n  `{\"ts\": \"...\", \"cart_uuid\": \"...\", \"subtotal\": 24.5, \"status\": \"intent\"}`\n  (`status` becomes `paid` \u002F `abandoned` after reconciliation).\n\n## Protocol (follow ALWAYS while this skill is installed)\n\n1. **Session start \u002F before building a cart**: report headroom —\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh status` prints spend-to-date vs each\n   cap. Tell the user their remaining budget before adding items.\n2. **Adding items**: route through the wrapper —\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh add-items \u003Cthe exact dd-cli cart add-items args>`\n   The wrapper execs the real `dd-cli cart add-items ...` and re-prices the\n   cart afterwards.\n3. **Checkout**: NEVER call `dd-cli order checkout-url` directly. Use\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh checkout \u003Ccart-uuid>`\n   - exit 0 → it printed the checkout URL and appended a ledger intent line.\n   - exit 2 → blocked; it printed a human-readable reason (which cap, by how\n     much). Relay the reason verbatim, then help within policy — e.g. suggest\n     a cheaper reorder from `dd-cli order history` or trimming the cart with\n     `dd-cli cart remove-item`.\n4. **When blocked, do not negotiate with the wrapper.** No editing\n   limits.json, no retrying with a fresh cart to reset the cooldown, no\n   splitting one order into several to duck the per-order cap. If the user\n   wants a different policy, point them to `\u002Fdoordash-budget`.\n5. If the wrapper reports the cart subtotal as unparseable, it blocks by\n   design (conservative default). Show the user the raw `cart show` output\n   and ask them to confirm the total explicitly before any manual override.\n\n## Reading the ledger\n\nAnswer \"how much have I spent this week?\" from the ledger, not memory:\n\n```bash\nbash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh status\n# or raw:\ncat ~\u002F.claude\u002Fdd-guard\u002Fledger.jsonl | jq -s '[.[] | select(.status != \"abandoned\")] | map(.subtotal) | add'\n```\n\nRemind the user that subtotals exclude fees\u002Ftips and intents may not have\nbeen paid — `\u002Fdoordash-budget` reconciles.\n","# DoorDash Spend Guard\n\nA budget stated in a prompt is advisory — the model can forget it mid-session\nand prompt injection can override it. This skill makes the budget\n**deterministic**: every checkout and cart mutation goes through one audited\nwrapper (`dd-guard.sh`) that prices the cart, checks the policy, and refuses\nout-of-policy actions with a machine exit code. The companion PreToolUse hook\n(`doordash-spend-guard` hook component) denies raw `dd-cli order checkout-url` \u002F\n`dd-cli cart add-items` calls that try to bypass the wrapper.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> Requires `dd-cli` installed and logged in. Wrapper needs `python3`.\n\n## Honest scope\n\n- Caps apply to the **pre-fee subtotal** that `cart show` exposes; fees, tip\n  and tax land on the DoorDash payment page. Documented headroom, not\n  loopholes.\n- The ledger records **intent** when a checkout URL is issued; the human may\n  abandon the page. `\u002Fdoordash-budget` reconciles intents against\n  `dd-cli order history`, marking entries `paid` or `abandoned`.\n- Enforcement teeth come from the hook + wrapper combo. Install both; the\n  skill alone is guidance.\n\n## Components in this bundle\n\n| Piece | Role |\n|---|---|\n| this skill | protocol: always route through dd-guard, report headroom |\n| `scripts\u002Fdd-guard.sh` → installs to `.claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh` | the deterministic gate |\n| hook `doordash\u002Fdoordash-spend-guard` | denies bypasses of the wrapper |\n| command `\u002Fdoordash-budget` | view\u002Fedit policy, reconcile ledger |\n\n## State (created on first run)\n\n- `~\u002F.claude\u002Fdd-guard\u002Flimits.json` — policy. **Human-edited only.** Never\n  edit this file yourself; when the user asks for a change, direct them to\n  `\u002Fdoordash-budget` which confirms interactively.\n\n```json\n{\n  \"per_order_max\": 40,\n  \"daily_max\": 60,\n  \"weekly_max\": 150,\n  \"monthly_max\": 400,\n  \"cooldown_minutes\": 45,\n  \"allowed_hours\": { \"start\": 7, \"end\": 23 }\n}\n```\n\n- `~\u002F.claude\u002Fdd-guard\u002Fledger.jsonl` — one line per priced action:\n  `{\"ts\": \"...\", \"cart_uuid\": \"...\", \"subtotal\": 24.5, \"status\": \"intent\"}`\n  (`status` becomes `paid` \u002F `abandoned` after reconciliation).\n\n## Protocol (follow ALWAYS while this skill is installed)\n\n1. **Session start \u002F before building a cart**: report headroom —\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh status` prints spend-to-date vs each\n   cap. Tell the user their remaining budget before adding items.\n2. **Adding items**: route through the wrapper —\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh add-items \u003Cthe exact dd-cli cart add-items args>`\n   The wrapper execs the real `dd-cli cart add-items ...` and re-prices the\n   cart afterwards.\n3. **Checkout**: NEVER call `dd-cli order checkout-url` directly. Use\n   `bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh checkout \u003Ccart-uuid>`\n   - exit 0 → it printed the checkout URL and appended a ledger intent line.\n   - exit 2 → blocked; it printed a human-readable reason (which cap, by how\n     much). Relay the reason verbatim, then help within policy — e.g. suggest\n     a cheaper reorder from `dd-cli order history` or trimming the cart with\n     `dd-cli cart remove-item`.\n4. **When blocked, do not negotiate with the wrapper.** No editing\n   limits.json, no retrying with a fresh cart to reset the cooldown, no\n   splitting one order into several to duck the per-order cap. If the user\n   wants a different policy, point them to `\u002Fdoordash-budget`.\n5. If the wrapper reports the cart subtotal as unparseable, it blocks by\n   design (conservative default). Show the user the raw `cart show` output\n   and ask them to confirm the total explicitly before any manual override.\n\n## Reading the ledger\n\nAnswer \"how much have I spent this week?\" from the ledger, not memory:\n\n```bash\nbash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh status\n# or raw:\ncat ~\u002F.claude\u002Fdd-guard\u002Fledger.jsonl | jq -s '[.[] | select(.status != \"abandoned\")] | map(.subtotal) | add'\n```\n\nRemind the user that subtotals exclude fees\u002Ftips and intents may not have\nbeen paid — `\u002Fdoordash-budget` reconciles.\n",{"name":5,"tags":60,"description":7,"allowed-tools":62},[48,47,46,50,61,45],"CLI","Bash(dd-cli:*), Bash(bash .claude\u002Fskills\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-spend-guard",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":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add davila7\u002Fclaude-code-templates --skill doordash-spend-guard",{"tool":79,"command":80},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill doordash-spend-guard",{"tool":82,"command":83},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill doordash-spend-guard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-spend-guard\u002FSKILL.md",true,[87,93,97,101,105,111,115,119],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Falgorithms.md","REFERENCE","参考文档",10038,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Falgorithms.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fcallbacks.md",15631,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fcallbacks.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fcustom_environments.md",13729,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fcustom_environments.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fvectorized_envs.md",14789,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fvectorized_envs.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fcustom_env_template.py","SCRIPT","脚本",9350,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Fcustom_env_template.py",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fdd-guard.sh",8267,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-spend-guard\u002Fscripts\u002Fdd-guard.sh",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fevaluate_agent.py",7335,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Fevaluate_agent.py",{"path":120,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Ftrain_rl_agent.py",5123,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Ftrain_rl_agent.py",[124,149,175,205,239,263],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":55},"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",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134,135,36,136,137,138,139,32,140,141,142,143,144,145,146,31,147,148],"scoring","pool","wealthville pool scoring","liquidity","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","public","look",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":55},"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",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,161,162,163,164,165,166,167,32,52,168,169,170,171,172,173,174],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":188,"publishedAt":55},"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",[181,184,185],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":186,"categoryName":187,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[189,30,190,191,192,193,194,136,195,196,197,198,199,200,201,139,202,203,32,204],"readonly","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":216,"publishedAt":55},"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",[213],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[217,218,219,220,221,222,53,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,136,238],"artifacts builder","web","web artifacts builder","artifacts","builder","state","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":243,"sourceHtmlUrl":244,"categories":245,"keywords":250,"publishedAt":55},"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",[246,249],{"categoryNo":247,"categoryName":248,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},[251,252,253,254,255,218,256,226,227,257,258,259,260,136,261,141,262],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":267,"sourceHtmlUrl":268,"categories":269,"keywords":277,"publishedAt":55},"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",[270,273,274],{"categoryNo":271,"categoryName":272,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":275,"categoryName":276,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[278,279,280,281,282,283,284,285,220,286,229,52,287,288,289,290,291,200,292,32,293,294,295,296,297,31,298],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]