Research Report: Converting claudekit-skills to Claude Code Marketplace

Research Report: Converting claudekit-skills to Claude Code Marketplace

Research Date: December 29, 2025, 11:49 AM Issue: #6 Status: Comprehensive analysis complete

Executive Summary

Converting claudekit-skills repository into a Claude Code Marketplace will enable seamless installation and automatic updates for 30+ skills, eliminating manual file copying. The conversion requires creating a .claude-plugin/marketplace.json manifest, restructuring plugins to include individual plugin.json manifests, and hosting via GitHub. Users will install via /plugin marketplace add mrgoonie/claudekit-skills instead of manual cloning. Key benefits: version management, automatic updates, centralized discovery, and improved developer experience.

Recommendation: Implement marketplace structure while maintaining backward compatibility with existing manual installation. Create plugins for skill categories (ai-ml, web-dev, devops, etc.) to reduce context bloat and improve installation granularity.

Research Methodology

• Sources consulted: 4 (Official Claude Code docs, GitHub repository analysis, WebFetch, Gemini AI research)
• Date range: December 2025
• Key search terms: "Claude Code marketplace", "plugin manifest", "marketplace.json", "plugin distribution", "GitHub marketplace hosting"

Key Findings

1. Claude Code Marketplace Overview

Definition: Plugin marketplace = catalog distributing Claude Code extensions with centralized discovery, version tracking, and automatic updates.

Architecture:

claudekit-skills/                    # GitHub repo root
├── .claude-plugin/
│   └── marketplace.json             # Marketplace manifest (REQUIRED)
└── plugins/                         # All plugins
    ├── ai-ml-tools/                 # Category-based plugin
    │   ├── .claude-plugin/
    │   │   └── plugin.json          # Plugin manifest
    │   └── skills/
    │       ├── ai-multimodal/
    │       ├── google-adk-python/
    │       └── ...
    ├── web-dev-tools/
    │   ├── .claude-plugin/
    │   │   └── plugin.json
    │   └── skills/
    │       ├── frontend-development/
    │       ├── ui-styling/
    │       └── ...
    └── devops-tools/
        ├── .claude-plugin/
        │   └── plugin.json
        └── skills/
            ├── devops/
            ├── databases/
            └── ...

2. Current State Analysis

Existing Structure:

• 30+ skills organized in .claude/skills/
• 1 agent in .claude/agents/
• 4 commands in .claude/commands/
• Manual installation via git clone + file copying
• Dependencies: Python packages (ai-multimodal), system tools (FFmpeg, ImageMagick), Node.js tools

Current Installation Process (Manual):

1. Clone repository
2. Copy .claude/ directory to project
3. Install Python dependencies (pip install -r requirements.txt)
4. Install system tools (FFmpeg, ImageMagick, etc.)
5. Configure environment variables
6. Manually update when changes occur

Pain Points:

• No version tracking
• Manual updates required
• No dependency resolution
• Unclear which skills are installed
• File conflicts when updating

3. Marketplace Structure Requirements

Marketplace Manifest (.claude-plugin/marketplace.json)

Required Fields:

{
  "name": "claudekit-skills",
  "owner": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "plugins": []
}

Optional Metadata:

{
  "metadata": {
    "description": "Professional Agent Skills for Claude Code - 30+ skills covering AI, web dev, DevOps, databases, and more",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  }
}

Reserved Names (Blocked):

• claude-code-marketplace
• claude-code-plugins
• claude-plugins-official
• anthropic-marketplace
• anthropic-plugins
• agent-skills
• Names impersonating official marketplaces

Plugin Entry Schema

Minimal:

{
  "name": "ai-ml-tools",
  "source": "./plugins/ai-ml-tools",
  "description": "AI and ML skills: ai-multimodal, google-adk-python",
  "version": "1.0.0"
}

Complete:

{
  "name": "web-dev-tools",
  "source": "./plugins/web-dev-tools",
  "description": "Web development skills: frontend-development, ui-styling, web-frameworks, aesthetic",
  "version": "1.0.0",
  "author": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "homepage": "https://claudekit.cc",
  "repository": "https://github.com/mrgoonie/claudekit-skills",
  "license": "MIT",
  "keywords": ["web", "frontend", "react", "nextjs", "tailwind"],
  "category": "productivity",
  "tags": ["development", "ui-ux"],
  "commands": ["./commands/"],
  "agents": ["./agents/"],
  "mcpServers": "./mcp/config.json",
  "strict": false
}

