[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AN094EV43B7115G5XFSKJ3":3,"skill-same:01M7AN094EV43B7115G5XFSKJ3":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AN094EV43B7115G5XFSKJ3","create-plan",null,"Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fcreate-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-plan\ndescription: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.\nmetadata:\n  short-description: Create a plan\n---\n\n# Create Plan\n\n## Goal\n\nTurn a user prompt into a **single, actionable plan** delivered in the final assistant message.\n\n## Minimal workflow\n\nThroughout the entire workflow, operate in read-only mode. Do not write or update files.\n\n1. **Scan context quickly**\n   - Read `README.md` and any obvious docs (`docs\u002F`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).\n   - Skim relevant files (the ones most likely touched).\n   - Identify constraints (language, frameworks, CI\u002Ftest commands, deployment shape).\n\n2. **Ask follow-ups only if blocking**\n   - Ask **at most 1–2 questions**.\n   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.\n   - If unsure but not blocked, make a reasonable assumption and proceed.\n\n3. **Create a plan using the template below**\n   - Start with **1 short paragraph** describing the intent and approach.\n   - Clearly call out what is **in scope** and what is **not in scope** in short.\n   - Then provide a **small checklist** of action items (default 6–10 items).\n      - Each checklist item should be a concrete action and, when helpful, mention files\u002Fcommands.\n      - **Make items atomic and ordered**: discovery → changes → tests → rollout.\n      - **Verb-first**: \"Add…\", \"Refactor…\", \"Verify…\", \"Ship…\".\n   - Include at least one item for **tests\u002Fvalidation** and one for **edge cases\u002Frisk** when applicable.\n   - If there are unknowns, include a tiny **Open questions** section (max 3).\n\n4. **Do not preface the plan with meta explanations; output only the plan as per template**\n\n## Plan template (follow exactly)\n\n```markdown\n# Plan\n\n\u003C1–3 sentences: what we're doing, why, and the high-level approach.>\n\n## Scope\n- In:\n- Out:\n\n## Action items\n[ ] \u003CStep 1>\n[ ] \u003CStep 2>\n[ ] \u003CStep 3>\n[ ] \u003CStep 4>\n[ ] \u003CStep 5>\n[ ] \u003CStep 6>\n\n## Open questions\n- \u003CQuestion 1>\n- \u003CQuestion 2>\n- \u003CQuestion 3>\n```\n\n## Checklist item guidance\nGood checklist items:\n- Point to likely files\u002Fmodules: src\u002F..., app\u002F..., services\u002F...\n- Name concrete validation: \"Run npm test\", \"Add unit tests for X\"\n- Include safe rollout when relevant: feature flag, migration plan, rollback note\n\nAvoid:\n- Vague steps (\"handle backend\", \"do auth\")\n- Too many micro-steps\n- Writing code snippets (keep the plan implementation-agnostic)\n","# Create Plan\n\n## Goal\n\nTurn a user prompt into a **single, actionable plan** delivered in the final assistant message.\n\n## Minimal workflow\n\nThroughout the entire workflow, operate in read-only mode. Do not write or update files.\n\n1. **Scan context quickly**\n   - Read `README.md` and any obvious docs (`docs\u002F`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).\n   - Skim relevant files (the ones most likely touched).\n   - Identify constraints (language, frameworks, CI\u002Ftest commands, deployment shape).\n\n2. **Ask follow-ups only if blocking**\n   - Ask **at most 1–2 questions**.\n   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.\n   - If unsure but not blocked, make a reasonable assumption and proceed.\n\n3. **Create a plan using the template below**\n   - Start with **1 short paragraph** describing the intent and approach.\n   - Clearly call out what is **in scope** and what is **not in scope** in short.\n   - Then provide a **small checklist** of action items (default 6–10 items).\n      - Each checklist item should be a concrete action and, when helpful, mention files\u002Fcommands.\n      - **Make items atomic and ordered**: discovery → changes → tests → rollout.\n      - **Verb-first**: \"Add…\", \"Refactor…\", \"Verify…\", \"Ship…\".\n   - Include at least one item for **tests\u002Fvalidation** and one for **edge cases\u002Frisk** when applicable.\n   - If there are unknowns, include a tiny **Open questions** section (max 3).\n\n4. **Do not preface the plan with meta explanations; output only the plan as per template**\n\n## Plan template (follow exactly)\n\n```markdown\n# Plan\n\n\u003C1–3 sentences: what we're doing, why, and the high-level approach.>\n\n## Scope\n- In:\n- Out:\n\n## Action items\n[ ] \u003CStep 1>\n[ ] \u003CStep 2>\n[ ] \u003CStep 3>\n[ ] \u003CStep 4>\n[ ] \u003CStep 5>\n[ ] \u003CStep 6>\n\n## Open questions\n- \u003CQuestion 1>\n- \u003CQuestion 2>\n- \u003CQuestion 3>\n```\n\n## Checklist item guidance\nGood checklist items:\n- Point to likely files\u002Fmodules: src\u002F..., app\u002F..., services\u002F...\n- Name concrete validation: \"Run npm test\", \"Add unit tests for X\"\n- Include safe rollout when relevant: feature flag, migration plan, rollback note\n\nAvoid:\n- Vague steps (\"handle backend\", \"do auth\")\n- Too many micro-steps\n- Writing code snippets (keep the plan implementation-agnostic)\n",{"name":5,"metadata":24,"description":7},{"short-description":25},"Create a plan","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fdevelopment\u002Fcreate-plan","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill create-plan",{"tool":39,"command":40},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill create-plan",{"tool":42,"command":43},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill create-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fcreate-plan\u002FSKILL.md",true,[],[48,55,64,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]