Dex Plugin - Ready to Publish Checklist
Status: 🟡 Almost Ready - See Action Items Below
What's Been Done ✅
Plugin Structure Created
-
.claude-plugin/plugin.json- Plugin manifest with all MCP servers configured -
.claude-plugin/PLUGIN_README.md- Comprehensive plugin documentation -
.claude-plugin/DISTRIBUTION_GUIDE.md- Complete distribution options guide -
.claude-plugin/INSTALLATION_QUICK_START.md- User-friendly quick start guide -
.gitignoreupdated - Protects personal vault data from being committed
Existing Assets (Already Good)
- 60+ Skills in
.claude/skills/ - 9 MCP Servers in
.claude/mcp/andcore/mcp/ - Session hooks in
.claude/hooks/ - Comprehensive documentation in
06-Resources/Dex_System/ - LICENSE file (MIT)
- CHANGELOG.md (detailed version history)
- README.md (comprehensive overview)
What You Need to Do 🔨
Critical (Before Publishing)
Test the Plugin Locally
cd /Users/dave/Claudesidian/dex-core # Validate the plugin manifest claude plugin validate . # Link it locally to test claude plugin add . --scope user # Check it's installed claude plugin list # Test in a clean directory cd /tmp mkdir test-dex-vault cd test-dex-vault # Open Claude Code and try: # - /setup (or ask to run onboarding) # - /daily-plan # - /dex-level-upFix the GitHub Repository URL
Update
.claude-plugin/plugin.json:"repository": "https://github.com/YOUR-USERNAME/dex"Replace
YOUR-USERNAMEwith your actual GitHub username.Create Python Requirements File
Create
dex-core/requirements.txt:anthropic-mcp>=0.1.0 pyyaml>=6.0 python-dateutil>=2.8.0Create Example Configuration Files
These should exist but verify:
System/user-profile.example.yamlSystem/pillars.example.yaml
If they don't exist, copy from your actual files and remove personal data.
Update Main README.md
Add a clear "Installation" section at the top:
## Installation ```bash # Install Dex as a Claude Code plugin claude plugin install https://github.com/YOUR-USERNAME/dex # Install Python dependencies pip install anthropic-mcp pyyaml python-dateutil # Run onboarding # Open Claude Code in your vault directory and type: /setupSee
.claude-plugin/INSTALLATION_QUICK_START.mdfor detailed guide.
Important (For Good UX)
Create a Demo Video (5-10 minutes)
- Show installation process
- Run through onboarding
- Demonstrate key skills (/daily-plan, /meeting-prep)
- Upload to YouTube
- Add link to README.md
Test Installation on Clean Machine
- Use a friend's computer or VM
- Follow your installation docs exactly
- Document any issues you encounter
- Fix documentation gaps
Create GitHub Repository
cd /Users/dave/Claudesidian/dex-core # Initialize if not already done git init git add . git commit -m "Initial plugin release" # Create repository on GitHub (via web interface) # Then push: git remote add origin https://github.com/YOUR-USERNAME/dex.git git branch -M main git push -u origin main # Create a release tag git tag -a v1.0.0 -m "First public release" git push origin v1.0.0Create GitHub Release
- Go to GitHub → Releases → "Create a new release"
- Tag: v1.0.0
- Title: "Dex 1.0 - Your AI Chief of Staff"
- Description: Copy from your main README intro
- Attach: Installation quick start guide
- Mark as "Latest release"
Optional (But Valuable)
Create Your Own Marketplace
# In a separate directory mkdir dex-marketplace cd dex-marketplace mkdir -p .claude-plugin plugins # Create marketplace.json cat > .claude-plugin/marketplace.json << 'EOF' { "name": "dex-marketplace", "description": "Personal knowledge management and AI Chief of Staff tools", "owner": { "name": "Dave Killeen", "email": "dave@davekilleen.com" }, "plugins": [ { "name": "dex", "description": "Your AI Chief of Staff. Complete personal operating system.", "source": { "source": "url", "url": "https://github.com/YOUR-USERNAME/dex.git" }, "category": "productivity", "homepage": "https://github.com/YOUR-USERNAME/dex" } ] } EOF # Push to GitHub git init git add . git commit -m "Dex marketplace" git remote add origin https://github.com/YOUR-USERNAME/dex-marketplace.git git push -u origin mainUsers can then:
claude plugin marketplace add https://github.com/YOUR-USERNAME/dex-marketplace claude plugin install dex@dex-marketplaceSubmit to Official Marketplace
- Fork: https://github.com/anthropics/claude-plugins-public
- Add your plugin entry to
marketplace.json - Submit PR
- Wait for Anthropic review
Distribution Strategy (Recommended)
Phase 1: Soft Launch (Week 1)
- Plugin structure created
- Test locally (yourself)
- Test with 2-3 beta users
- Fix any installation issues
- Create installation video
Phase 2: GitHub Release (Week 2)
- Push to GitHub
- Create v1.0.0 release
- Update README with installation instructions
- Share on LinkedIn (personal network)
- Share on X/Twitter
- Post in Vibe PM community
Phase 3: Marketplace (Week 3-4)
- Create dex-marketplace repository
- Test marketplace installation
- Write blog post about plugin distribution
- Share marketplace link widely
Phase 4: Official Submission (Month 2)
- Gather user feedback
- Fix any reported issues
- Submit to claude-plugins-official
- Wait for approval
Testing Checklist
Before publishing, verify:
Local Installation
-
claude plugin validate .passes - Plugin installs locally without errors
- Skills appear in skill list
- MCP servers start successfully
Clean Installation
- Fresh directory installation works
- Onboarding completes successfully
- Vault structure is created correctly
- All skills work after onboarding
Core Workflows
-
/daily-planruns successfully -
/daily-reviewruns successfully -
/week-planruns successfully - Task creation works
- Person page creation works
- Project tracking works
MCP Servers
- Work MCP responds to queries
- Calendar MCP integrates correctly
- Tasks MCP creates and updates tasks
- Onboarding MCP completes setup
Documentation
- README is clear and accurate
- Installation guide is complete
- Troubleshooting section addresses common issues
- Links in docs work
Known Issues to Address
(Document any issues you find during testing here)
- None yet - test first!
Support Plan
Before launching, prepare:
GitHub Issues Template
- Bug report template
- Feature request template
- Question/support template
FAQ Document
- Common installation issues
- Python version problems
- MCP server troubleshooting
- Skill not appearing
Response Plan
- How quickly will you respond to issues?
- Where should users ask questions? (GitHub Discussions?)
- Community Discord/Slack?
Marketing Plan
Once published, promote via:
Week 1: Announcement
- LinkedIn post with demo video
- X/Twitter thread
- Update Vibe PM podcast show notes
- Email to newsletter subscribers
Week 2: Content
- Blog post: "Dex is now a Claude Code plugin"
- Blog post: "How to build a Claude Code plugin"
- YouTube: Extended demo/walkthrough
Week 3: Community
- Post in Claude Code communities
- Share in Product Management communities
- Post in PKM/Productivity communities
Week 4: Podcast Episode
- Record "Building Dex as a Plugin" episode
- Discuss lessons learned
- Demo the installation process
Revenue Options (Future)
If you want to monetize later:
Free Core + Premium Features
- Current Dex: Free
- Premium: Advanced integrations, team features
Dex Pro Marketplace
- Separate premium plugins
- Salesforce/HubSpot integrations
- Advanced analytics
Consulting Services
- Free: Self-service
- Paid: Setup assistance, custom integrations
Enterprise Edition
- Team deployment
- Custom configurations
- Priority support
Next Immediate Steps
This week:
- Run
claude plugin validate .and fix any errors - Test local installation thoroughly
- Create requirements.txt
- Update repository URL in plugin.json
- Create example config files
Next week:
- Create GitHub repository
- Test GitHub-based installation
- Record demo video
- Update README with installation section
- Soft launch to 3 beta testers
Week 3:
- Incorporate beta feedback
- Create GitHub release v1.0.0
- Announce on LinkedIn/X
- Share with Vibe PM community
You're 90% there! The hard work (building Dex) is done. Now it's just packaging and distribution.
Focus on getting a few beta users first, then expand distribution as you get feedback.
Questions? Check .claude-plugin/DISTRIBUTION_GUIDE.md for detailed strategies.