[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72B7J4GAZRGTCNCRWMNPTRW":3,"skill-same:01M72B7J4GAZRGTCNCRWMNPTRW":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M72B7J4GAZRGTCNCRWMNPTRW","command-creator",null,"This skill should be used when creating a Claude Code slash command. Use when users ask to \"create a command\", \"make a slash command\", \"add a command\", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: command-creator\ndescription: This skill should be used when creating a Claude Code slash command. Use when users ask to \"create a command\", \"make a slash command\", \"add a command\", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.\n---\n\n# Command Creator\n\nThis skill guides the creation of Claude Code slash commands - reusable workflows that can be invoked with `\u002Fcommand-name` in Claude Code conversations.\n\n## About Slash Commands\n\nSlash commands are markdown files stored in `.claude\u002Fcommands\u002F` (project-level) or `~\u002F.claude\u002Fcommands\u002F` (global\u002Fuser-level) that get expanded into prompts when invoked. They're ideal for:\n\n- Repetitive workflows (code review, PR submission, CI fixing)\n- Multi-step processes that need consistency\n- Agent delegation patterns\n- Project-specific automation\n\n## When to Use This Skill\n\nInvoke this skill when users:\n\n- Ask to \"create a command\" or \"make a slash command\"\n- Want to automate a repetitive workflow\n- Need to document a consistent process for reuse\n- Say \"I keep doing X, can we make a command for it?\"\n- Want to create project-specific or global commands\n\n## Bundled Resources\n\nThis skill includes reference documentation for detailed guidance:\n\n- **references\u002Fpatterns.md** - Command patterns (workflow automation, iterative fixing, agent delegation, simple execution)\n- **references\u002Fexamples.md** - Real command examples with full source (submit-stack, ensure-ci, create-implementation-plan)\n- **references\u002Fbest-practices.md** - Quality checklist, common pitfalls, writing guidelines, template structure\n\nLoad these references as needed when creating commands to understand patterns, see examples, or ensure quality.\n\n## Command Structure Overview\n\nEvery slash command is a markdown file with:\n\n```markdown\n---\ndescription: Brief description shown in \u002Fhelp (required)\nargument-hint: \u003Cplaceholder> (optional, if command takes arguments)\n---\n\n# Command Title\n\n[Detailed instructions for the agent to execute autonomously]\n```\n\n## Command Creation Workflow\n\n### Step 1: Determine Location\n\n**Auto-detect the appropriate location:**\n\n1. Check git repository status: `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n2. Default location:\n   - If in git repo → Project-level: `.claude\u002Fcommands\u002F`\n   - If not in git repo → Global: `~\u002F.claude\u002Fcommands\u002F`\n3. Allow user override:\n   - If user explicitly mentions \"global\" or \"user-level\" → Use `~\u002F.claude\u002Fcommands\u002F`\n   - If user explicitly mentions \"project\" or \"project-level\" → Use `.claude\u002Fcommands\u002F`\n\nReport the chosen location to the user before proceeding.\n\n### Step 2: Show Command Patterns\n\nHelp the user understand different command types. Load **references\u002Fpatterns.md** to see available patterns:\n\n- **Workflow Automation** - Analyze → Act → Report (e.g., submit-stack)\n- **Iterative Fixing** - Run → Parse → Fix → Repeat (e.g., ensure-ci)\n- **Agent Delegation** - Context → Delegate → Iterate (e.g., create-implementation-plan)\n- **Simple Execution** - Run command with args (e.g., codex-review)\n\nAsk the user: \"Which pattern is closest to what you want to create?\" This helps frame the conversation.\n\n### Step 3: Gather Command Information\n\nAsk the user for key information:\n\n#### A. Command Name and Purpose\n\nAsk:\n\n- \"What should the command be called?\" (for filename)\n- \"What does this command do?\" (for description field)\n\nGuidelines:\n\n- Command names MUST be kebab-case (hyphens, NOT underscores)\n  - ✅ CORRECT: `submit-stack`, `ensure-ci`, `create-from-plan`\n  - ❌ WRONG: `submit_stack`, `ensure_ci`, `create_from_plan`\n- File names match command names: `my-command.md` → invoked as `\u002Fmy-command`\n- Description should be concise, action-oriented (appears in `\u002Fhelp` output)\n\n#### B. Arguments\n\nAsk:\n\n- \"Does this command take any arguments?\"\n- \"Are arguments required or optional?\"\n- \"What should arguments represent?\"\n\nIf command takes arguments:\n\n- Add `argument-hint: \u003Cplaceholder>` to frontmatter\n- Use `\u003Cangle-brackets>` for required arguments\n- Use `[square-brackets]` for optional arguments\n\n#### C. Workflow Steps\n\nAsk:\n\n- \"What are the specific steps this command should follow?\"\n- \"What order should they happen in?\"\n- \"What tools or commands should be used?\"\n\nGather details about:\n\n- Initial analysis or checks to perform\n- Main actions to take\n- How to handle results\n- Success criteria\n- Error handling approach\n\n#### D. Tool Restrictions and Guidance\n\nAsk:\n\n- \"Should this command use any specific agents or tools?\"\n- \"Are there any tools or operations it should avoid?\"\n- \"Should it read any specific files for context?\"\n\n### Step 4: Generate Optimized Command\n\nCreate the command file with agent-optimized instructions. Load **references\u002Fbest-practices.md** for:\n\n- Template structure\n- Best practices for agent execution\n- Writing style guidelines\n- Quality checklist\n\nKey principles:\n\n- Use imperative\u002Finfinitive form (verb-first instructions)\n- Be explicit and specific\n- Include expected outcomes\n- Provide concrete examples\n- Define clear error handling\n\n### Step 5: Create the Command File\n\n1. Determine full file path:\n   - Project: `.claude\u002Fcommands\u002F[command-name].md`\n   - Global: `~\u002F.claude\u002Fcommands\u002F[command-name].md`\n\n2. Ensure directory exists:\n\n   ```bash\n   mkdir -p [directory-path]\n   ```\n\n3. Write the command file using the Write tool\n\n4. Confirm with user:\n   - Report the file location\n   - Summarize what the command does\n   - Explain how to use it: `\u002Fcommand-name [arguments]`\n\n### Step 6: Test and Iterate (Optional)\n\nIf the user wants to test:\n\n1. Suggest testing: `You can test this command by running: \u002Fcommand-name [arguments]`\n2. Be ready to iterate based on feedback\n3. Update the file with improvements as needed\n\n## Quick Tips\n\n**For detailed guidance, load the bundled references:**\n\n- Load **references\u002Fpatterns.md** when designing the command workflow\n- Load **references\u002Fexamples.md** to see how existing commands are structured\n- Load **references\u002Fbest-practices.md** before finalizing to ensure quality\n\n**Common patterns to remember:**\n\n- Use Bash tool for `pytest`, `pyright`, `ruff`, `prettier`, `make`, `gt` commands\n- Use Task tool to invoke subagents for specialized tasks\n- Check for specific files first (e.g., `.PLAN.md`) before proceeding\n- Mark todos complete immediately, not in batches\n- Include explicit error handling instructions\n- Define clear success criteria\n\n## Summary\n\nWhen creating a command:\n\n1. **Detect location** (project vs global)\n2. **Show patterns** to frame the conversation\n3. **Gather information** (name, purpose, arguments, steps, tools)\n4. **Generate optimized command** with agent-executable instructions\n5. **Create file** at appropriate location\n6. **Confirm and iterate** as needed\n\nFocus on creating commands that agents can execute autonomously, with clear steps, explicit tool usage, and proper error handling.\n","# Command Creator\n\nThis skill guides the creation of Claude Code slash commands - reusable workflows that can be invoked with `\u002Fcommand-name` in Claude Code conversations.\n\n## About Slash Commands\n\nSlash commands are markdown files stored in `.claude\u002Fcommands\u002F` (project-level) or `~\u002F.claude\u002Fcommands\u002F` (global\u002Fuser-level) that get expanded into prompts when invoked. They're ideal for:\n\n- Repetitive workflows (code review, PR submission, CI fixing)\n- Multi-step processes that need consistency\n- Agent delegation patterns\n- Project-specific automation\n\n## When to Use This Skill\n\nInvoke this skill when users:\n\n- Ask to \"create a command\" or \"make a slash command\"\n- Want to automate a repetitive workflow\n- Need to document a consistent process for reuse\n- Say \"I keep doing X, can we make a command for it?\"\n- Want to create project-specific or global commands\n\n## Bundled Resources\n\nThis skill includes reference documentation for detailed guidance:\n\n- **references\u002Fpatterns.md** - Command patterns (workflow automation, iterative fixing, agent delegation, simple execution)\n- **references\u002Fexamples.md** - Real command examples with full source (submit-stack, ensure-ci, create-implementation-plan)\n- **references\u002Fbest-practices.md** - Quality checklist, common pitfalls, writing guidelines, template structure\n\nLoad these references as needed when creating commands to understand patterns, see examples, or ensure quality.\n\n## Command Structure Overview\n\nEvery slash command is a markdown file with:\n\n```markdown\n---\ndescription: Brief description shown in \u002Fhelp (required)\nargument-hint: \u003Cplaceholder> (optional, if command takes arguments)\n---\n\n# Command Title\n\n[Detailed instructions for the agent to execute autonomously]\n```\n\n## Command Creation Workflow\n\n### Step 1: Determine Location\n\n**Auto-detect the appropriate location:**\n\n1. Check git repository status: `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`\n2. Default location:\n   - If in git repo → Project-level: `.claude\u002Fcommands\u002F`\n   - If not in git repo → Global: `~\u002F.claude\u002Fcommands\u002F`\n3. Allow user override:\n   - If user explicitly mentions \"global\" or \"user-level\" → Use `~\u002F.claude\u002Fcommands\u002F`\n   - If user explicitly mentions \"project\" or \"project-level\" → Use `.claude\u002Fcommands\u002F`\n\nReport the chosen location to the user before proceeding.\n\n### Step 2: Show Command Patterns\n\nHelp the user understand different command types. Load **references\u002Fpatterns.md** to see available patterns:\n\n- **Workflow Automation** - Analyze → Act → Report (e.g., submit-stack)\n- **Iterative Fixing** - Run → Parse → Fix → Repeat (e.g., ensure-ci)\n- **Agent Delegation** - Context → Delegate → Iterate (e.g., create-implementation-plan)\n- **Simple Execution** - Run command with args (e.g., codex-review)\n\nAsk the user: \"Which pattern is closest to what you want to create?\" This helps frame the conversation.\n\n### Step 3: Gather Command Information\n\nAsk the user for key information:\n\n#### A. Command Name and Purpose\n\nAsk:\n\n- \"What should the command be called?\" (for filename)\n- \"What does this command do?\" (for description field)\n\nGuidelines:\n\n- Command names MUST be kebab-case (hyphens, NOT underscores)\n  - ✅ CORRECT: `submit-stack`, `ensure-ci`, `create-from-plan`\n  - ❌ WRONG: `submit_stack`, `ensure_ci`, `create_from_plan`\n- File names match command names: `my-command.md` → invoked as `\u002Fmy-command`\n- Description should be concise, action-oriented (appears in `\u002Fhelp` output)\n\n#### B. Arguments\n\nAsk:\n\n- \"Does this command take any arguments?\"\n- \"Are arguments required or optional?\"\n- \"What should arguments represent?\"\n\nIf command takes arguments:\n\n- Add `argument-hint: \u003Cplaceholder>` to frontmatter\n- Use `\u003Cangle-brackets>` for required arguments\n- Use `[square-brackets]` for optional arguments\n\n#### C. Workflow Steps\n\nAsk:\n\n- \"What are the specific steps this command should follow?\"\n- \"What order should they happen in?\"\n- \"What tools or commands should be used?\"\n\nGather details about:\n\n- Initial analysis or checks to perform\n- Main actions to take\n- How to handle results\n- Success criteria\n- Error handling approach\n\n#### D. Tool Restrictions and Guidance\n\nAsk:\n\n- \"Should this command use any specific agents or tools?\"\n- \"Are there any tools or operations it should avoid?\"\n- \"Should it read any specific files for context?\"\n\n### Step 4: Generate Optimized Command\n\nCreate the command file with agent-optimized instructions. Load **references\u002Fbest-practices.md** for:\n\n- Template structure\n- Best practices for agent execution\n- Writing style guidelines\n- Quality checklist\n\nKey principles:\n\n- Use imperative\u002Finfinitive form (verb-first instructions)\n- Be explicit and specific\n- Include expected outcomes\n- Provide concrete examples\n- Define clear error handling\n\n### Step 5: Create the Command File\n\n1. Determine full file path:\n   - Project: `.claude\u002Fcommands\u002F[command-name].md`\n   - Global: `~\u002F.claude\u002Fcommands\u002F[command-name].md`\n\n2. Ensure directory exists:\n\n   ```bash\n   mkdir -p [directory-path]\n   ```\n\n3. Write the command file using the Write tool\n\n4. Confirm with user:\n   - Report the file location\n   - Summarize what the command does\n   - Explain how to use it: `\u002Fcommand-name [arguments]`\n\n### Step 6: Test and Iterate (Optional)\n\nIf the user wants to test:\n\n1. Suggest testing: `You can test this command by running: \u002Fcommand-name [arguments]`\n2. Be ready to iterate based on feedback\n3. Update the file with improvements as needed\n\n## Quick Tips\n\n**For detailed guidance, load the bundled references:**\n\n- Load **references\u002Fpatterns.md** when designing the command workflow\n- Load **references\u002Fexamples.md** to see how existing commands are structured\n- Load **references\u002Fbest-practices.md** before finalizing to ensure quality\n\n**Common patterns to remember:**\n\n- Use Bash tool for `pytest`, `pyright`, `ruff`, `prettier`, `make`, `gt` commands\n- Use Task tool to invoke subagents for specialized tasks\n- Check for specific files first (e.g., `.PLAN.md`) before proceeding\n- Mark todos complete immediately, not in batches\n- Include explicit error handling instructions\n- Define clear success criteria\n\n## Summary\n\nWhen creating a command:\n\n1. **Detect location** (project vs global)\n2. **Show patterns** to frame the conversation\n3. **Gather information** (name, purpose, arguments, steps, tools)\n4. **Generate optimized command** with agent-executable instructions\n5. **Create file** at appropriate location\n6. **Confirm and iterate** as needed\n\nFocus on creating commands that agents can execute autonomously, with clear steps, explicit tool usage, and proper error handling.\n",{"name":5,"description":7},"main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fcommand-creator","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Sansar35\u002Fclaude-agent --skill command-creator",{"tool":35,"command":36},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill command-creator",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill command-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002FSKILL.md",true,[43,49,53,57,61],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},".skill-source.json","REFERENCE","参考文档",550,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002F.skill-source.json",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"README.md",15507,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002FREADME.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fbest-practices.md",13806,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002Freferences\u002Fbest-practices.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fexamples.md",15806,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002Freferences\u002Fexamples.md",{"path":62,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fpatterns.md",9002,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fcommand-creator\u002Freferences\u002Fpatterns.md",[66,73,80,87,94,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","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\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]