[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1TS7X0CCEB1B38TPX9M97":3,"skill-same:01M7C1TS7X0CCEB1B38TPX9M97":110},{"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":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C1TS7X0CCEB1B38TPX9M97","cc-plugins",null,"Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle","zak-keown\u002Fmoe","zak-keown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320717241?v=4","01M7BZFXME0NW6TQX0H7AZM2KS","01M7BZFXN32VR0JN5AATRD53H4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cc-plugins\ndescription: Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle\n---\n\n# Developing Claude Code Plugins\n\n## Overview\n\nThis skill provides efficient workflows for creating Claude Code plugins. Use it to make plugin development fast and correct - it synthesizes official docs into actionable steps and provides working examples.\n\n## When to Use\n\nUse this skill when:\n- Creating a new Claude Code plugin from scratch\n- Adding components to an existing plugin (skills, commands, hooks, MCP servers)\n- Setting up a development marketplace for testing\n- Troubleshooting plugin structure issues\n- Understanding plugin architecture and patterns\n- Releasing a plugin (versioning, tagging, marketplace distribution)\n- Publishing updates or maintaining existing plugins\n\n**For comprehensive official documentation**, use native skill discovery to load `cc-config` for full docs.\n\n## Quick Reference\n\n| Need to... | Read This | Official Docs |\n|-----------|-----------|---------------|\n| Understand directory structure | `references\u002Fplugin-structure.md` | `plugins.md` |\n| Choose a plugin pattern | `references\u002Fcommon-patterns.md` | `plugins.md` |\n| Make hooks work cross-platform | `references\u002Fpolyglot-hooks.md` | `hooks.md` |\n| Debug plugin issues | `references\u002Ftroubleshooting.md` | Various |\n| See working examples | `examples\u002F` directory | N\u002FA |\n\n## Plugin Development Workflow\n\n### Phase 1: Plan\n\nBefore writing code:\n\n1. **Define your plugin's purpose**\n   - What problem does it solve?\n   - Who will use it?\n   - What components will it need?\n\n2. **Choose your pattern** (read `references\u002Fcommon-patterns.md`)\n   - Simple plugin with one skill?\n   - MCP integration with guidance?\n   - Command collection?\n   - Full-featured platform?\n\n3. **Review examples**\n   - `examples\u002Fsimple-greeter-plugin\u002F` - Minimal plugin\n   - `examples\u002Ffull-featured-plugin\u002F` - All components\n   - Installed plugins in `~\u002F.claude\u002Fplugins\u002F`\n\n### Phase 2: Create Structure\n\n1. **Create directories** (see `references\u002Fplugin-structure.md` for details):\n   ```bash\n   mkdir -p my-plugin\u002F.claude-plugin\n   mkdir -p my-plugin\u002Fskills\n   # Add other component directories as needed\n   ```\n\n2. **Declare the plugin in `moe-mint.yaml`** — do NOT hand-write a manifest.\n\n   In this repo, `@bubstack\u002Fmoe-mint` generates `.claude-plugin\u002Fplugin.json`,\n   `.claude-plugin\u002Fmarketplace.json` and every other harness manifest from one\n   config file. A hand-edited manifest is overwritten by the next `generate`\n   and reported as drift by `moe-mint validate`.\n\n   ```yaml\n   name: my-plugin\n   version: 1.0.0\n   description: What your plugin does\n   author:\n     name: Your Name\n   bootstrap: none        # or { skill: \u003Cname> } for a session-start skill\n   ```\n\n   Then:\n   ```bash\n   moe-mint generate\n   ```\n\n   `references\u002Fplugin-structure.md` documents the manifest shape mint emits.\n   Read it to understand the output; do not author the output.\n\n3. **Outside this repo**, where there is no mint, write\n   `.claude-plugin\u002Fplugin.json` and a local `.claude-plugin\u002Fmarketplace.json`\n   by hand in the shapes `references\u002Fplugin-structure.md` gives. Everything\n   below applies either way.\n\n### Phase 3: Add Components\n\nUse maintain a task artifact with `write_to_file` and `replace_file_content` to log component creation:\n\n**Example:**\n```\n- Create skill: main-workflow\n- Add command: \u002Fhello\n- Configure hooks\n- Write README\n- Test installation\n```\n\nFor each component type, see:\n- **Format\u002Fsyntax**: `references\u002Fplugin-structure.md`\n- **When to use**: `references\u002Fcommon-patterns.md`\n- **Working code**: `examples\u002F` directory\n\n### Phase 4: Test Locally\n\n1. **Install for testing**:\n   ```bash\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmy-plugin\n   \u002Fplugin install my-plugin@my-dev\n   ```\n   Then restart Claude Code.\n\n2. **Test each component**:\n   - Skills: Ask for tasks matching skill descriptions\n   - Commands: Run `\u002Fyour-command`\n   - MCP servers: Check tools are available\n   - Hooks: Trigger relevant events\n\n3. **Iterate**:\n   ```bash\n   \u002Fplugin uninstall my-plugin@my-dev\n   # Make changes\n   \u002Fplugin install my-plugin@my-dev\n   # Restart Claude Code\n   ```\n\n### Phase 5: Debug and Refine\n\nIf something doesn't work, read `references\u002Ftroubleshooting.md` for:\n- Plugin not loading\n- Skill not triggering\n- Command not appearing\n- MCP server not starting\n- Hooks not firing\n\nCommon issues are usually:\n- Wrong directory structure\n- Hardcoded paths (use `${CLAUDE_PLUGIN_ROOT}`)\n- Forgot to restart Claude Code\n- Missing executable permissions on scripts\n\n### Phase 6: Release and Distribute\n\n1. **Write README** with:\n   - What the plugin does\n   - Installation instructions\n   - Usage examples\n   - Component descriptions\n\n2. **Bump the version** with the tool that owns it:\n   ```bash\n   moe-mint bump \u003Cnew-version>      # rewrites moe-mint.yaml and regenerates\n   moe-mint bump --audit            # finds stray copies of the old version\n   ```\n   Semantic versioning, `major.minor.patch`. Record what changed in the\n   package's own notes — never in an upstream `CHANGELOG.md` or\n   `RELEASE-NOTES.md`, which are inherited record and are not ours to edit.\n\n3. **Commit to a branch and open a merge request.** Do not push to the\n   default branch and do not tag a release: CI runs from one root\n   `.gitlab-ci.yml`, and there is no release workflow to trigger.\n\n4. **Distribution — one path only.**\n\n   Moe publishes nothing publicly (ARCHITECTURE.md section 8, decided\n   2026-08-31). No crates.io, no PyPI, no npm, no public GitHub marketplace.\n   A plugin ships by being listed in this repo's single root\n   `.claude-plugin\u002Fmarketplace.json`, which points at the generated tree under\n   `\u002Fplugins\u002F\u003Cname>`:\n\n   ```json\n   {\n     \"name\": \"moe\",\n     \"plugins\": [{\n       \"name\": \"my-plugin\",\n       \"source\": \".\u002Fplugins\u002Fmy-plugin\",\n       \"version\": \"1.0.0\",\n       \"description\": \"What your plugin does\",\n       \"strict\": true\n     }]\n   }\n   ```\n\n   Teammates install from a clone:\n   ```\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmoe\n   \u002Fplugin install my-plugin@moe\n   ```\n\n   Anything that genuinely must be consumable outside the repo goes to the\n   GitLab instance registry under the `@bubstack` scope. Nothing else leaves\n   the company.\n\n5. **Test the install** from a clean checkout:\n   ```\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmoe\n   \u002Fplugin install my-plugin@moe\n   # verify each component, then\n   \u002Fplugin uninstall my-plugin@moe\n   ```\n\n6. **Announce and maintain**: tell the team, watch for issues, plan the next\n   change. There are no public release notes to write.\n\n## Critical Rules\n\n**Always follow these** (from `references\u002Fplugin-structure.md`):\n\n1. **`.claude-plugin\u002F` contains ONLY manifests** (`plugin.json` and optionally `marketplace.json`)\n   - ❌ Don't put skills, commands, or other components inside\n   - ✅ Put them at plugin root\n\n2. **Use `${CLAUDE_PLUGIN_ROOT}` for all paths in config files**\n   - Makes plugin portable across systems\n   - Required for hooks, MCP servers, scripts\n\n3. **Use relative paths in `plugin.json`**\n   - Start with `.\u002F`\n   - Relative to plugin root\n\n4. **Make scripts executable**\n   - `chmod +x script.sh`\n   - Required for hooks and MCP servers\n\n## Resources in This Skill\n\n- **`references\u002Fplugin-structure.md`** - Directory layout, file formats, component syntax\n- **`references\u002Fcommon-patterns.md`** - When to use each plugin pattern, examples\n- **`references\u002Fpolyglot-hooks.md`** - Cross-platform hook wrapper for Windows\u002FmacOS\u002FLinux\n- **`references\u002Ftroubleshooting.md`** - Debug guide for common issues\n- **`examples\u002Fsimple-greeter-plugin\u002F`** - Minimal working plugin (one skill)\n- **`examples\u002Ffull-featured-plugin\u002F`** - Complete plugin with all components (includes `run-hook.cmd`)\n\n## Cross-References\n\nFor deep dives into official documentation, use the `cc-config` skill to access:\n- `plugins.md` - Plugin development overview\n- `plugins-reference.md` - Complete API reference\n- `skills.md` - Skill authoring guide\n- `slash-commands.md` - Command format\n- `hooks.md`, `hooks-guide.md` - Hook system\n- `mcp.md` - MCP server integration\n- `plugin-marketplaces.md` - Distribution\n\n## Best Practices\n\n1. **Start simple** - Begin with minimal structure, add complexity when needed\n2. **Test frequently** - Install → test → uninstall → modify → repeat\n3. **Use examples** - Copy patterns from working plugins\n4. **Follow conventions** - Match style of existing plugins\n5. **Document everything** - Clear README helps users and future you\n6. **Version properly** - Use semantic versioning (major.minor.patch)\n\n## Workflow Summary\n\n```\nPlan → Choose pattern, review examples\nCreate → Make structure, write manifests\nAdd → Build components (skills, commands, etc.)\nTest → Install via dev marketplace\nDebug → Use troubleshooting guide\nRelease → Version, tag, distribute via marketplace\nMaintain → Monitor, update, support users\n```\n\n**The correct path is the fast path.** Use references, follow patterns, test frequently.\n","# Developing Claude Code Plugins\n\n## Overview\n\nThis skill provides efficient workflows for creating Claude Code plugins. Use it to make plugin development fast and correct - it synthesizes official docs into actionable steps and provides working examples.\n\n## When to Use\n\nUse this skill when:\n- Creating a new Claude Code plugin from scratch\n- Adding components to an existing plugin (skills, commands, hooks, MCP servers)\n- Setting up a development marketplace for testing\n- Troubleshooting plugin structure issues\n- Understanding plugin architecture and patterns\n- Releasing a plugin (versioning, tagging, marketplace distribution)\n- Publishing updates or maintaining existing plugins\n\n**For comprehensive official documentation**, use native skill discovery to load `cc-config` for full docs.\n\n## Quick Reference\n\n| Need to... | Read This | Official Docs |\n|-----------|-----------|---------------|\n| Understand directory structure | `references\u002Fplugin-structure.md` | `plugins.md` |\n| Choose a plugin pattern | `references\u002Fcommon-patterns.md` | `plugins.md` |\n| Make hooks work cross-platform | `references\u002Fpolyglot-hooks.md` | `hooks.md` |\n| Debug plugin issues | `references\u002Ftroubleshooting.md` | Various |\n| See working examples | `examples\u002F` directory | N\u002FA |\n\n## Plugin Development Workflow\n\n### Phase 1: Plan\n\nBefore writing code:\n\n1. **Define your plugin's purpose**\n   - What problem does it solve?\n   - Who will use it?\n   - What components will it need?\n\n2. **Choose your pattern** (read `references\u002Fcommon-patterns.md`)\n   - Simple plugin with one skill?\n   - MCP integration with guidance?\n   - Command collection?\n   - Full-featured platform?\n\n3. **Review examples**\n   - `examples\u002Fsimple-greeter-plugin\u002F` - Minimal plugin\n   - `examples\u002Ffull-featured-plugin\u002F` - All components\n   - Installed plugins in `~\u002F.claude\u002Fplugins\u002F`\n\n### Phase 2: Create Structure\n\n1. **Create directories** (see `references\u002Fplugin-structure.md` for details):\n   ```bash\n   mkdir -p my-plugin\u002F.claude-plugin\n   mkdir -p my-plugin\u002Fskills\n   # Add other component directories as needed\n   ```\n\n2. **Declare the plugin in `moe-mint.yaml`** — do NOT hand-write a manifest.\n\n   In this repo, `@bubstack\u002Fmoe-mint` generates `.claude-plugin\u002Fplugin.json`,\n   `.claude-plugin\u002Fmarketplace.json` and every other harness manifest from one\n   config file. A hand-edited manifest is overwritten by the next `generate`\n   and reported as drift by `moe-mint validate`.\n\n   ```yaml\n   name: my-plugin\n   version: 1.0.0\n   description: What your plugin does\n   author:\n     name: Your Name\n   bootstrap: none        # or { skill: \u003Cname> } for a session-start skill\n   ```\n\n   Then:\n   ```bash\n   moe-mint generate\n   ```\n\n   `references\u002Fplugin-structure.md` documents the manifest shape mint emits.\n   Read it to understand the output; do not author the output.\n\n3. **Outside this repo**, where there is no mint, write\n   `.claude-plugin\u002Fplugin.json` and a local `.claude-plugin\u002Fmarketplace.json`\n   by hand in the shapes `references\u002Fplugin-structure.md` gives. Everything\n   below applies either way.\n\n### Phase 3: Add Components\n\nUse maintain a task artifact with `write_to_file` and `replace_file_content` to log component creation:\n\n**Example:**\n```\n- Create skill: main-workflow\n- Add command: \u002Fhello\n- Configure hooks\n- Write README\n- Test installation\n```\n\nFor each component type, see:\n- **Format\u002Fsyntax**: `references\u002Fplugin-structure.md`\n- **When to use**: `references\u002Fcommon-patterns.md`\n- **Working code**: `examples\u002F` directory\n\n### Phase 4: Test Locally\n\n1. **Install for testing**:\n   ```bash\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmy-plugin\n   \u002Fplugin install my-plugin@my-dev\n   ```\n   Then restart Claude Code.\n\n2. **Test each component**:\n   - Skills: Ask for tasks matching skill descriptions\n   - Commands: Run `\u002Fyour-command`\n   - MCP servers: Check tools are available\n   - Hooks: Trigger relevant events\n\n3. **Iterate**:\n   ```bash\n   \u002Fplugin uninstall my-plugin@my-dev\n   # Make changes\n   \u002Fplugin install my-plugin@my-dev\n   # Restart Claude Code\n   ```\n\n### Phase 5: Debug and Refine\n\nIf something doesn't work, read `references\u002Ftroubleshooting.md` for:\n- Plugin not loading\n- Skill not triggering\n- Command not appearing\n- MCP server not starting\n- Hooks not firing\n\nCommon issues are usually:\n- Wrong directory structure\n- Hardcoded paths (use `${CLAUDE_PLUGIN_ROOT}`)\n- Forgot to restart Claude Code\n- Missing executable permissions on scripts\n\n### Phase 6: Release and Distribute\n\n1. **Write README** with:\n   - What the plugin does\n   - Installation instructions\n   - Usage examples\n   - Component descriptions\n\n2. **Bump the version** with the tool that owns it:\n   ```bash\n   moe-mint bump \u003Cnew-version>      # rewrites moe-mint.yaml and regenerates\n   moe-mint bump --audit            # finds stray copies of the old version\n   ```\n   Semantic versioning, `major.minor.patch`. Record what changed in the\n   package's own notes — never in an upstream `CHANGELOG.md` or\n   `RELEASE-NOTES.md`, which are inherited record and are not ours to edit.\n\n3. **Commit to a branch and open a merge request.** Do not push to the\n   default branch and do not tag a release: CI runs from one root\n   `.gitlab-ci.yml`, and there is no release workflow to trigger.\n\n4. **Distribution — one path only.**\n\n   Moe publishes nothing publicly (ARCHITECTURE.md section 8, decided\n   2026-08-31). No crates.io, no PyPI, no npm, no public GitHub marketplace.\n   A plugin ships by being listed in this repo's single root\n   `.claude-plugin\u002Fmarketplace.json`, which points at the generated tree under\n   `\u002Fplugins\u002F\u003Cname>`:\n\n   ```json\n   {\n     \"name\": \"moe\",\n     \"plugins\": [{\n       \"name\": \"my-plugin\",\n       \"source\": \".\u002Fplugins\u002Fmy-plugin\",\n       \"version\": \"1.0.0\",\n       \"description\": \"What your plugin does\",\n       \"strict\": true\n     }]\n   }\n   ```\n\n   Teammates install from a clone:\n   ```\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmoe\n   \u002Fplugin install my-plugin@moe\n   ```\n\n   Anything that genuinely must be consumable outside the repo goes to the\n   GitLab instance registry under the `@bubstack` scope. Nothing else leaves\n   the company.\n\n5. **Test the install** from a clean checkout:\n   ```\n   \u002Fplugin marketplace add \u002Fpath\u002Fto\u002Fmoe\n   \u002Fplugin install my-plugin@moe\n   # verify each component, then\n   \u002Fplugin uninstall my-plugin@moe\n   ```\n\n6. **Announce and maintain**: tell the team, watch for issues, plan the next\n   change. There are no public release notes to write.\n\n## Critical Rules\n\n**Always follow these** (from `references\u002Fplugin-structure.md`):\n\n1. **`.claude-plugin\u002F` contains ONLY manifests** (`plugin.json` and optionally `marketplace.json`)\n   - ❌ Don't put skills, commands, or other components inside\n   - ✅ Put them at plugin root\n\n2. **Use `${CLAUDE_PLUGIN_ROOT}` for all paths in config files**\n   - Makes plugin portable across systems\n   - Required for hooks, MCP servers, scripts\n\n3. **Use relative paths in `plugin.json`**\n   - Start with `.\u002F`\n   - Relative to plugin root\n\n4. **Make scripts executable**\n   - `chmod +x script.sh`\n   - Required for hooks and MCP servers\n\n## Resources in This Skill\n\n- **`references\u002Fplugin-structure.md`** - Directory layout, file formats, component syntax\n- **`references\u002Fcommon-patterns.md`** - When to use each plugin pattern, examples\n- **`references\u002Fpolyglot-hooks.md`** - Cross-platform hook wrapper for Windows\u002FmacOS\u002FLinux\n- **`references\u002Ftroubleshooting.md`** - Debug guide for common issues\n- **`examples\u002Fsimple-greeter-plugin\u002F`** - Minimal working plugin (one skill)\n- **`examples\u002Ffull-featured-plugin\u002F`** - Complete plugin with all components (includes `run-hook.cmd`)\n\n## Cross-References\n\nFor deep dives into official documentation, use the `cc-config` skill to access:\n- `plugins.md` - Plugin development overview\n- `plugins-reference.md` - Complete API reference\n- `skills.md` - Skill authoring guide\n- `slash-commands.md` - Command format\n- `hooks.md`, `hooks-guide.md` - Hook system\n- `mcp.md` - MCP server integration\n- `plugin-marketplaces.md` - Distribution\n\n## Best Practices\n\n1. **Start simple** - Begin with minimal structure, add complexity when needed\n2. **Test frequently** - Install → test → uninstall → modify → repeat\n3. **Use examples** - Copy patterns from working plugins\n4. **Follow conventions** - Match style of existing plugins\n5. **Document everything** - Clear README helps users and future you\n6. **Version properly** - Use semantic versioning (major.minor.patch)\n\n## Workflow Summary\n\n```\nPlan → Choose pattern, review examples\nCreate → Make structure, write manifests\nAdd → Build components (skills, commands, etc.)\nTest → Install via dev marketplace\nDebug → Use troubleshooting guide\nRelease → Version, tag, distribute via marketplace\nMaintain → Monitor, update, support users\n```\n\n**The correct path is the fast path.** Use references, follow patterns, test frequently.\n",{"name":5,"description":7},"main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","plugins\u002Fmoe\u002Fskills\u002Fcc-plugins",1,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe","https:\u002F\u002Fgithub.com\u002Fzak-keown","2026-09-05 06:29:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zak-keown\u002Fmoe --skill cc-plugins",{"tool":36,"command":37},"bunx","bunx skills add zak-keown\u002Fmoe --skill cc-plugins",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill cc-plugins","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002FSKILL.md",true,[44,50,54,58,62,68,74,78,82,86,90,94,98,102,106],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"examples\u002Ffull-featured-plugin\u002F.claude-plugin\u002Fmarketplace.json","REFERENCE","参考文档",438,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002F.claude-plugin\u002Fmarketplace.json",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"examples\u002Ffull-featured-plugin\u002F.claude-plugin\u002Fplugin.json",674,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002F.claude-plugin\u002Fplugin.json",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"examples\u002Ffull-featured-plugin\u002Fcommands\u002Fhello.md",683,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fcommands\u002Fhello.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"examples\u002Ffull-featured-plugin\u002Fhooks\u002Fhooks.json",480,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fhooks\u002Fhooks.json",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"examples\u002Ffull-featured-plugin\u002Fhooks\u002Fpost-write.sh","SCRIPT","脚本",305,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fhooks\u002Fpost-write.sh",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"examples\u002Ffull-featured-plugin\u002Fhooks\u002Frun-hook.cmd","OTHER","其他",391,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fhooks\u002Frun-hook.cmd",{"path":75,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":76,"sourceHtmlUrl":77},"examples\u002Ffull-featured-plugin\u002Fhooks\u002Fsession-init.sh",420,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fhooks\u002Fsession-init.sh",{"path":79,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":80,"sourceHtmlUrl":81},"examples\u002Ffull-featured-plugin\u002Fmcp\u002Fserver.js",730,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002Fmcp\u002Fserver.js",{"path":83,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":84,"sourceHtmlUrl":85},"examples\u002Ffull-featured-plugin\u002FREADME.md",2819,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Ffull-featured-plugin\u002FREADME.md",{"path":87,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":88,"sourceHtmlUrl":89},"examples\u002Fsimple-greeter-plugin\u002F.claude-plugin\u002Fplugin.json",459,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Fsimple-greeter-plugin\u002F.claude-plugin\u002Fplugin.json",{"path":91,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":92,"sourceHtmlUrl":93},"examples\u002Fsimple-greeter-plugin\u002FREADME.md",1370,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Fexamples\u002Fsimple-greeter-plugin\u002FREADME.md",{"path":95,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcommon-patterns.md",6313,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Freferences\u002Fcommon-patterns.md",{"path":99,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fplugin-structure.md",6260,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Freferences\u002Fplugin-structure.md",{"path":103,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fpolyglot-hooks.md",7058,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Freferences\u002Fpolyglot-hooks.md",{"path":107,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Ftroubleshooting.md",8970,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fcc-plugins\u002Freferences\u002Ftroubleshooting.md",[111,118,125,132,139,146],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M7C1Z5362Y8NVRZ69HWP0ZD0","write-skill","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":18},"01M7C1YZ9966WK9R6ZRPCGWF3G","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":18},"01M7C1YMR4SJD7BPBBPXZCVGVH","write-clearly","Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-clearly\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":18},"01M7C1YH9805YSM0N20VQAVSXF","windows-vm","Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwindows-vm\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":18},"01M7C1YD87SCNEJ2C9B8HFR2NQ","verify-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":18},"01M7C1YARDEHT0TJ9BRG30ZCF4","using-moe","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fusing-moe\u002FSKILL.md",[],[]]