Add comprehensive release planning documentation: - V3_RELEASE_MASTER_PLAN.md - Complete 4-week campaign strategy - V3_RELEASE_SUMMARY.md - Quick reference summary - WEBSITE_HANDOFF_V3.md - Website update instructions for other Kimi - RELEASE_PLAN.md, RELEASE_CONTENT_CHECKLIST.md, RELEASE_EXECUTIVE_SUMMARY.md - QA_FIXES_SUMMARY.md - QA fixes documentation
8.5 KiB
📝 Release Content Checklist
Quick reference for what to create and where to post.
📱 Content to Create (Priority Order)
🔥 MUST CREATE (This Week)
1. Main Release Blog Post
File: blog/v2.9.0-release.md
Platforms: Dev.to → Medium → GitHub Discussions
Length: 800-1200 words
Time: 3-4 hours
Outline:
Title: Skill Seekers v2.9.0: The Universal Documentation Preprocessor
1. Hook (2 sentences on the problem)
2. TL;DR with key stats (16 formats, 1,852 tests, 18 MCP tools)
3. The Problem (everyone rebuilds scrapers)
4. The Solution (one command → any format)
5. Show 3 examples:
- RAG: LangChain/Chroma
- AI Coding: Cursor
- Claude skills
6. What's new in v2.9.0 (bullet list)
7. Installation + Quick Start
8. Links to docs/examples
9. Call to action (star, try, share)
Key Stats to Include:
- 16 platform adaptors
- 1,852 tests passing
- 18 MCP tools
- 58,512 lines of code
- 24+ preset configs
- Available on PyPI:
pip install skill-seekers
2. Twitter/X Thread
File: social/twitter-thread.txt
Platform: Twitter/X
Length: 7-10 tweets
Time: 1 hour
Structure:
Tweet 1: Announcement + hook (problem)
Tweet 2: The solution (one tool, 16 formats)
Tweet 3: RAG use case (LangChain example)
Tweet 4: AI coding use case (Cursor example)
Tweet 5: MCP tools showcase
Tweet 6: Test coverage (1,852 tests)
Tweet 7: Installation command
Tweet 8: GitHub link + CTA
3. Reddit Posts
File: social/reddit-posts.md
Platforms: r/LangChain, r/LLMDevs, r/cursor
Length: 300-500 words each
Time: 1 hour
r/LangChain Version:
- Focus: RAG pipeline automation
- Title: "I built a tool that scrapes docs and outputs LangChain Documents"
- Show code example
- Mention: metadata preservation, chunking
r/cursor Version:
- Focus: Framework knowledge
- Title: "Give Cursor complete React/Vue/etc knowledge in 2 minutes"
- Show .cursorrules workflow
- Before/after comparison
r/LLMDevs Version:
- Focus: Universal preprocessing
- Title: "Universal documentation preprocessor - 16 output formats"
- Broader appeal
- Link to all integrations
4. LinkedIn Post
File: social/linkedin-post.md
Platform: LinkedIn
Length: 200-300 words
Time: 30 minutes
Tone: Professional, infrastructure-focused Angle: Developer productivity, automation Hashtags: #AI #RAG #LangChain #DeveloperTools #OpenSource
📝 SHOULD CREATE (Week 1-2)
5. RAG Tutorial Post
File: blog/rag-tutorial.md
Platform: Dev.to
Length: 1000-1500 words
Time: 3-4 hours
Content:
- Step-by-step: React docs → LangChain → Chroma
- Complete working code
- Screenshots of output
- Before/after comparison
6. AI Coding Assistant Guide
File: blog/ai-coding-guide.md
Platform: Dev.to
Length: 800-1000 words
Time: 2-3 hours
Content:
- Cursor integration walkthrough
- Show actual code completion improvements
- Also mention Windsurf, Cline
7. Comparison Post
File: blog/comparison.md
Platform: Dev.to
Length: 600-800 words
Time: 2 hours
Content:
| Aspect | Manual | Skill Seekers |
|---|---|---|
| Time | 2 hours | 2 minutes |
| Code | 50+ lines | 1 command |
| Quality | Raw HTML | Structured |
| Testing | None | 1,852 tests |
🎥 NICE TO HAVE (Week 2-3)
8. Quick Demo Video
Length: 2-3 minutes Platform: YouTube, Twitter, LinkedIn Content:
- Screen recording
- Show: scrape → package → use
- Fast-paced, no fluff
9. GitHub Action Tutorial
File: blog/github-action.md
Platform: Dev.to
Content: Auto-update skills on doc changes
📧 Email Outreach Targets
Week 1 Emails (Send Immediately)
-
LangChain Team
- Contact: contact@langchain.dev or Harrison Chase
- Subject: "Skill Seekers - LangChain Integration + Data Loader Proposal"
- Attach: LangChain example notebook
- Ask: Documentation mention, data loader contribution
-
LlamaIndex Team
- Contact: hello@llamaindex.ai
- Subject: "Skill Seekers - LlamaIndex Integration"
- Attach: LlamaIndex example
- Ask: Collaboration on data loader
-
Pinecone Team
- Contact: community@pinecone.io
- Subject: "Integration Guide: Documentation → Pinecone"
- Attach: Pinecone integration guide
- Ask: Feedback, docs mention
Week 2 Emails (Send Monday)
-
Cursor Team
- Contact: support@cursor.sh
- Subject: "Integration Guide: Skill Seekers → Cursor"
- Attach: Cursor integration guide
- Ask: Docs mention
-
Windsurf/Codeium
- Contact: hello@codeium.com
- Subject: "Windsurf Integration Guide"
- Attach: Windsurf guide
-
Cline Maintainer
- Contact: Saoud Rizwan (via GitHub issues or Twitter @saoudrizwan)
- Subject: "Cline + Skill Seekers MCP Integration"
- Angle: MCP tools
-
Continue.dev
- Contact: Nate Sesti (via GitHub)
- Subject: "Continue.dev Context Provider Integration"
- Angle: Multi-platform support
Week 4 Emails (Follow-ups)
8-11. Follow-ups to all above - Share results/metrics - Ask for feedback - Propose next steps
12-15. Podcast/YouTube Channels - Fireship (fireship.io/contact) - Theo - t3.gg - Programming with Lewis - AI Engineering Podcast
🌐 Where to Share (Priority Order)
Tier 1: Must Post (Day 1-3)
- Dev.to (main blog)
- Twitter/X (thread)
- GitHub Discussions (release notes)
- r/LangChain
- r/LLMDevs
- Hacker News (Show HN)
Tier 2: Should Post (Day 3-7)
- Medium (cross-post)
- r/cursor
- r/ClaudeAI
- r/webdev
- r/programming
Tier 3: Nice to Post (Week 2)
- r/LocalLLaMA
- r/selfhosted
- r/devops
- r/github
- Product Hunt
- Indie Hackers
- Lobsters
📊 Tracking Spreadsheet
Create a simple spreadsheet to track:
| Platform | Post Date | URL | Views | Engagement | Notes |
|---|---|---|---|---|---|
| Dev.to | |||||
| r/LangChain | |||||
| ... |
🎯 Weekly Goals
Week 1 Goals
- 1 main blog post published
- 1 Twitter thread posted
- 3 Reddit posts submitted
- 3 emails sent
- 1 Hacker News submission
Target: 500+ views, 20+ stars, 3+ emails responded
Week 2 Goals
- 1 RAG tutorial published
- 1 AI coding guide published
- 4 more Reddit posts
- 4 more emails sent
- Twitter engagement continued
Target: 800+ views, 40+ total stars, 5+ emails responded
Week 3 Goals
- GitHub Action announcement
- 1 automation tutorial
- Product Hunt submission
- 2 follow-up emails
Target: 1,000+ views, 60+ total stars
Week 4 Goals
- Results blog post
- 4 follow-up emails
- Integration comparison matrix
- Next phase planning
Target: 2,000+ total views, 80+ total stars
🚀 Daily Checklist
Morning (15 min)
- Check GitHub stars (track growth)
- Check Reddit posts (respond to comments)
- Check Twitter (engage with mentions)
Work Session (1-2 hours)
- Create content OR
- Post to platform OR
- Send outreach emails
Evening (15 min)
- Update tracking spreadsheet
- Plan tomorrow's focus
- Note any interesting comments/feedback
✅ Pre-Flight Checklist
Before hitting "Publish":
- All links work (GitHub, docs, website)
- Installation command tested:
pip install skill-seekers - Example commands tested
- Screenshots ready (if using)
- Code blocks formatted correctly
- Call to action clear (star, try, share)
- Tags/keywords added
💡 Pro Tips
Timing
- Dev.to: Tuesday-Thursday, 9-11am EST (best engagement)
- Twitter: Tuesday-Thursday, 8-10am EST
- Reddit: Tuesday-Thursday, 9-11am EST
- Hacker News: Tuesday, 9-10am EST (Show HN)
Engagement
- Respond to ALL comments in first 2 hours
- Pin your best comment with additional links
- Cross-link between posts (blog → Twitter → Reddit)
- Use consistent branding (same intro, same stats)
Email Outreach
- Send Tuesday-Thursday, 9-11am recipient timezone
- Follow up once after 5-7 days if no response
- Keep emails under 150 words
- Always include working example/link
🎬 START NOW
Your first 3 tasks (Today):
- Write main blog post (Dev.to) - 3 hours
- Create Twitter thread - 1 hour
- Draft Reddit posts - 1 hour
Then tomorrow: 4. Publish on Dev.to 5. Post Twitter thread 6. Submit to r/LangChain
You've got this! 🚀