Component Configuration:

• commands: Array of paths to command directories
• agents: Array of paths to agent markdown files
• hooks: Path to hooks configuration JSON
• mcpServers: Path to MCP servers configuration
• lspServers: Path to LSP servers configuration
• strict: Validation mode (default: false)

Plugin Manifest (plugin.json)

Each plugin needs .claude-plugin/plugin.json:

{
  "name": "ai-ml-tools",
  "description": "AI and ML capabilities with Gemini API integration",
  "version": "1.0.0",
  "author": {
    "name": "ClaudeKit Team"
  },
  "skills": [
    "ai-multimodal",
    "google-adk-python"
  ],
  "dependencies": {
    "python": ">=3.8",
    "packages": [
      "google-genai>=0.1.0",
      "pypdf>=4.0.0",
      "python-docx>=1.0.0"
    ]
  }
}

4. Migration Strategy

Phase 1: Categorize Skills (Recommended Grouping)

Proposed Plugin Categories:

1. ai-ml-tools (2 skills)

   • ai-multimodal
   • google-adk-python

2. web-dev-tools (4 skills)

   • frontend-development
   • frontend-design
   • ui-styling
   • web-frameworks

3. devops-tools (3 skills)

   • devops
   • databases
   • chrome-devtools

4. backend-tools (2 skills)

   • backend-development
   • better-auth

5. document-processing (4 skills)

   • document-skills/docx
   • document-skills/pdf
   • document-skills/pptx
   • document-skills/xlsx

6. debugging-tools (4 skills)

   • debugging/defense-in-depth
   • debugging/root-cause-tracing
   • debugging/systematic-debugging
   • debugging/verification-before-completion

7. problem-solving-tools (6 skills)

   • problem-solving/collision-zone-thinking
   • problem-solving/inversion-exercise
   • problem-solving/meta-pattern-recognition
   • problem-solving/scale-game
   • problem-solving/simplification-cascades
   • problem-solving/when-stuck

8. platform-tools (2 skills)

   • shopify
   • mcp-management

9. meta-tools (3 skills)

   • skill-creator
   • code-review
   • mcp-builder

10. media-tools (2 skills)

    • media-processing
    • aesthetic

11. research-tools (2 skills)

    • docs-seeker
    • repomix

12. specialized-tools (2 skills)

    • sequential-thinking
    • mermaidjs-v11

Total: 12 plugins covering 30+ skills + agents + commands

Alternative (All-in-One): Single plugin with all skills (simpler structure, larger download, less granular control)

Phase 2: Directory Restructuring

Option A: Category-Based (Recommended)

claudekit-skills/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   ├── ai-ml-tools/
│   │   ├── .claude-plugin/
│   │   │   └── plugin.json
│   │   └── skills/
│   │       ├── ai-multimodal/
│   │       └── google-adk-python/
│   ├── web-dev-tools/
│   │   ├── .claude-plugin/
│   │   │   └── plugin.json
│   │   └── skills/
│   │       ├── frontend-development/
│   │       ├── ui-styling/
│   │       └── ...
│   └── ...
└── .claude/  # Keep for backward compatibility
    ├── skills/
    ├── agents/
    └── commands/

Option B: All-in-One Plugin

claudekit-skills/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   └── claudekit-all/
│       ├── .claude-plugin/
│       │   └── plugin.json
│       ├── skills/      # Symlink to .claude/skills
│       ├── agents/      # Symlink to .claude/agents
│       └── commands/    # Symlink to .claude/commands
└── .claude/  # Original structure (unchanged)

Phase 3: Manifest Creation

Marketplace Manifest Example:

