[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79WVB0X62ZXMEFBC5NHN3H9":3,"skill-same:01M79WVB0X62ZXMEFBC5NHN3H9":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M79WVB0X62ZXMEFBC5NHN3H9","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.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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\ntags: [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,"tags":23,"description":7,"allowed-tools":30},[24,25,26,27,28,29],"DoorDash","Allergies","Dietary Restrictions","Safety","Guardrails","CLI","Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit","main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill doordash-allergy-shield",{"tool":43,"command":44},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill doordash-allergy-shield",{"tool":46,"command":47},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill doordash-allergy-shield","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fallergen-synonyms.md","REFERENCE","参考文档",2444,"https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-allergy-shield\u002Freferences\u002Fallergen-synonyms.md",[58,65,74,81,88,95],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]