claude-plugin-marketplace: Command for Claude Code

Auto-Improve All Plugins

Purpose

Fully autonomous improvement of every plugin in the claude-plugin-marketplace repository. Each plugin's expert agent will:

1. Self-determine what needs improvement using web search and Context7
2. Autonomously decide what features/fixes to add
3. Complete all improvements themselves (no pausing, no asking)
4. Minimize context usage by doing all work within agent contexts

This command uses agent-driven execution to keep primary context window usage minimal while maximizing improvement quality.

Process

DO NOT do the work yourself. Launch agents and let them do ALL the work autonomously.

Step 1: Launch All Plugin Expert Agents in Parallel

Use a single message with multiple Task tool calls to launch all agents simultaneously. This keeps your context usage minimal.

Plugins to Improve (14 total):

• adf-master → adf-master:adf-expert
• ado-master → ado-master:ado-expert
• azure-master → azure-master:azure-resources-expert
• azure-to-docker-master → azure-to-docker-master:docker-compose-generator
• bash-master → general-purpose agent
• context-master → Explore agent (very thorough)
• docker-master → docker-master:docker-expert
• git-master → general-purpose agent
• plugin-master → plugin-master:plugin-architect
• powershell-master → powershell-master:powershell-expert
• salesforce-master → salesforce-master:sf-integration-expert
• ssdt-master → ssdt-master:ssdt-expert
• terraform-master → terraform-master:terraform-expert
• test-master → test-master:test-expert

Step 2: Provide Autonomous Improvement Instructions

Give each agent these instructions (they will work independently in their own contexts):

You are the expert for the [PLUGIN_NAME] plugin in the claude-plugin-marketplace repository.

Your task: AUTONOMOUSLY IMPROVE your plugin. You will:
1. Self-determine what needs improvement (no one will tell you what to do)
2. Decide what features/fixes to add (use your expert judgment)
3. Complete ALL improvements yourself (do not pause or ask for approval)
4. Work entirely within your own context (minimize main context usage)

AUTONOMOUS IMPROVEMENT PROCESS:

1. **SELF-ASSESS Your Plugin (You Decide What's Needed)**
   - Read all files in plugins/[PLUGIN_NAME]/ directory
   - Use your expert knowledge to identify gaps
   - Compare against your domain expertise
   - Look for outdated patterns, missing features, verbose content

2. **DISCOVER 2025 State-of-the-Art (Web Search + Context7)**
   - WebSearch: "[TECHNOLOGY] new features 2025"
   - WebSearch: "[TECHNOLOGY] breaking changes 2025"
   - WebSearch: "[TECHNOLOGY] latest version 2025"
   - WebSearch: "[TECHNOLOGY] best practices 2025"
   - Context7: Get current library documentation
   - YOU DECIDE what's worth adding based on findings

3. **AUTONOMOUSLY DECIDE Improvements to Make**
   Based on your assessment and research, decide:
   - Which 2025 features to add (pick the most valuable ones)
   - What bugs/issues to fix (prioritize critical ones)
   - What content to optimize (target 20-40% reduction)
   - What new files to create (if gaps are significant)
   - What version bump is appropriate

   DO NOT ask for approval. Use your expert judgment.

4. **COMPLETE ALL IMPROVEMENTS (No Pausing)**
   Execute your decisions:
   - CREATE new command/skill files for new capabilities
   - EDIT existing files to add features and fix issues
   - USE `scripts/version_ops.py` for any plugin version bumps
   - REMOVE duplicate content across files
   - REPLACE deprecated features with current alternatives
   - VALIDATE all examples work with current versions
   - **BUMP versions with `python3 scripts/version_ops.py`** (MANDATORY - never hand-edit version fields)
   - **ALIGN metadata**: Ensure `python3 scripts/version_ops.py --validate --metadata all` passes; sync marketplace keyword mirrors from plugin-owned plugin.json when needed
   - **ENSURE PORTABILITY** - Remove all user-specific paths, machine names, personal info, private project references, PRs, commits, companies, and internal paths

   Complete everything before returning results.

5. **REPORT Your Autonomous Improvements**
   After completing all improvements, provide:
   - **Decisions Made**: What you decided to improve and why
   - **New Features Added**: List new 2025 features now documented
   - **Files Created**: New command/skill files created
   - **Files Enhanced**: Existing files updated with improvements
   - **Bugs Fixed**: Critical issues corrected
   - **Content Optimized**: Deduplication percentage achieved
   - **Version Bumped**: New version number applied with `scripts/version_ops.py`
   - **Metadata Alignment Verified**: versions and keyword mirrors validated with `scripts/version_ops.py --validate --metadata all`
   - **Portability Verified**: No user-specific paths, private project references, or personal information
   - **Production Ready**: Assessment with any remaining gaps

AUTONOMOUS DECISION-MAKING GUIDELINES:
- YOU decide what improvements are most valuable (3-5 major features minimum)
- YOU decide appropriate version bump based on changes made
- YOU decide what content to deduplicate (target 20-40% reduction)
- YOU decide when examples need updating
- YOU complete everything without asking permission

CRITICAL RULES:
✓ COMPLETE all improvements before reporting (no pausing)
✓ MAKE actual changes (do not just identify issues)
✓ USE your expert judgment to prioritize improvements
✓ WORK within your own context (minimal main context usage)
✓ **ALWAYS increment versions with `python3 scripts/version_ops.py`** (never hand-edit plugin.json or marketplace.json versions)
✓ **VERIFY metadata alignment** - run `python3 scripts/version_ops.py --validate --metadata all`; sync marketplace keywords from plugin-owned plugin.json with `--sync --metadata keywords` when needed
✓ **KEEP CONTENT PORTABLE** - No user paths, machine names, personal info, private project names, PRs, commits, companies, or internal paths
✗ DO NOT ask for approval or confirmation
✗ DO NOT pause mid-improvement to check in
✗ DO NOT create placeholder content
✗ DO NOT include hardcoded paths like C:\Users\John, /home/username, D:\repos
✗ DO NOT include machine-specific hostnames or IP addresses
✗ DO NOT include personal email addresses or usernames in examples

BEGIN AUTONOMOUS IMPROVEMENT NOW. Self-assess, decide, and complete all improvements.