{
  "name": "claudekit-skills",
  "owner": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "metadata": {
    "description": "Professional Agent Skills for Claude Code - AI, web dev, DevOps, databases, and more",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "ai-ml-tools",
      "source": "./plugins/ai-ml-tools",
      "description": "AI and ML capabilities: ai-multimodal (Gemini API), google-adk-python",
      "version": "1.0.0",
      "keywords": ["ai", "ml", "gemini", "multimodal"],
      "category": "productivity"
    },
    {
      "name": "web-dev-tools",
      "source": "./plugins/web-dev-tools",
      "description": "Web development: frontend-development, ui-styling, web-frameworks, aesthetic",
      "version": "1.0.0",
      "keywords": ["web", "frontend", "react", "nextjs"],
      "category": "productivity"
    },
    {
      "name": "devops-tools",
      "source": "./plugins/devops-tools",
      "description": "DevOps and infrastructure: devops, databases, chrome-devtools",
      "version": "1.0.0",
      "keywords": ["devops", "databases", "automation"],
      "category": "productivity"
    }
  ]
}

5. Distribution & Publishing

GitHub Hosting (Recommended)

Setup:

1. Commit .claude-plugin/marketplace.json to repository
2. Push to GitHub: mrgoonie/claudekit-skills
3. Users add marketplace: /plugin marketplace add mrgoonie/claudekit-skills
4. Users install plugins: /plugin install ai-ml-tools@claudekit-skills

Installation Commands:

# Add marketplace (one-time)
/plugin marketplace add mrgoonie/claudekit-skills

# Install specific plugin
/plugin install ai-ml-tools@claudekit-skills
/plugin install web-dev-tools@claudekit-skills

# Or install all (if using all-in-one plugin)
/plugin install claudekit-all@claudekit-skills

Auto-Enable in Projects:

Add to .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "claudekit-skills": {
      "source": {
        "source": "github",
        "repo": "mrgoonie/claudekit-skills"
      }
    }
  },
  "enabledPlugins": {
    "ai-ml-tools@claudekit-skills": true,
    "web-dev-tools@claudekit-skills": true
  }
}

Version Management

Git Tags for Releases:

git tag -a v1.0.0 -m "Initial marketplace release"
git push origin v1.0.0

Pin to Specific Version:

{
  "source": {
    "source": "github",
    "repo": "mrgoonie/claudekit-skills",
    "ref": "v1.0.0"
  }
}

Update Workflow:

1. Users receive automatic update notifications
2. Run /plugin update ai-ml-tools@claudekit-skills
3. Or update all: /plugin update --all

6. Security Considerations

Plugin Caching:

• Plugins copied to cache during installation (not used in-place)
• Cannot reference files outside plugin directory (../shared-utils blocked)
• Use ${CLAUDE_PLUGIN_ROOT} variable for relative paths in hooks/MCP configs

Enterprise Controls:

Restrict to approved marketplaces in managed settings:

{
  "strictKnownMarketplaces": [
    {
      "source": "github",
      "repo": "mrgoonie/claudekit-skills",
      "ref": "v1.0.0"
    }
  ]
}

Validation:

# Validate manifest before publishing
claude plugin validate .
# Or within Claude Code
/plugin validate .

7. Best Practices

Naming Conventions:

• Use kebab-case for plugin names
• Descriptive names: ai-ml-tools not tools
• Avoid reserved names
• Keep names concise but clear

Versioning:

• Follow SemVec: MAJOR.MINOR.PATCH
• Breaking changes = MAJOR bump
• New features = MINOR bump
• Bug fixes = PATCH bump

Documentation:

• Include README.md in each plugin
• Document dependencies clearly
• Provide installation examples
• List skill capabilities

Testing:

• Test local installation before publishing
• Validate JSON syntax
• Test on multiple platforms
• Verify dependency resolution

Comparative Analysis: Manual vs Marketplace

Implementation Recommendations

Quick Start Guide

Step 1: Create Marketplace Structure

mkdir -p .claude-plugin
mkdir -p plugins

Step 2: Create Marketplace Manifest

cat > .claude-plugin/marketplace.json << 'EOF'
{
  "name": "claudekit-skills",
  "owner": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "metadata": {
    "description": "Professional Agent Skills for Claude Code",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  },
  "plugins": []
}
EOF

Step 3A: Option A - Category-Based Plugins (Recommended)

# Create category plugin directories
for category in ai-ml-tools web-dev-tools devops-tools backend-tools \
                document-processing debugging-tools problem-solving-tools \
                platform-tools meta-tools media-tools research-tools \
                specialized-tools; do
  mkdir -p plugins/$category/.claude-plugin
  mkdir -p plugins/$category/skills
done

