From my-plugin-dev
Development toolkit for the my-claude-plugins marketplace. Use when working on plugin development, troubleshooting plugin issues, creating new plugins, or maintaining the my-claude-plugins repository.
How this skill is triggered — by the user, by Claude, or both
Slash command
/my-plugin-dev:devThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Development toolkit for the **my-claude-plugins** marketplace repository (`dkmaker/my-claude-plugins`).
Development toolkit for the my-claude-plugins marketplace repository (dkmaker/my-claude-plugins).
Before doing anything, gather context:
Check if we're inside the my-claude-plugins repo:
# Check for marketplace.json with our known plugins
if [ -f ".claude-plugin/marketplace.json" ]; then
jq -r '.name' .claude-plugin/marketplace.json
fi
If not in the repo, check common locations:
/home/cp/code/dkmaker/my-claude-pluginsIf repo not found, ask the user for the path.
Check how plugins are loaded:
--plugin-dir pointing to the repo source~/.claude/plugins/cache/my-claude-plugins/If production mode is detected, warn:
You're running with cached plugins. Changes to source files won't take effect. To develop locally, restart Claude Code with:
claude --plugin-dir /home/cp/code/dkmaker/my-claude-plugins/<plugin-name>
# Current branch and dirty state
git status --short --branch
# Which plugins have changes
git diff --name-only | grep -oP '^[^/]+' | sort -u
Present a context summary to the user before proceeding.
This skill depends on claude-docs CLI as the source of truth for Claude Code conventions.
Priority chain:
Check for claude-docs: Run command -v claude-docs
claude-docs get <slug> before generating any plugin componentplugins, plugins-reference, skills, hooks-guide, hooks, mcp, plugin-marketplacesclaude-docs list to discover all available topicsIf claude-docs not found: Ask the user to enable the claude-expert plugin:
The
claude-expertplugin provides theclaude-docsCLI which is the source of truth for Claude Code documentation. Enable it with:/plugin install claude-expert@my-claude-plugins
Last resort fallback: If user declines claude-expert, fetch documentation directly:
https://code.claude.com/docs/llms.txtIMPORTANT: Before generating any plugin component (hooks, skills, MCP config, plugin.json), ALWAYS verify the current format via this documentation chain. Never rely on training data for Claude Code specifics.
Based on $ARGUMENTS:
| First argument | Action |
|---|---|
develop | Load workflows/develop.md — full dev lifecycle |
troubleshoot | Load workflows/troubleshoot.md — diagnostics & debugging |
scaffold | Load workflows/scaffold.md — create a new plugin |
| (none) | Show the three options below and ask which workflow |
If no argument provided, present:
Also show:
claude command line for local dev testingLoad repo-map.md when you need to understand the current state of any plugin.
Load plugin-templates.md when creating or modifying plugin components.
npx claudepluginhub dkmaker/my-claude-plugins --plugin my-plugin-devDevelops Claude Code plugins through planning, structure setup, component addition (skills, commands, hooks, MCP), dev marketplace testing, release workflows, with patterns and examples.
Guides developers in creating, scaffolding, validating, and publishing Claude Code plugins including directory structure, plugin.json schema, YAML frontmatter, agents, commands, skills, and marketplace deployment.
Guides Claude Code plugin creation, structure (plugin.json, commands/agents/skills/hooks), installation (/plugin), marketplaces, team workflows, testing, debugging, and settings. Delegates to docs-management.