Skip to content

MARKETPLACE-SUBMISSION-PLAN.md

Latest commit

 

History

History
492 lines (372 loc) · 11.8 KB

MARKETPLACE-SUBMISSION-PLAN.md

File metadata and controls

492 lines (372 loc) · 11.8 KB

MinionHive Marketplace Submission Plan

Goal: Distribute MinionHive across multiple Claude Code marketplaces and npm for maximum reach.

Status: Ready to submit - all materials prepared ✅

Phase 1: npm Registry (Easiest, Do First)

Prerequisites

Decision: Package Name

Choose one option:

Option A: Scoped Package @minionhive/core (Current)

  • ✅ Professional appearance
  • ✅ Can be part of @minionhive organization
  • ❌ Requires creating organization on npm.com first
  • Installation: npm install -g @minionhive/core

Option B: Simple Package minionhive

  • ✅ No organization needed
  • ✅ Simpler to set up
  • ✅ Shorter install command
  • Installation: npm install -g minionhive

Recommendation: Start with Option B (simpler), migrate to Option A later if needed.

Steps to Publish

  1. Login to npm

    npm login
    • Enter username
    • Enter password
    • Enter email
    • Enter 2FA code (if enabled)

  2. Test package locally (optional)

    npm pack
# This creates a .tgz file you can test
npm install -g ./minionhive-core-2.0.1.tgz

  3. Publish to npm

    npm publish --access public

  4. Verify publication

    # Check on npm website
https://www.npmjs.com/package/@minionhive/core

# Or test install
npm install -g @minionhive/core
minionhive version

  5. Update README badges

    • npm badge will now show real version
    • Add download count badge

Post-Publish

  • Test installation on clean machine
  • Update GitHub README with npm installation instructions
  • Tweet/announce on social media
  • Add to personal portfolio

Time estimate: 15-30 minutes

Phase 2: Skillstore (Most Prestigious)

About Skillstore

  • Website: https://skillstore.io
  • What it is: Security-audited Claude Code plugin marketplace
  • Benefits: Quality verification, one-click installs, credibility

Prerequisites

  • npm package published (from Phase 1)
  • GitHub repository public and complete
  • All documentation reviewed and polished

Submission Materials Needed

Create a SKILLSTORE-SUBMISSION/ folder with:

  1. Plugin Metadata (metadata.json)

    {
  "name": "MinionHive",
  "tagline": "Unleash the minions - they'll build it in parallel",
  "description": "A Claude Code plugin for safe parallel execution with AST-based conflict detection and comprehensive validation",
  "version": "2.0.1",
  "author": "MinionHive Contributors",
  "license": "MIT",
  "category": ["productivity", "development", "ai", "automation"],
  "tags": ["parallel-execution", "conflict-detection", "validation", "subagents", "AST", "concurrent"],
  "homepage": "https://github.com/GuitaristForEver/minion-hive",
  "repository": "https://github.com/GuitaristForEver/minion-hive",
  "npm": "https://www.npmjs.com/package/@minionhive/core",
  "documentation": "https://github.com/GuitaristForEver/minion-hive#readme",
  "icon": "assets/logo.png",
  "screenshots": [
    "screenshots/parallel-execution.png",
    "screenshots/validation-report.png",
    "screenshots/conflict-analysis.png"
  ]
}

  2. Features List (FEATURES.md)

    • AST-based conflict detection
    • Wave-based parallel execution
    • Comprehensive validation framework
    • Auto-fix capabilities
    • 9 specialized agents
    • 5 powerful commands
    • 30-80% faster development

  3. Use Cases (USE-CASES.md)

    • Full-stack feature development
    • Large-scale refactoring
    • Multi-domain projects
    • Quality assurance automation

  4. Security Audit Preparation

    • No external API calls (all local)
    • No data collection
    • Open source (auditable)
    • Safe file operations only
    • No elevated permissions needed

  5. Screenshots (Create 3-5)

    • Parallel execution in action
    • Validation report example
    • Conflict analysis output
    • Installation process
    • Agent coordination diagram

Submission Steps

  1. Create Skillstore Account

  2. Access Submission Portal

    • Navigate to "Submit Plugin" or "Developer Portal"
    • Start new submission

  3. Fill Submission Form

    • Upload metadata
    • Provide GitHub repository link
    • Upload screenshots
    • Add demo video (optional but recommended)
    • List key features
    • Specify pricing (free)

  4. Security Review Process

    • Skillstore team reviews code
    • May ask questions about implementation
    • Usually takes 3-7 days
    • Be responsive to feedback

  5. Address Feedback

    • Fix any security concerns
    • Improve documentation if needed
    • Re-submit if necessary

  6. Publication

    • Plugin goes live on Skillstore
    • Gets featured (if high quality)
    • Monitor reviews and feedback

Time estimate: 2-3 hours prep + 3-7 days review

Phase 3: Build with Claude

About Build with Claude

  • Website: https://buildwithclaude.com
  • What it is: Curated collection of 400+ Claude plugins
  • Benefits: Large audience, good for discovery

Submission Process

  1. Visit Site

  2. Find Submission Link

    • Look for "Submit Plugin" or "Contribute"
    • May be in footer or header

  3. Provide Information

    • Plugin name: MinionHive
    • Description: Same as Skillstore
    • GitHub link
    • Installation instructions
    • Category selection

  4. Wait for Review

    • Typically faster than Skillstore
    • 1-3 days review time