# Copy skills to respective categories
# ai-ml-tools
cp -r .claude/skills/ai-multimodal plugins/ai-ml-tools/skills/
cp -r .claude/skills/google-adk-python plugins/ai-ml-tools/skills/

# web-dev-tools
cp -r .claude/skills/frontend-development plugins/web-dev-tools/skills/
cp -r .claude/skills/frontend-design plugins/web-dev-tools/skills/
cp -r .claude/skills/ui-styling plugins/web-dev-tools/skills/
cp -r .claude/skills/web-frameworks plugins/web-dev-tools/skills/

# Continue for other categories...

Step 3B: Option B - All-in-One Plugin (Simpler)

mkdir -p plugins/claudekit-all/.claude-plugin
cd plugins/claudekit-all
ln -s ../../.claude/skills skills
ln -s ../../.claude/agents agents
ln -s ../../.claude/commands commands

Step 4: Create Plugin Manifests

# Example: ai-ml-tools
cat > plugins/ai-ml-tools/.claude-plugin/plugin.json << 'EOF'
{
  "name": "ai-ml-tools",
  "description": "AI and ML capabilities with Gemini API integration",
  "version": "1.0.0",
  "author": {
    "name": "ClaudeKit Team"
  }
}
EOF

Step 5: Update Marketplace Manifest with Plugins

{
  "plugins": [
    {
      "name": "ai-ml-tools",
      "source": "./plugins/ai-ml-tools",
      "description": "AI and ML capabilities: ai-multimodal, google-adk-python",
      "version": "1.0.0"
    }
  ]
}

Step 6: Validate

/plugin validate .

Step 7: Commit and Push

git add .claude-plugin/ plugins/
git commit -m "feat: convert to Claude Code marketplace structure"
git push origin main
git tag -a v1.0.0 -m "Initial marketplace release"
git push origin v1.0.0

Step 8: Test Installation

/plugin marketplace add mrgoonie/claudekit-skills
/plugin install ai-ml-tools@claudekit-skills

Recommended Implementation Strategy

Phase 1: Hybrid Approach (Immediate)

1. Create marketplace structure alongside existing .claude/ directory
2. Use symlinks or copy skills to plugins
3. Publish v1.0.0 with marketplace support
4. Keep .claude/ for backward compatibility
5. Document both installation methods in README

Phase 2: Migration Notice (1-2 months)

1. Add deprecation notice to README for manual installation
2. Update documentation to recommend marketplace installation
3. Monitor adoption metrics
4. Provide migration guide for existing users

Phase 3: Full Marketplace (3-6 months)

1. Remove .claude/ directory (breaking change = v2.0.0)
2. Marketplace becomes primary distribution method
3. Maintain legacy branch for manual installation

Backward Compatibility Strategy

Dual-Path Support:

claudekit-skills/
├── .claude-plugin/          # NEW: Marketplace structure
│   └── marketplace.json
├── plugins/                 # NEW: Plugins
│   ├── ai-ml-tools/
│   └── ...
└── .claude/                 # KEEP: Backward compatibility
    ├── skills/
    ├── agents/
    └── commands/

README Update:

## Installation

