Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub ivintik/private-claude-marketplace --plugin plugin-opsHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-ops:optimizeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
Validates Claude Code plugin structure and manifest, launches agent to fix issues with user confirmation, increments version, re-validates, and reports. For plugin quality optimization.
Analyzes SKILL.md files, plugin prompts, and command instructions; scores clarity, safety, effectiveness, completeness, conciseness; provides rewrites and edits.
Analyzes Claude Code plugin skills to identify script opportunities for performance gains (fewer tokens, faster execution, consistency), then creates scripts optionally via --analyze, --create, or --all.
Share bugs, ideas, or general feedback.
Analyze and optimize a plugin's knowledge and skills for size and clarity.
Parse $ARGUMENTS:
--dry-run: Report changes without applying. This is the default — changes are only applied when user explicitly omits this flag.--target: Focus area — knowledge (default), skills, or all.Cache guard: ~/.claude/plugins/cache/ is READ-ONLY. Resolve to the real git repo via atlas: atlas_search_projects(query="plugin-name").
For each skill, evaluate:
Description quality (most impactful — poor descriptions mean skills never trigger):
Instruction clarity:
Cross-skill consistency:
Apply: fix broken refs, sharpen descriptions, align skill/agent pairs, clarify steps.
For deeper skill refinement (test prompts, eval loops, description optimization), recommend /skill-creator (from the plugin-dev plugin).
Prepend optimization entry to REFLECTIONS.md (format from knowledge/lifecycle-formats.md)
Optimization {applied|dry-run} for {plugin-name} v{version}
Knowledge: {before} KB → {after} KB ({reduction}%)
- {file}: {change}
Skills: {N} modified
- {skill}: {change}