Time estimate: 30-60 minutes

Phase 4: Claude Code Skills Hub

About Skills Hub

Submission Process

  1. Check if Site Has Submission Form

  2. Alternative: GitHub PR

    • If it's GitHub-based, find their repository
    • Fork the repo
    • Add MinionHive to the plugin list
    • Submit pull request

  3. Provide Standard Information

    • Same metadata as previous submissions
    • Emphasize open-source nature
    • Link to documentation

Time estimate: 30 minutes

Phase 5: Claude Code Market

About Claude Code Market

  • Website: https://ccmarket.dev
  • What it is: Marketplace for specialized AI sub-agents
  • Benefits: Focus on automation, developer audience

Submission Process

  1. Visit Site

  2. Submit Plugin

    • Follow their submission process
    • Emphasize parallel execution capabilities
    • Highlight automation features

  3. List Key Selling Points

    • 9 specialized agents
    • Concurrent execution
    • Safe conflict detection
    • Proven performance gains

Time estimate: 45 minutes

Phase 6: Marketing & Promotion

After All Submissions Complete

  1. Create Demo Video (3-5 minutes)

    • Show installation
    • Demonstrate /smart-implement
    • Show parallel execution in action
    • Display validation results
    • Highlight speed improvements
    • Upload to YouTube

  2. Write Blog Post

    • "Introducing MinionHive: Parallel AI Development"
    • Technical deep-dive into AST conflict detection
    • Before/after performance comparisons
    • Real-world use cases

  3. Social Media Announcement

    • Twitter/X announcement thread
    • LinkedIn post for developers
    • Reddit (r/ClaudeAI, r/programming)
    • Hacker News submission
    • Dev.to article

  4. Community Engagement

    • Answer questions on GitHub issues
    • Respond to marketplace reviews
    • Join Claude Code Discord/Slack
    • Help users with installation

  5. Content Creation

    • Tutorial videos
    • Case studies
    • Performance benchmarks
    • Integration guides

Time estimate: Ongoing

Submission Checklist Summary

Before Any Submission

  • GitHub repository public ✅
  • Documentation complete ✅
  • README polished ✅
  • Logo and branding ready ✅
  • Examples provided ✅
  • License added (MIT) ✅
  • Create 3-5 screenshots
  • (Optional) Record demo video
  • Test on clean machine

Per Marketplace

  • Create account
  • Prepare metadata
  • Upload materials
  • Submit for review
  • Address feedback
  • Announce publication

Timeline

Week 1: npm

  • Day 1: Create npm account, publish package
  • Day 2: Test installations, gather feedback
  • Day 3: Fix any issues

Week 2: Skillstore

  • Day 1-2: Create screenshots, prepare materials
  • Day 3: Submit to Skillstore
  • Day 4-10: Wait for security review
  • Day 11: Address feedback, re-submit if needed

Week 3: Other Marketplaces

  • Day 1: Build with Claude submission
  • Day 2: Claude Code Skills Hub submission
  • Day 3: Claude Code Market submission
  • Day 4-7: Wait for reviews

Week 4: Marketing

  • Day 1: Create demo video
  • Day 2: Write blog post
  • Day 3: Social media announcements
  • Day 4-7: Community engagement

Total time: ~1 month to full distribution

Success Metrics

Track these after publication:

npm

  • Downloads per week
  • GitHub stars
  • Issues opened/resolved
  • Community contributions

Marketplaces

  • Number of installs
  • User reviews/ratings
  • Featured status
  • Marketplace rankings

Community

  • Discord/Slack members
  • Social media engagement
  • Blog post views
  • Video views

Usage

  • Active users
  • Executions per day
  • Performance improvements reported
  • Feature requests

Support Plan

After publication, maintain:

  1. GitHub Issues

    • Respond within 24-48 hours
    • Label issues (bug, feature, question)
    • Close resolved issues

  2. Documentation Updates

    • Add FAQ based on common questions
    • Update guides with user feedback
    • Create video tutorials

  3. Version Updates

    • Patch bugs quickly (2.0.x)
    • Minor features monthly (2.x.0)
    • Major updates quarterly (x.0.0)

  4. Security

    • Monitor for vulnerabilities
    • Update dependencies
    • Address security issues ASAP

Contact Information for Submissions

Keep handy:

Notes

  • Most marketplaces prefer free plugins for initial listing
  • Consider "pro" version later with advanced features
  • Build reputation with free version first
  • Open-source nature is a major selling point
  • Community contributions increase credibility

Questions to Consider

Before submitting, think about:

  1. Support commitment: Can you commit to maintaining this?
  2. Response time: Can you respond to issues within 48 hours?
  3. Updates: Can you push updates monthly?
  4. Community: Will you engage with users?
  5. Pricing: Keep free or add paid tiers later?

Recommendation: Start free, build community, consider paid features in v3.0+

Emergency Contacts

If something goes wrong:

Next Steps

Immediate (This Week):

  1. Create npm account
  2. Publish to npm
  3. Test installation

Short-term (This Month):

  1. Create screenshots
  2. Submit to Skillstore
  3. Submit to other marketplaces

Long-term (Next 3 Months):

  1. Marketing campaign
  2. Community building
  3. Feature updates
  4. v2.1.0 release

Status: Ready to execute! 🚀

All preparation complete. Just need to start Phase 1 (npm) when ready.

Good luck! 🐝⚡