### Option 1: Marketplace (Recommended)
\`\`\`bash
/plugin marketplace add mrgoonie/claudekit-skills
/plugin install ai-ml-tools@claudekit-skills
\`\`\`

### Option 2: Manual (Legacy)
\`\`\`bash
git clone https://github.com/mrgoonie/claudekit-skills
cp -r claudekit-skills/.claude/* /path/to/your/project/.claude/
\`\`\`
**Note:** Manual installation is deprecated. Please migrate to marketplace.

Common Pitfalls & Solutions

Issue 1: File Path References

• Problem: Skills reference ../shared-utils outside plugin
• Solution: Restructure to include shared code in each plugin or use ${CLAUDE_PLUGIN_ROOT} variable

Issue 2: Duplicate plugin names

• Problem: Two plugins with same name field
• Solution: Ensure unique names in marketplace.json

Issue 3: Invalid JSON syntax

• Problem: Missing commas, unquoted strings
• Solution: Validate with /plugin validate . before committing

Issue 4: Missing dependencies

• Problem: Python packages not installed
• Solution: Document in plugin README, consider dependency installation script

Issue 5: Large plugin downloads

• Problem: All-in-one plugin too large
• Solution: Use category-based plugins for granular installation

Code Examples

Complete Marketplace Manifest

{
  "name": "claudekit-skills",
  "owner": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "metadata": {
    "description": "Professional Agent Skills for Claude Code - 30+ skills covering AI, web dev, DevOps, databases, document processing, debugging, and more",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "ai-ml-tools",
      "source": "./plugins/ai-ml-tools",
      "description": "AI and ML capabilities: ai-multimodal (Gemini API with image/video/audio processing), google-adk-python (Agent Development Kit)",
      "version": "1.0.0",
      "author": {
        "name": "ClaudeKit Team",
        "email": "[email protected]"
      },
      "homepage": "https://claudekit.cc",
      "repository": "https://github.com/mrgoonie/claudekit-skills",
      "license": "MIT",
      "keywords": ["ai", "ml", "gemini", "multimodal", "adk"],
      "category": "productivity",
      "tags": ["ai", "machine-learning"]
    },
    {
      "name": "web-dev-tools",
      "source": "./plugins/web-dev-tools",
      "description": "Web development skills: frontend-development (React/TypeScript), frontend-design (production UI/UX), ui-styling (shadcn/Tailwind), web-frameworks (Next.js/Turborepo), aesthetic (design principles)",
      "version": "1.0.0",
      "keywords": ["web", "frontend", "react", "nextjs", "tailwind", "ui-ux"],
      "category": "productivity"
    },
    {
      "name": "devops-tools",
      "source": "./plugins/devops-tools",
      "description": "DevOps and infrastructure: devops (Cloudflare/Docker/GCP), databases (MongoDB/PostgreSQL), chrome-devtools (Puppeteer automation)",
      "version": "1.0.0",
      "keywords": ["devops", "databases", "automation", "cloudflare", "docker"],
      "category": "productivity"
    },
    {
      "name": "backend-tools",
      "source": "./plugins/backend-tools",
      "description": "Backend development: backend-development (Node.js/Python/Go), better-auth (TypeScript auth framework)",
      "version": "1.0.0",
      "keywords": ["backend", "nodejs", "python", "authentication"],
      "category": "productivity"
    },
    {
      "name": "document-processing",
      "source": "./plugins/document-processing",
      "description": "Document skills: docx (Word documents), pdf (PDF processing), pptx (PowerPoint), xlsx (Excel/financial modeling)",
      "version": "1.0.0",
      "keywords": ["documents", "pdf", "word", "excel", "powerpoint"],
      "category": "productivity"
    },
    {
      "name": "debugging-tools",
      "source": "./plugins/debugging-tools",
      "description": "Debugging frameworks: defense-in-depth, root-cause-tracing, systematic-debugging, verification-before-completion",
      "version": "1.0.0",
      "keywords": ["debugging", "testing", "quality-assurance"],
      "category": "productivity"
    },
    {
      "name": "problem-solving-tools",
      "source": "./plugins/problem-solving-tools",
      "description": "Problem-solving techniques: collision-zone-thinking, inversion-exercise, meta-pattern-recognition, scale-game, simplification-cascades, when-stuck",
      "version": "1.0.0",
      "keywords": ["problem-solving", "innovation", "thinking"],
      "category": "productivity"
    },
    {
      "name": "platform-tools",
      "source": "./plugins/platform-tools",
      "description": "Platform integrations: shopify (apps/extensions/themes), mcp-management (Model Context Protocol servers)",
      "version": "1.0.0",
      "keywords": ["shopify", "mcp", "integrations"],
      "category": "productivity"
    },
    {
      "name": "meta-tools",
      "source": "./plugins/meta-tools",
      "description": "Meta development: skill-creator (create new skills), code-review (review workflows), mcp-builder (build MCP servers)",
      "version": "1.0.0",
      "keywords": ["meta", "code-review", "mcp"],
      "category": "productivity"
    },
    {
      "name": "media-tools",
      "source": "./plugins/media-tools",
      "description": "Media processing: media-processing (FFmpeg/ImageMagick), aesthetic (design principles/visual hierarchy)",
      "version": "1.0.0",
      "keywords": ["media", "ffmpeg", "imagemagick", "design"],
      "category": "productivity"
    },
    {
      "name": "research-tools",
      "source": "./plugins/research-tools",
      "description": "Research capabilities: docs-seeker (llms.txt documentation discovery), repomix (repo packaging for AI)",
      "version": "1.0.0",
      "keywords": ["research", "documentation", "analysis"],
      "category": "productivity"
    },
    {
      "name": "specialized-tools",
      "source": "./plugins/specialized-tools",
      "description": "Specialized skills: sequential-thinking (step-by-step reasoning), mermaidjs-v11 (diagram generation)",
      "version": "1.0.0",
      "keywords": ["diagrams", "reasoning", "visualization"],
      "category": "productivity"
    }
  ]
}

Plugin Manifest Example (ai-ml-tools)

{
  "name": "ai-ml-tools",
  "description": "AI and ML capabilities with Google Gemini API integration for multimodal processing and agent development",
  "version": "1.0.0",
  "author": {
    "name": "ClaudeKit Team",
    "email": "[email protected]"
  },
  "homepage": "https://claudekit.cc",
  "repository": "https://github.com/mrgoonie/claudekit-skills",
  "license": "MIT",
  "keywords": ["ai", "ml", "gemini", "multimodal", "adk"],
  "skills": [
    {
      "name": "ai-multimodal",
      "description": "Process and generate multimedia content using Google Gemini API. Analyze audio, images, videos, documents. Generate images.",
      "dependencies": {
        "python": ">=3.8",
        "packages": [
          "google-genai>=0.1.0",
          "pypdf>=4.0.0",
          "python-docx>=1.0.0",
          "markdown>=3.5.0",
          "Pillow>=10.0.0",
          "python-dotenv>=1.0.0"
        ],
        "env": ["GEMINI_API_KEY"]
      }
    },
    {
      "name": "google-adk-python",
      "description": "Google's Agent Development Kit for building AI agents with tool integration and orchestration",
      "dependencies": {
        "python": ">=3.9",
        "packages": []
      }
    }
  ]
}

Installation Script for Users

#!/bin/bash
# install-claudekit.sh

echo "Installing ClaudeKit Skills Marketplace..."

# Add marketplace
echo "Adding marketplace..."
claude plugin marketplace add mrgoonie/claudekit-skills

# Prompt user for categories
echo "Select plugins to install:"
echo "1. AI & ML Tools"
echo "2. Web Development Tools"
echo "3. DevOps Tools"
echo "4. Backend Tools"
echo "5. Document Processing"
echo "6. Debugging Tools"
echo "7. Problem Solving Tools"
echo "8. Platform Tools"
echo "9. Meta Tools"
echo "10. Media Tools"
echo "11. Research Tools"
echo "12. Specialized Tools"
echo "13. Install All"

read -p "Enter numbers (space-separated): " choices

for choice in $choices; do
  case $choice in
    1) claude plugin install ai-ml-tools@claudekit-skills ;;
    2) claude plugin install web-dev-tools@claudekit-skills ;;
    3) claude plugin install devops-tools@claudekit-skills ;;
    4) claude plugin install backend-tools@claudekit-skills ;;
    5) claude plugin install document-processing@claudekit-skills ;;
    6) claude plugin install debugging-tools@claudekit-skills ;;
    7) claude plugin install problem-solving-tools@claudekit-skills ;;
    8) claude plugin install platform-tools@claudekit-skills ;;
    9) claude plugin install meta-tools@claudekit-skills ;;
    10) claude plugin install media-tools@claudekit-skills ;;
    11) claude plugin install research-tools@claudekit-skills ;;
    12) claude plugin install specialized-tools@claudekit-skills ;;
    13)
      for plugin in ai-ml-tools web-dev-tools devops-tools backend-tools \
                    document-processing debugging-tools problem-solving-tools \
                    platform-tools meta-tools media-tools research-tools \
                    specialized-tools; do
        claude plugin install $plugin@claudekit-skills
      done
      ;;
  esac
done

echo "Installation complete!"

Resources & References

Official Documentation

• Claude Code Plugin Marketplaces - Complete marketplace documentation
• Creating Plugins - Plugin development guide
• Discover and Install Plugins - User installation guide
• Plugin Settings Reference - Configuration options

Recommended Tutorials

• Setting up a GitHub-based marketplace
• Creating category-based plugin structure
• Migrating from manual to marketplace distribution
• Version management with Git tags
• Enterprise marketplace restrictions

Community Resources

• GitHub Issues: https://github.com/anthropics/claude-code/issues
• Claude Code Discord (if available)
• Stack Overflow tag: claude-code

Further Reading

• Semantic Versioning: https://semver.org/
• JSON Schema Validation
• Git Tagging Best Practices
• Plugin Architecture Patterns

Appendices

A. Glossary

• Marketplace: Catalog distributing Claude Code extensions with version tracking
• Plugin: Installable package containing skills, agents, commands, hooks, or MCP servers
• Manifest: JSON configuration file defining marketplace or plugin metadata
• Plugin Root: Base directory for plugin files, referenced via ${CLAUDE_PLUGIN_ROOT}
• Strict Mode: Enterprise setting restricting marketplace additions to approved sources
• Source: Location where plugin files are fetched from (local path, GitHub, Git URL)
• MCP: Model Context Protocol for integrating external tools and services
• Skill: Specialized workflow combining mission briefs, guardrails, and integration hints

B. Version Compatibility Matrix

C. Implementation Checklist

Pre-Implementation:

• Review current repository structure
• Identify skill categories
• Choose plugin organization strategy (category-based vs all-in-one)
• Plan backward compatibility approach
• Document dependencies for each plugin

Implementation:

• Create .claude-plugin/ directory
• Write marketplace.json manifest
• Create plugins/ directory structure
• Copy/reorganize skills into plugins
• Create plugin manifests (plugin.json)
• Add README.md to each plugin
• Document installation process

Testing:

• Validate JSON syntax (/plugin validate .)
• Test local marketplace installation
• Test plugin installation
• Verify skill activation
• Test dependency resolution
• Test on multiple platforms

Publishing:

• Commit marketplace structure
• Create Git tag (v1.0.0)
• Push to GitHub
• Test installation from GitHub
• Update repository README
• Announce marketplace availability

Post-Launch:

• Monitor installation metrics
• Gather user feedback
• Fix reported issues
• Plan version updates
• Maintain documentation

D. Migration Timeline

Week 1: Planning & Design

• Finalize plugin categorization
• Create manifest templates
• Design directory structure

Week 2: Implementation

• Create marketplace manifest
• Restructure plugins
• Write plugin manifests
• Update documentation

Week 3: Testing

• Local testing
• Beta testing with users
• Fix issues
• Validate across platforms

Week 4: Launch

• Publish v1.0.0
• Update README
• Announce to community
• Monitor adoption

Month 2-3: Iteration

• Gather feedback
• Fix bugs
• Add missing features
• Improve documentation

Month 4+: Full Migration

• Deprecate manual installation
• Release v2.0.0 (marketplace-only)
• Maintain legacy branch

Unresolved Questions

1. Dependency Installation: How should Python dependencies be auto-installed when users install plugins? Options:

   • Document in README (current approach)
   • Include installation script in plugin
   • Use package manager integration (future feature?)

2. Shared Code: How to handle shared utilities used across multiple plugins?

   • Duplicate code in each plugin (isolated, larger size)
   • Create separate common-utils plugin as dependency
   • Wait for plugin dependency resolution feature

3. Plugin Granularity: Should each skill be its own plugin or use category grouping?

   • 30+ individual plugins (maximum granularity, overhead)
   • 12 category plugins (recommended balance)
   • 1 all-in-one plugin (simplest, least flexible)

4. Breaking Changes: When to remove .claude/ directory for backward compatibility?

   • Keep indefinitely (no breaking change)
   • Remove in v2.0.0 after 3-6 months (recommended)
   • Immediate removal (clean but breaking)

5. Agent & Command Packaging: Should agents and commands be separate plugins or bundled with skills?

   • Bundled (current structure, simpler)
   • Separate (more modular, complex)
   • Hybrid (skills bundled, agents/commands separate)

6. Enterprise Marketplace: Should a separate enterprise marketplace be created with vetted/approved skills?

   • Public marketplace only
   • Enterprise fork with additional skills
   • Dual marketplace strategy

Research Completed: December 29, 2025 Next Steps: Review recommendations, choose implementation strategy (category-based vs all-in-one), create implementation plan, begin Phase 1 development