
X Founder Operations
- 27 installs
- 20 repo stars
- Updated August 4, 2026
- qverisai/open-qveris-skills
Automate founder operations and scale team workflows for growing startups
About
X Founder Operations is an AI-powered operations automation agent that provides founder workflow optimization. Use it when you need intelligent automation of startup operations at scale.
- Founder automation
- Ops efficiency
- Process tracking
- AI insights
X Founder Operations by the numbers
- 27 all-time installs (skills.sh)
- Ranked #1,919 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/qverisai/open-qveris-skills --skill x-founder-operationsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 27 |
|---|---|
| repo stars | ★ 20 |
| Last updated | August 4, 2026 |
| Repository | qverisai/open-qveris-skills ↗ |
What it does
Automate founder operations and scale team workflows for growing startups
Files
X Founder Operations
Systematic X (Twitter) account operations for founders, indie developers, and tech professionals.
Who This Is For
- Founders: Building a brand, generating leads, fundraising, hiring, and establishing thought leadership while running a company
- Indie developers: Growing an audience around products, sharing the build journey, converting followers to users
- Tech professionals: Building a personal brand, establishing domain expertise, expanding professional network
This skill adapts to your specific role, goals, and growth stage through configurable profiles and goals.
Core Philosophy
Three Pillars
1. Authenticity First: Your persona is a focused version of who you really are, not a character you play. People follow people, not brands. 2. Value Before Promotion: 80% of content should deliver genuine value. Trust is built slowly and lost quickly. 3. Data-Driven Evolution: Every post generates data. Every data point informs the next decision. Strategy evolves through empirical results, not gut feeling.
Data Integrity (Non-Negotiable)
- NEVER fabricate tweet content, metrics, or URLs
- NEVER guess or hallucinate to fill data gaps
- ALWAYS validate data through the validation workflow
- ALWAYS mark missing data as `null`, never assume values
When API calls fail: STOP, report the failure honestly, and never proceed with fabricated data. See Data Validation Script for the full validation workflow.
Quick Start
1. Set Up Your Profile
Copy and customize the config templates:
config/profile.example.json → config/profile.json
config/goals.example.json → config/goals.json
config/watchlist.example.json → config/watchlist.json
config/content-calendar.example.json → config/content-calendar.jsonFill in your handle, role, product info, voice attributes, and target audience. See Profile Optimization for guidance on optimizing your X profile.
2. Define Your Goals
In config/goals.json, set:
- Primary objective (brand building, lead gen, fundraising, hiring, thought leadership)
- Growth stage (early, growth, established, authority)
- Monthly and quarterly targets
- Content mix ratios
See Growth Benchmarks for realistic targets by growth stage.
3. Build Your Watchlist
In config/watchlist.json, identify:
- 5-10 core circle accounts for daily engagement
- 3-5 competitor accounts to monitor
- Industry and media accounts to track
- Relevant X Communities to join
4. Start the Daily Loop
Follow the Operations Methodology PDCA loop:
Morning: Scan → Plan → Warm Up (30-45 min)
Daytime: Create → Post → Engage (throughout the day)
Evening: Check metrics → Reflect → Plan tomorrow (15-20 min)Daily Operations Loop
The core operating system. See Methodology for full details.
Morning Phase: Plan + Warm Up
1. Scan: Check overnight mentions, core circle activity, trending topics 2. Plan: Select today's content from calendar, prepare tweet drafts 3. Warm up: Spend 15-20 min replying to 10-15 accounts from your core circle (this primes the algorithm before your own posts)
Execution Phase: Create + Post + Engage
4. Post 2-3 tweets at optimal windows (see Cron Schedule), spaced 2-3 hours apart 5. Stay active 30-60 min after each post — reply to every comment in the first hour 6. Engage with core circle and community 2-3 times throughout the day 7. No external links in main tweet body — always put links in the first reply
Evening Phase: Check + Reflect
8. Collect metrics for today's posts 9. Quick reflection using Daily Review Template 10. Plan tomorrow: draft content, identify engagement targets
Weekly/Monthly/Quarterly
- Weekly (Sunday evening): Performance review, content audit, A/B test assessment, next week planning. Use Weekly Review Template.
- Monthly: Goal progress evaluation, strategy assessment, competitor analysis, persona check. Use Monthly Review Template.
- Quarterly: Major strategy review, goal reset, persona evolution, skill updates.
Content Strategy
See Content Strategy for the full framework.
Five Content Pillars
| Pillar | Target % | Purpose |
|---|---|---|
| Technical Depth | 40% | Tips, insights, tutorials — builds authority |
| Industry Pulse | 25% | Hot takes, predictions, trend analysis — builds thought leadership |
| Builder's Journey | 25% | Build-in-public, decisions, lessons — builds connection |
| Community Value | 10% | Questions, polls, resources — builds community |
| Personal Touch | woven in | Humor, personality, human moments — builds "活人感" |
Content Pipeline
Ideation → Drafting → Review → Scheduling → Posting → MeasurementEach step has quality checks. See Content Strategy: Content Pipeline for details.
Proven Content Formulas
- Claim + Evidence + CTA: Bold claim, specific proof, discussion prompt
- Story + Lesson + Takeaway: Brief narrative, what happened, actionable insight
- Question + Context + Invitation: Thoughtful question, why you're asking, invite perspectives
- List + Value + CTA: Numbered items with brief explanations, bookmark/follow prompt
- Reaction + Analysis + Prediction: News reference, your unique analysis, what happens next
Content Repurposing
- High-performing thread → 5-7 standalone tweets over the following week
- Popular single tweet → expand into a full thread
- Thread → blog post or newsletter; blog → thread
- Repost top content every 3-4 weeks with fresh phrasing
Thread Strategy
Threads are the highest-leverage growth mechanism on X. See Thread Playbook.
Thread Architecture
Hook (stop the scroll) → Context → Value Delivery (one point per tweet) → Summary → CTAKey Guidelines
- Optimal length: 5-7 tweets for most founders
- Post at 08:00-10:00 in target audience timezone
- Include visuals in 60-70% of thread tweets
- Prepare day before, post Tuesday-Thursday
- Target: 1-2 threads per week
Multimodal Content
See Multimodal Guide for complete guidance.
Impact
- Native video: ~10x distribution vs text-only
- Images: 2-3x engagement vs text-only
- Visuals increase dwell time (key algorithm signal)
Visual Types
| Type | Best For |
|---|---|
| Screenshots | Product demos, code output, real data, dashboards |
| Diagrams | System architecture, workflows, mental models |
| Code snippets | Technical tutorials, debugging stories |
| Memes | Industry humor, personality, cultural commentary |
| Data visualizations | Research, trends, build-in-public metrics |
| Video (native) | Product demos, talking head takes, tutorials |
The "活人感" Rule
Every visual should feel like a real person made it. Slightly imperfect screenshots, hand-drawn diagrams, and real workspace photos signal authenticity. Overly polished, stock-photo, or obviously AI-generated visuals signal corporate or fake.
Product Integration ("夹带私货")
See Product Integration for the full framework.
Three Tiers
| Tier | What | Frequency | How |
|---|---|---|---|
| Tier 1: Background | Product exists in your world, not the subject | Default mode | Bio, profile, pinned tweet do the work |
| Tier 2: Contextual | Product mentioned as example within a broader insight | ~10% of posts | "When we built [X], we found..." |
| Tier 3: Direct | Product is the subject: launches, milestones, demos | ~10% of posts | Launch threads, milestone celebrations |
Golden Rule
If you removed the product mention, the tweet should still be valuable. The product is the proof, not the point.
CTA Optimization
- Never put links in the main tweet (30-50% algorithm penalty)
- Soft CTAs work better than hard sells on X
- Match CTA to relationship stage: new followers → "follow for more"; engaged followers → "try it"
Engagement Playbook
See Engagement Playbook for full details.
Engagement Funnel
Stranger → Lurker → Follower → Fan → Advocate → Customer/PartnerCore Circle
Identify 20-30 key accounts. Engage with Tier 1 accounts daily, Tier 2 accounts 3-4x/week, Tier 3 opportunistically. See Watchlist Config.
Reply Quality Framework
| Level | Type | Impact |
|---|---|---|
| S | Data/Evidence | Very high |
| A | Novel Perspective | High |
| B | Personal Story | High |
| C | Thoughtful Question | Medium |
| D | Agreement + Extension | Medium |
| F | Empty Agreement ("So true!") | Zero — never do this |
Additional Channels
- X Spaces: Host bi-weekly audio discussions; invite guests from core circle
- X Communities: Post in 3-5 relevant communities; provide value, not promotion
- DMs: After 3+ public interactions, send genuine (not salesy) direct messages
- X Lists: Private lists for competitors, industry leaders, investors, potential customers
Persona & Voice
See Persona & Voice Guide.
Voice Attributes
Define your position on each spectrum in config/profile.json:
- Technical Depth: Surface ←→ Deep
- Humor: Serious ←→ Playful
- Formality: Casual ←→ Formal
- Vulnerability: Guarded ←→ Open
- Boldness: Cautious ←→ Provocative
Consistency Rules
- Maintain consistent tone across all content (the algorithm learns your pattern)
- Adapt tone to context (technical vs personal vs promotional) while keeping core voice
- Build personality anchors: recurring themes, catchphrases, or running jokes that create recognition
- For bilingual users: English for technical/international content, native language for personal/cultural content
Algorithm Awareness
See Algorithm Guide for complete details.
Key Rules
1. First 30 minutes determine reach: Engagement velocity in the first 15-30 min drives 80%+ of total reach 2. Reply > Retweet > Bookmark > Like: Algorithm weights replies highest (~1x), likes lowest (~0.5x) 3. External links are penalized: 30-50% fewer impressions. Links go in first reply. 4. Consistency rewards: Sudden posting changes trigger spam detection. Maintain steady cadence. 5. Niche specificity: Stay focused on 2-3 topics. Random off-topic posts dilute your algorithm placement. 6. Negative signals are devastating: Mute/block/report carry ~-74x weight. Never post hostile content. 7. Video gets priority: Native video gets ~10x distribution vs text-only.
Goal Framework
Configure in goals.json. The skill adapts recommendations based on your primary objective and growth stage.
Primary Objectives
| Objective | Key X Activities |
|---|---|
| Brand building | Consistent voice, thought leadership content, thread strategy |
| Lead generation | Product integration, bio link optimization, CTA strategy |
| Fundraising | Industry analysis, investor engagement, traction posts |
| Hiring | Engineering challenges, culture posts, team stories |
| Thought leadership | Deep technical content, contrarian takes, Spaces hosting |
| Community building | Questions, engagement, Spaces, community participation |
Growth Stages
| Stage | Followers | Focus |
|---|---|---|
| Early | 0-1K | Finding voice, building core circle, posting consistently |
| Growth | 1K-10K | Thread strategy, content mix optimization, relationship depth |
| Established | 10K-50K | Authority content, Spaces hosting, selective engagement |
| Authority | 50K+ | Maintaining quality, community leadership, platform leverage |
See Growth Benchmarks for realistic targets by stage.
Automated Operations
See Cron Schedule for the full task schedule.
Daily Automated Tasks
| Task | Timing | Purpose |
|---|---|---|
| Morning Scan | 30 min before Window A | Trending topics, core circle activity, overnight mentions |
| Window A Reminder | Start of posting window | Content recommendation based on calendar + scan |
| Midday Collection | Between windows | Updated trends, Window A post metrics |
| Window B Reminder | Start of posting window | Updated recommendation for evening window |
| Engagement Follow-up | 30 min after Window B | Identify reply opportunities, quote tweet candidates |
| Mentions Check | 1 hour after Window B | Categorize and prioritize mentions |
| Evening Review | End of day | Metrics collection, daily performance summary |
Validation Workflow
All automated data collection follows this pipeline:
x-timeline → Get tweet list
↓
x-tweet-info → Get detailed metrics per tweet
↓
Cross-validate → ID, author, timestamp consistency
↓
Sanity check → Reasonable data (likes ≤ impressions, no negatives)
↓
Report → Mark anomalies, never guessCompetitor Analysis
See Competitor Framework.
Select 5-8 benchmark accounts across three categories:
- Aspirational (2-3): 10-100x your size, same niche
- Peer (2-3): Similar size and growth stage
- Emerging (1-2): Smaller but growing fast
Analyze monthly: content formulas, engagement patterns, posting times, visual strategy. Extract what works, adapt to your voice.
Tools and Scripts
Data Validation
File: scripts/x_data_validator.py Validates X data through a 5-layer pipeline: API status, tweet ID presence, cross-validation, metrics completeness, data sanity checks.
Content Planner
File: scripts/content_planner.py Reads profile, goals, and calendar config to generate daily content recommendations with content mix compliance tracking.
Analytics Reporter
File: scripts/analytics_reporter.py Generates performance reports using the validation workflow. Produces weekly and monthly analytics with benchmark comparisons.
Smoke Tests (Regression Guard)
Location: tests/ — 63 unit tests covering all three scripts.
Run:
# No dependencies required — uses Python stdlib unittest
python3 -m unittest discover tests/ -v
Run after any script change before shipping.
## Emergency Protocols
### API Failures
1. Retry with exponential backoff (3 attempts max)
2. If still failing: report to user with clear error
3. NEVER proceed with fabricated data
### Content Crisis
1. Pause all automated posts
2. Review recent content for issues
3. Prepare response strategy
4. Notify user immediately
### Data Anomalies
1. Flag immediately in validation report
2. Cross-check with alternative sources
3. Don't include suspicious data in analysis
4. Alert user to investigate
## References
### Methodology & Strategy
- [Operations Methodology](references/methodology.md) — PDCA daily loop, A/B testing, review cadences
- [Content Strategy](references/content-strategy.md) — 5-pillar system, content pipeline, formulas, timing
- [Thread Playbook](references/thread-playbook.md) — Thread architecture, hooks, scheduling, repurposing
- [Multimodal Guide](references/multimodal-guide.md) — Visual types, tools, "活人感" checklist
- [Product Integration](references/product-integration.md) — 3-tier promotion, CTA optimization, launch playbook
### Growth & Engagement
- [Engagement Playbook](references/engagement-playbook.md) — Funnel, core circle, reply quality, DMs, Spaces
- [Persona & Voice Guide](references/persona-voice.md) — Voice development, consistency, language mix
- [Algorithm Guide](references/algorithm-guide.md) — How the X algorithm works, optimization tactics
- [Profile Optimization](references/profile-optimization.md) — Bio, photo, pinned tweet, header
### Analysis & Benchmarks
- [Competitor Framework](references/competitor-framework.md) — Benchmark selection, analysis template
- [Growth Benchmarks](references/growth-benchmarks.md) — Industry data by account size and content type
- [Cron Schedule](references/cron-schedule.md) — Automated task schedule, error handling
### Configuration
- [Profile Config](config/profile.example.json) — Handle, role, product, voice, audience
- [Goals Config](config/goals.example.json) — Objectives, targets, KPIs, content mix
- [Watchlist Config](config/watchlist.example.json) — Core circle, competitors, communities
- [Content Calendar](config/content-calendar.example.json) — Weekly rhythm, posting windows
### Templates
- [Daily Review](templates/daily-review.md)
- [Weekly Review](templates/weekly-review.md)
- [Monthly Review](templates/monthly-review.md)
- [Performance Report](templates/performance-report.md)
## Remember
**Trust is built through consistent reliability.** Every post, every reply, every data point matters. Never compromise on data integrity. Never sacrifice authenticity for engagement.
This skill is a living system. It evolves with every daily review, every weekly analysis, and every quarterly strategy reset. The methodology ensures you're always getting smarter about what works for YOUR specific account, audience, and goals.
.evolution/
Runtime state directory for the X Founder Operations skill.
Files in this directory are generated and updated during daily operations. They are gitignored (only this README is committed).
Files
reflections.json— Accumulated lessons learned, performance patterns, and strategy adjustments. Updated during daily/weekly reviews.strategy-state.json— Current strategy parameters: what content mix is working, which posting times are optimal, which engagement tactics are producing results. Used by the PDCA loop to inform next-cycle planning.
Design Principle
Evolution state captures what the skill has learned about this specific account over time. It allows the daily operations loop to make data-informed decisions rather than starting from scratch each cycle.
Unlike config/ (which captures user intent and setup), .evolution/ captures empirical results and adaptive learning.
# User-specific config (only .example files are committed)
config/profile.json
config/goals.json
config/watchlist.json
config/content-calendar.json
# Runtime evolution state
.evolution/reflections.json
.evolution/strategy-state.json
# OS artifacts
.DS_Store
# Python
__pycache__/
*.pyc
{
"weekly_rhythm": {
"monday": {
"theme": "Industry Pulse",
"morning": "Trend analysis or hot take on weekend developments",
"afternoon": "Reply to weekend thought leader posts",
"thread_day": false
},
"tuesday": {
"theme": "Technical Depth",
"morning": "Deep technical insight or tutorial",
"afternoon": "Engage with community technical discussions",
"thread_day": true,
"thread_note": "Best day for educational threads"
},
"wednesday": {
"theme": "Builder's Journey",
"morning": "Behind-the-scenes product insight or decision",
"afternoon": "Build-in-public update with real metrics",
"thread_day": false
},
"thursday": {
"theme": "Community Value",
"morning": "Question, poll, or resource share",
"afternoon": "Reply to mentions, engage with replies",
"thread_day": true,
"thread_note": "Good for resource/list threads"
},
"friday": {
"theme": "Personal Touch + Week Recap",
"morning": "Founder reflection or prediction",
"afternoon": "Light/humorous content, community engagement",
"thread_day": false
},
"saturday": {
"theme": "Light Engagement",
"activity": "Monitor for real-time opportunities, casual replies",
"thread_day": false
},
"sunday": {
"theme": "Planning + Review",
"activity": "Weekly review, plan next week's content, schedule threads",
"thread_day": false
}
},
"posting_windows": {
"description": "Configure based on your timezone relative to target audience",
"window_a": {
"label": "Morning window (target audience morning/lunch)",
"target_audience_time": "09:00-12:00",
"content_type": "Technical insights, threads, product updates"
},
"window_b": {
"label": "Afternoon window (target audience evening)",
"target_audience_time": "17:00-20:00",
"content_type": "Engagement content, questions, lighter posts"
}
},
"thread_schedule": {
"frequency": "1-2 per week",
"best_days": ["tuesday", "thursday"],
"best_time": "08:00-10:00 in target audience timezone",
"preparation": "Draft day before, review morning of posting"
}
}
{
"primary_objective": "brand_building",
"primary_objective_options": [
"brand_building",
"lead_generation",
"fundraising",
"hiring",
"thought_leadership",
"community_building",
"product_launch"
],
"growth_stage": "early",
"growth_stage_definitions": {
"early": "0-1K followers, establishing presence",
"growth": "1K-10K followers, building momentum",
"established": "10K-50K followers, scaling influence",
"authority": "50K+ followers, maintaining leadership"
},
"targets": {
"1_month": {
"follower_growth_pct": 20,
"avg_engagement_rate_pct": 2.0,
"avg_impressions_per_tweet": 200,
"weekly_threads": 1,
"daily_tweets": 3,
"daily_replies": 10,
"key_relationship_targets": 5
},
"3_month": {
"follower_growth_pct": 50,
"avg_engagement_rate_pct": 3.0,
"avg_impressions_per_tweet": 500,
"weekly_threads": 2,
"daily_tweets": 5,
"daily_replies": 15,
"key_relationship_targets": 15
},
"6_month": {
"follower_growth_pct": 150,
"avg_engagement_rate_pct": 3.5,
"avg_impressions_per_tweet": 1000,
"weekly_threads": 2,
"daily_tweets": 5,
"thought_leader_mentions": 5,
"speaking_invitations": 2
}
},
"kpis": {
"primary": ["engagement_rate", "follower_growth", "impressions_per_tweet"],
"secondary": ["reply_rate", "bookmark_rate", "profile_visits", "link_clicks"],
"business": ["website_referrals_from_x", "leads_from_x", "mentions_by_target_accounts"]
},
"content_mix": {
"value_tweets_pct": 40,
"opinion_tweets_pct": 25,
"story_tweets_pct": 25,
"engagement_tweets_pct": 10,
"promotional_cap_pct": 20
}
}
{
"handle": "@your_handle",
"display_name": "Your Name",
"role": "founder",
"timezone": "America/New_York",
"industry": "AI / Developer Tools",
"product": {
"name": "Your Product",
"url": "https://yourproduct.com",
"one_liner": "One sentence describing what your product does",
"positioning": "How you want to be known in the market",
"core_narrative": "The deeper story behind why you're building this"
},
"background": {
"credentials": ["Ex-BigCo Engineer", "University Degree"],
"unique_perspective": "What makes your viewpoint different from others in your space",
"prior_roles": ["Previous Company - Role"]
},
"target_audience": {
"primary": "Who you most want to reach (e.g., AI engineers, startup founders)",
"secondary": "Secondary audience (e.g., investors, tech media)",
"markets": ["US", "EU"]
},
"voice": {
"attributes": {
"technical_depth": "high",
"humor": "moderate",
"formality": "casual-professional",
"vulnerability": "moderate",
"boldness": "high"
},
"language": {
"primary": "English",
"secondary": null,
"mix_strategy": "English for technical content, native language for personal/cultural content"
},
"personality_anchors": [
"A recurring theme or running joke that builds recognition"
]
},
"content_pillars": {
"technical_depth": "Topics for deep technical insights",
"builders_journey": "Behind-the-scenes, decisions, lessons",
"industry_pulse": "Trends, predictions, hot takes in your space",
"community_value": "Questions, tutorials, resources you share",
"personal_touch": "Humor, personality, human moments"
}
}
{
"core_circle": {
"description": "20-30 accounts you engage with regularly. Reply targets for daily warm-up.",
"accounts": [
{
"handle": "@example_leader",
"category": "thought_leader",
"relevance": "AI/ML technical insights",
"engagement_priority": "high",
"notes": "Posts daily, replies to technical comments"
},
{
"handle": "@example_founder",
"category": "peer_founder",
"relevance": "Building in same space",
"engagement_priority": "high",
"notes": "Good for mutual engagement"
},
{
"handle": "@example_investor",
"category": "investor",
"relevance": "Active in your funding stage/sector",
"engagement_priority": "medium",
"notes": "Engage thoughtfully, demonstrate domain expertise"
}
]
},
"competitors": {
"description": "Accounts doing similar things. Monitor for content strategy insights.",
"accounts": [
{
"handle": "@competitor_1",
"category": "direct_competitor",
"what_to_track": ["content_angles", "posting_times", "engagement_patterns"]
}
]
},
"industry_accounts": {
"description": "Official accounts, media, newsletters in your space.",
"accounts": [
{
"handle": "@industry_news",
"category": "media",
"what_to_track": ["breaking_news", "trending_topics"]
}
]
},
"potential_customers": {
"description": "People showing buying signals or discussing problems you solve.",
"accounts": []
},
"x_communities": {
"description": "Relevant X Communities to post in and monitor.",
"communities": [
{
"name": "Community Name",
"url": "https://x.com/i/communities/...",
"relevance": "Your niche topic",
"posting_frequency": "2-3x per week"
}
]
}
}
X Founder Operations
Systematic X (Twitter) account operations skill for founders, indie developers, and tech professionals.
SEO Keywords
OpenClaw, X operations skill, Twitter growth strategy, founder personal branding, indie developer marketing, tech Twitter, content strategy, engagement playbook, thread strategy, build in public, AI agent social media, X algorithm optimization, community building, product promotion, thought leadership
What This Skill Does
X Founder Operations provides a complete operating system for running an effective X account. It implements a daily Plan-Do-Check-Act (PDCA) closed loop that continuously optimizes your content, engagement, and growth strategy based on real performance data.
Core Capabilities
- Daily operations loop: Structured morning scan, content creation, engagement, and evening review
- Content strategy: 5-pillar system with proven formulas, templates, and content pipeline
- Thread growth playbook: Architecture, hook formulas, scheduling, and repurposing
- Multimodal content: Image, video, diagram, and meme strategy for authentic engagement
- Product promotion: 3-tier "夹带私货" framework for natural product integration
- Engagement playbook: Core circle strategy, reply quality framework, DMs, X Spaces
- Persona development: Voice attributes, consistency rules, "活人感" (human feel) checklist
- Algorithm awareness: How the X algorithm works and how to optimize for it
- Competitor analysis: Benchmark selection, content formula extraction, gap identification
- Data-driven evolution: A/B testing, performance analytics, continuous improvement
- Automated scheduling: Cron-based task schedule with timezone configuration
Who It's For
| Role | Primary Use |
|---|---|
| Founders | Brand building, lead generation, fundraising, hiring, thought leadership |
| Indie Developers | Audience building, build-in-public, converting followers to users |
| Tech Professionals | Personal branding, domain expertise, professional networking |
Quick Start
1. Copy config templates and customize:
config/profile.example.json → config/profile.json
config/goals.example.json → config/goals.json
config/watchlist.example.json → config/watchlist.json
config/content-calendar.example.json → config/content-calendar.json2. Optimize your X profile using references/profile-optimization.md
3. Start the daily PDCA loop described in references/methodology.md
4. Set up automated tasks from references/cron-schedule.md
Project Structure
x-founder-operations/
├── SKILL.md # Core skill definition
├── README.md # This file
├── .gitignore
├── config/
│ ├── profile.example.json # User profile template
│ ├── goals.example.json # Goal framework template
│ ├── watchlist.example.json # Accounts to engage/monitor
│ └── content-calendar.example.json # Weekly content rhythm
├── references/
│ ├── methodology.md # PDCA daily loop system
│ ├── content-strategy.md # 5-pillar content framework
│ ├── thread-playbook.md # Thread growth strategy
│ ├── multimodal-guide.md # Visual content creation
│ ├── product-integration.md # Product promotion framework
│ ├── engagement-playbook.md # Community & relationship building
│ ├── persona-voice.md # Voice development guide
│ ├── algorithm-guide.md # X algorithm mechanics
│ ├── profile-optimization.md # Profile conversion optimization
│ ├── competitor-framework.md # Competitor analysis methodology
│ ├── growth-benchmarks.md # Industry benchmark data
│ └── cron-schedule.md # Automated task schedule
├── templates/
│ ├── daily-review.md # Daily PDCA review template
│ ├── weekly-review.md # Weekly performance review
│ ├── monthly-review.md # Monthly strategy review
│ └── performance-report.md # Analytics report template
├── scripts/
│ ├── x_data_validator.py # Data validation workflow
│ ├── content_planner.py # Content recommendation engine
│ └── analytics_reporter.py # Performance analytics
└── .evolution/
└── README.md # Runtime state documentationKey Design Principles
- Config over hardcode: All user-specific data in
config/, all methodology inreferences/ - Closed-loop by design: Every action feeds back into the next iteration
- Role-adaptive: Strategy adapts to founder, indie dev, or tech professional
- Multimodal-first: Every content template considers visual elements
- Authentic over viral: Sustainable growth through genuine value, not engagement hacking
- Data-driven evolution: Metrics drive strategy changes, not gut feeling
Data Integrity
This skill enforces strict data integrity:
- Never fabricates tweet content, metrics, or URLs
- Validates all data through a 5-layer pipeline (API status, ID presence, cross-validation, metrics completeness, sanity checks)
- Missing data is marked as
null, never substituted with 0 or estimates - All anomalies are flagged and reported
Prompt Examples
- "Plan today's X content and engagement"
- "Review yesterday's tweet performance and iterate"
- "Draft a thread about [topic]"
- "Analyze competitor accounts and find engagement opportunities"
- "Run weekly X operations review"
- "Help me optimize my X profile for conversions"
- "What content should I post this week?"
- "Generate a performance report for this month"
Notes
- Config files (
config/*.json) are gitignored. Only.example.jsontemplates are committed. - Runtime evolution state (
.evolution/*.json) is gitignored and generated during operations. - The skill is designed for use with OpenClaw-compatible agents but the methodology and references are useful standalone.
- All posting times should be configured relative to your target audience's timezone.
License
This skill is part of the open-qveris-skills collection.
X Algorithm Guide (2025-2026)
How the X algorithm distributes content and how to work with it.
---
How Distribution Works
Every tweet enters a ranking pipeline. The algorithm decides who sees it based on four signal categories:
1. Engagement velocity — Speed of interactions in the first 15-30 minutes 2. Relationship signals — History of interactions between author and viewer 3. Content quality — Predicted engagement based on content features 4. Interest matching — Topic alignment via SimClusters (~145K topic groups)
The critical insight: early, fast engagement matters far more than total engagement. A tweet with 10 interactions in 5 minutes outranks one with 100 interactions over 24 hours.
---
Engagement Weight Hierarchy
Not all engagement is equal. Approximate weights:
| Action | Weight | Notes |
|---|---|---|
| Reply | 1x (baseline) | Signals conversation; strongest positive signal |
| Retweet / Quote | ~1x | Signals distribution-worthy content |
| Bookmark | ~1x | Signals high-intent relevance (save-worthy) |
| Like | ~0.5x | Passive; weakest positive signal |
| Profile click | ~24x vs like | Strong interest signal |
| 2+ min dwell time | ~22x vs like | Deep content consumption |
| Mute | ~-74x | Devastating negative signal |
| Block | ~-74x | Devastating negative signal |
| Report | ~-74x | Devastating negative signal |
Optimization priority: Create content that generates replies, bookmarks, and extended reading time — not just likes.
---
Key Algorithm Rules
1. The 30-Minute Window
The first 30 minutes after posting determine 80%+ of a tweet's total reach. Tactics to win this window:
- Post when your audience is most active (not when convenient for you)
- "Warm up" before posting by spending 30 min replying to others (signals you're an active user)
- Have your core circle ready to engage early
- Craft hooks that stop the scroll and prompt immediate replies
2. External Links Are Penalized
Tweets with external links receive 30-50% fewer impressions. The algorithm wants users to stay on X.
Workaround: Post your insight as a text/image tweet, then add the link in the first reply. Reference "link in reply" or use a bookmark-worthy format.
3. Consistency Rewards, Sudden Changes Punish
The algorithm learns your account-specific posting patterns. Sudden behavior changes (e.g., going from 2 tweets/day to 15, or going silent for a week) trigger spam detection and reduce reach.
- Maintain a consistent posting cadence
- Ramp up gradually when increasing frequency
- If you need to go offline, don't disappear entirely — schedule a few posts
4. SimClusters and Niche Specificity
X places every account into topic clusters (~145K clusters). Your content reaches people in overlapping clusters first. Staying focused on 2-3 related topics maximizes cluster alignment and reach.
Anti-pattern: Posting about random unrelated topics dilutes your cluster placement and confuses the algorithm about who to show your content to.
5. Sentiment Analysis
The algorithm runs sentiment analysis on content:
- Positive, constructive content gets wider distribution
- Negative, hostile, or divisive content is throttled
- Contrarian takes are fine — hostility is not
6. Dwell Time
How long users spend reading your content is a ranking signal. Longer-form content (threads, detailed tweets, image carousels) that holds attention gets rewarded.
Tactics to increase dwell time:
- Use line breaks and formatting for readability
- Include images or diagrams that require inspection
- Write threads where each tweet compels reading the next
- Provide enough depth that people pause to think
7. Video Gets Priority
Native video (uploaded directly to X) receives approximately 10x the distribution of text-only posts. Long-form video (2+ minutes) performs best. External video links (YouTube, etc.) are penalized like any other external link.
---
Algorithm Anti-Patterns
Things that hurt your reach:
| Anti-Pattern | Consequence |
|---|---|
| "Like if you agree" / forced engagement bait | Actively penalized since 2024 |
| Sudden posting frequency changes | Spam detection, reduced reach |
| Excessive external links | 30-50% fewer impressions per link tweet |
| Off-topic content (breaking niche) | Diluted SimCluster placement |
| Negative/hostile tone | Algorithmic throttling |
| Buying followers or engagement | Destroys SimCluster placement, fake accounts get pruned |
| Deleting and reposting tweets | Resets engagement, algorithm sees inconsistency |
---
Practical Playbook
Before Every Post
1. Check: is your audience awake and active right now? 2. Spend 15-30 min engaging with others first (warm up the algorithm) 3. Ensure no external links in the main tweet body 4. Craft a hook designed to generate replies, not just likes
After Every Post
1. Stay active for 30-60 minutes after posting 2. Reply to every comment in the first hour (signals active conversation) 3. Don't post another tweet for 2-3 hours (let this one breathe)
Weekly Algorithm Hygiene
1. Review which content types generate the most replies vs. likes 2. Double down on reply-generating formats 3. Check if any posts triggered negative signals (low impressions = possible throttle) 4. Ensure posting consistency (no big gaps or spikes)
---
Algorithm Guide v1.0 — Based on X algorithm analysis and public documentation as of early 2026
Competitor Analysis Framework
How to systematically analyze other X accounts in your space, extract actionable insights, and adapt their successful tactics to your own voice.
---
Purpose
Competitor analysis is not about copying. It's about: 1. Understanding what content patterns work in your niche 2. Identifying engagement formulas you can adapt 3. Finding gaps that no one else is filling 4. Calibrating your benchmarks against reality
---
Selecting Benchmark Accounts
Choose 5-8 accounts across three categories:
Category 1: Aspirational (2-3 accounts)
Accounts 10-100x your size in your niche. They show what's possible and what content resonates at scale.
Selection criteria: Same industry/topic, high engagement rate (not just follower count), content you genuinely respect.
Category 2: Peer (2-3 accounts)
Accounts at a similar size and growth stage. They show what's realistic and what tactics work at your scale.
Selection criteria: Similar follower count (+/- 50%), same niche, actively growing (not dormant).
Category 3: Emerging (1-2 accounts)
Accounts smaller than you but growing fast. They show innovative tactics and untapped angles.
Selection criteria: Rapid growth (50%+ monthly), novel content approaches, high engagement-to-follower ratio.
Configure these in watchlist under competitors.
---
Analysis Framework
For each benchmark account, analyze these dimensions monthly:
1. Content Strategy Analysis
| Dimension | What to Track |
|---|---|
| Content pillars | What topics do they cover? What's their mix? |
| Content formats | Single tweets, threads, videos, images, polls? |
| Posting frequency | How many tweets/day? Threads/week? |
| Posting times | When do they post? What timezone do they optimize for? |
| Thread strategy | How often? What topics? What hook styles? |
| Multimodal usage | How do they use images, video, screenshots? |
2. Engagement Pattern Analysis
| Dimension | What to Track |
|---|---|
| Engagement rate | Total engagement / impressions for recent posts |
| Reply vs like ratio | Higher reply ratio = deeper engagement |
| Top-performing content | What gets the most engagement? Why? |
| Worst-performing content | What falls flat? What can you avoid? |
| Reply behavior | Do they reply to comments? How? What tone? |
| Community interaction | Do they engage with others' content? How often? |
3. Content Formula Extraction
For each benchmark account's top 3 performing posts, extract:
Post: [Brief description]
Performance: [Likes, Retweets, Replies, Impressions, Engagement Rate]
Format: [Single tweet / Thread / Quote tweet / Image / Video]
Structure:
1. Hook type: [Bold claim / Question / Story / etc.]
2. Value delivery: [How they deliver the core insight]
3. Visual element: [What image/video/screenshot they used]
4. CTA: [What they asked readers to do]
Why it worked: [Your analysis]
What you can adapt: [Specific takeaway for your content]---
Monthly Competitor Report Template
# Competitor Analysis — [Month Year]
## Benchmark Accounts
- Aspirational: @account1, @account2
- Peer: @account3, @account4
- Emerging: @account5
## Key Findings
### Content Trends
- [What content types are performing well across benchmark accounts]
- [Any new formats or approaches emerging]
### Top-Performing Content (across all benchmarks)
1. [Account] — [Content description] — [Performance metrics]
- Why it worked: [Analysis]
- Adaptable insight: [What you can use]
2. [Account] — [Content description] — [Performance metrics]
- Why it worked: [Analysis]
- Adaptable insight: [What you can use]
3. [Account] — [Content description] — [Performance metrics]
- Why it worked: [Analysis]
- Adaptable insight: [What you can use]
### Content Gaps
- [Topics no one is covering well — opportunities for you]
- [Formats no one is using — first-mover advantage]
### Strategy Insights
- [Timing patterns worth testing]
- [Engagement tactics worth adopting]
- [Persona/voice elements worth adapting]
## Action Items for Next Month
1. [Specific tactic to test]
2. [Content angle to try]
3. [Engagement pattern to adopt]---
Competitive Intelligence Cadence
| Frequency | Action |
|---|---|
| Daily | Quick scan of competitor posts via X Lists |
| Weekly | Note any standout content from competitors |
| Monthly | Full competitor analysis using framework above |
| Quarterly | Re-evaluate benchmark account selection |
---
Rules of Engagement
- Adapt, don't copy: Take the formula, use your own voice and examples
- Analyze the structure, not the content: "Bold claim + evidence + CTA" is a formula; their specific tweet is their content
- Stay in your lane: Don't try to be @karpathy if you're not @karpathy. Extract the principles, apply as yourself
- Watch for declining accounts too: Learn what stops working
- Don't obsess: 30 minutes per month of analysis is enough. Spend 95% of your time creating, not watching
---
Competitor Analysis Framework v1.0
Content Strategy
A systematic framework for creating high-performing X content. This replaces ad-hoc posting with a disciplined pipeline from ideation to measurement.
---
Five Content Pillars
Every piece of content should map to one of these pillars. The mix ratio is configurable in goals (default: 40/25/25/10).
Pillar 1: Technical Depth (40% — Value)
Deep insights, tutorials, analysis, and non-obvious observations about your domain.
Why it works: Establishes authority. Generates bookmarks (high algorithm weight) and long dwell time. Attracts your ideal audience.
Formats:
- Technical insight with concrete example
- Tutorial or how-to (step-by-step)
- Tool/framework comparison
- Architecture or design decision analysis
- Code snippet with explanation
- Data analysis with visualization
Template — Technical Insight:
[Bold technical claim or non-obvious observation]
[Specific example or proof — screenshot, code, data]
[Why this matters for your audience]
[Optional: CTA or question to prompt discussion]Template — Tutorial Thread:
Tweet 1: [Hook — "Here's how to X in Y steps"]
Tweet 2-N: [One step per tweet, with screenshot or code]
Final: [Summary + CTA — "Bookmark for later" or "Follow for more"]Pillar 2: Industry Pulse (25% — Opinion)
Hot takes, predictions, trend analysis, and contrarian perspectives on your industry.
Why it works: Drives engagement through agreement and disagreement. Shows you're plugged into the industry. Generates replies and quote tweets.
Formats:
- Contrarian take on popular opinion
- Prediction with reasoning
- Reaction to industry news (within 2 hours of breaking)
- "Everyone's talking about X, but the real story is Y"
- Comparison of competing approaches
Template — Contrarian Take:
[Conventional wisdom] is wrong.
[Your contrarian position]
[Evidence or reasoning — 2-3 points]
[What this means going forward]Template — Rapid Reaction:
[Breaking news reference]
[Your immediate analysis — what most people miss]
[What this means for your space specifically]
[Optional: link to deeper analysis in reply]Pillar 3: Builder's Journey (25% — Story)
Behind-the-scenes content, build-in-public updates, decisions, failures, and lessons learned.
Why it works: Builds emotional connection. Humanizes you beyond your expertise. Creates loyal followers who feel invested in your journey.
Formats:
- Build-in-public update with real metrics
- Decision and the reasoning behind it
- Failure post-mortem (what went wrong, what you learned)
- Milestone celebration with context
- "Day in the life" moments
- Founder/builder reflections
Template — Build-in-Public Update:
[Product/Project] week [N] update:
[Metric 1]: [number] → [number] ([change])
[Metric 2]: [number] → [number] ([change])
What worked: [specific thing]
What didn't: [specific thing]
Next week: [focus area]
[Screenshot of dashboard/metrics]Template — Lesson Learned:
[Mistake or unexpected outcome]
I thought [assumption].
Reality: [what actually happened].
The lesson: [actionable takeaway]
[Optional: what you're doing differently now]Pillar 4: Community Value (10% — Engagement)
Questions, polls, resource shares, and content designed to spark conversation.
Why it works: Generates replies (highest algorithm weight). Builds community. Surfaces insights from your audience. Shows you value others' perspectives.
Formats:
- Open-ended question about your domain
- "Which do you prefer: A or B?"
- Resource roundup (tools, articles, repos)
- Community highlight (sharing others' great work)
- Poll with follow-up analysis
Template — Engaging Question:
[Specific, answerable question about your domain]
(Genuinely curious — I'm [context for why you're asking])Template — Resource Share:
[N] [tools/resources/articles] I've been using for [specific use case]:
1. [Name] — [one-line why it's good]
2. [Name] — [one-line why it's good]
...
What would you add? 👇Pillar 5: Personal Touch (woven into all pillars)
Humor, personality, cultural references, and human moments. Not a separate category — this is the texture layered into every pillar.
Why it works: Creates the "活人感" (human feel) that differentiates real accounts from bots and corporate accounts. Makes your content memorable and shareable.
How to apply:
- Add a self-deprecating observation to technical content
- Include a relevant meme or cultural reference with industry commentary
- Share a genuine emotional reaction (excitement, frustration, surprise)
- Use your natural speaking voice, not a "content creator" voice
- Occasionally break format with something purely human
---
Content Pipeline
Stage 1: Ideation (Continuous)
Sources for content ideas:
- Your daily work: Problems you're solving, decisions you're making, tools you're using
- Industry feeds: News, product launches, research papers
- Core circle: What are thought leaders discussing? Where can you add value?
- Audience signals: What questions are people asking? What content gets bookmarked?
- Competitor analysis: What angles are working for accounts in your space?
- Personal experience: Unique stories, non-obvious observations, failures
Keep a running list (notes app, draft tweets, content calendar). Capture ideas immediately — don't rely on memory.
Stage 2: Drafting
- Write the core insight first, then craft the hook
- The hook (first line) must stop the scroll: bold claim, surprising stat, contrarian take, or compelling question
- Keep tweets concise. Cut every word that doesn't add value
- For threads: write all tweets, then revise for flow and make each tweet standalone-worthy
- Add visual elements where they enhance the message (see multimodal guide)
- Check product integration opportunity (see product integration)
Stage 3: Review
Before posting, check:
- [ ] Does this add genuine value? Would I engage with this if someone else posted it?
- [ ] Is the hook strong enough to stop the scroll?
- [ ] Is there a clear takeaway or discussion point?
- [ ] No external links in main tweet (links in first reply)
- [ ] No typos, broken formatting
- [ ] Appropriate content pillar and product integration tier
- [ ] Optimal posting time for this content type
Stage 4: Scheduling & Posting
- Schedule using content calendar rhythm (see content calendar config)
- Post at optimal windows for your target audience
- For threads: post at 08:00-10:00 in target audience timezone
- For single tweets: space 2-3 hours apart
- Stay active 30-60 min after posting to reply to early engagement
Stage 5: Measurement
After 24-48 hours, collect:
- Impressions, engagement rate, reply count, bookmark count
- Compare against your baseline (from goals config)
- Tag content type and pillar for pattern analysis
- Feed results into weekly review (see methodology)
---
Content Formulas
Proven structural formulas ranked by typical engagement:
Formula A: Claim + Evidence + Insight
[Bold, specific claim]
[Evidence: data, example, screenshot]
[What this means / why it matters]Best for: Technical depth, industry pulse
Formula B: Story + Lesson + Takeaway
[Brief story or situation]
[What happened / what went wrong]
[The lesson or non-obvious insight]Best for: Builder's journey, personal touch
Formula C: Question + Context + Invitation
[Specific, thoughtful question]
[Why you're asking / your current thinking]
[Invitation to share perspectives]Best for: Community value, engagement
Formula D: List + Value + CTA
[N things about X]
1. [Item + brief explanation]
2. [Item + brief explanation]
...
[CTA: bookmark, follow, what would you add?]Best for: Resource shares, tutorials, threads
Formula E: Reaction + Analysis + Prediction
[Reference to event/news/trend]
[Your analysis — what most people miss]
[What you think happens next]Best for: Industry pulse, rapid reaction to news
---
Content Repurposing Loop
Maximize ROI from every piece of content:
Unbundling (Thread → Standalone Tweets)
A high-performing thread contains 5-10 standalone insights. Over the following week, extract individual tweets:
- Each thread tweet becomes a standalone post with slight rewording
- Space them out (1-2 per day from a single thread)
- Reference the original thread for those who want the full context
Expansion (Tweet → Thread)
When a single tweet performs unexpectedly well:
- Expand the core insight into a 5-7 tweet thread
- Add examples, data, visuals that flesh out the idea
- Post 2-3 days after the original tweet's peak engagement
Cross-Format Repurposing
- Thread → blog post or newsletter edition
- X Spaces discussion → thread summarizing key insights
- Blog post → thread extracting the key points
- Product launch → multiple angles over 1-2 weeks (announcement, behind-the-scenes, user reactions, technical deep-dive)
Evergreen Recycling
- Repost your best-performing content every 3-4 weeks
- Rephrase the hook and update any dated details
- Different audience segments see your content at different times
- Track whether recycled content maintains or declines in performance
---
Timing Framework
Rather than hardcoded posting times, optimize based on YOUR audience's timezone and activity patterns.
Determining Optimal Times
1. Identify your primary audience timezone (from profile config) 2. Map peak activity windows:
- Window A: 09:00-12:00 in audience timezone (morning engagement)
- Window B: 17:00-20:00 in audience timezone (evening engagement)
3. Convert to your local timezone and set up cron reminders (see cron schedule) 4. A/B test: Try different times within these windows and measure
Day-of-Week Patterns
Research-backed general patterns (test for your audience):
- Tuesday-Thursday: Highest engagement for professional/tech content
- Wednesday: Particularly strong for morning threads
- Friday: Good for lighter, community-oriented content
- Weekend: Lower overall but less competition — good for niche technical content
---
Content Strategy v1.0
Cron Schedule
Automated task schedule for daily X operations. Configure based on your timezone and target audience.
---
Timezone Configuration
Calculate your posting windows based on:
- Your timezone: Set in profile config
- Target audience timezone: Usually US East (ET) or US West (PT) for tech/founder accounts
- Peak windows: 09:00-12:00 and 17:00-20:00 in target audience timezone
Timezone Mapping Example
For an operator in Asia (UTC+8) targeting US audiences:
| Your Local | US East (ET) | US West (PT) | Activity |
|---|---|---|---|
| 01:00 | 12:00 | 09:00 | US lunch / West morning — Window A |
| 08:00 | 19:00 | 16:00 | US evening / West afternoon |
| 09:00 | 20:00 | 17:00 | US prime time — Window B |
| 22:00 | 09:00 | 06:00 | US East morning (West too early) |
For an operator in US East (ET):
| Your Local | US East (ET) | US West (PT) | Activity |
|---|---|---|---|
| 09:00 | 09:00 | 06:00 | East morning — Window A |
| 12:00 | 12:00 | 09:00 | East lunch / West morning |
| 17:00 | 17:00 | 14:00 | East end-of-day — Window B |
| 20:00 | 20:00 | 17:00 | Evening engagement |
---
Daily Task Schedule
Task 1: Morning Scan
When: 30 minutes before Window A Duration: 15 min (automated) + 15 min (manual review)
Automated actions: 1. Fetch trending topics in your niche keywords 2. Scan core circle accounts for recent high-engagement posts 3. Check overnight mentions, replies, and DMs 4. Generate "Morning Briefing" report
Keywords to monitor (configure per account):
- Your product name
- Your industry terms (e.g., "AI Agent", "developer tools")
- Competitor names
- Trending hashtags in your space
Report format:
Morning Briefing — [Date]
Trending Topics:
- [Topic 1]: [Brief context]
- [Topic 2]: [Brief context]
Core Circle Activity:
- @account posted about [topic] — engagement opportunity
- @account's tweet getting traction — reply candidate
Overnight Mentions:
- [List of mentions requiring response]
Suggested Actions:
1. Reply to @account's post about [topic]
2. Post about [trending topic] — draft angle: [suggestion]
3. Respond to mention from @accountTask 2: Posting Reminder — Window A
When: Start of Window A Duration: 5 min reminder
Actions: 1. Remind to post (or confirm scheduled post went live) 2. Provide content recommendation based on:
- Today's content calendar theme
- Morning scan results
- Content mix ratio compliance
Content recommendation format:
Window A Posting Reminder
Today's Theme: [from content calendar]
Recommended Angle: [specific suggestion]
Content Pillar: [which pillar this serves]
Product Integration: [Tier 1/2/3 recommendation]
Content Mix Status (this week):
- Value: [actual]% / [target]%
- Opinion: [actual]% / [target]%
- Story: [actual]% / [target]%
- Engagement: [actual]% / [target]%Task 3: Midday Content Collection
When: Between Window A and Window B Duration: 15 min (automated)
Automated actions: 1. Scan for new trending topics since morning 2. Check performance of Window A post (early metrics) 3. Identify engagement opportunities (new posts from core circle) 4. Update content recommendations for Window B
Task 4: Posting Reminder — Window B
When: Start of Window B Duration: 5 min reminder
Same format as Task 2, updated with midday scan results.
Task 5: Engagement Follow-up
When: 30 minutes after Window B Duration: 15 min (automated analysis)
Actions: 1. Collect metrics for today's posts 2. Identify high-quality replies worth responding to 3. Check for quote tweet opportunities 4. Generate engagement recommendations
Engagement criteria:
- Replies from accounts in your core circle (always respond)
- Thoughtful replies that add value (respond with depth)
- Questions about your domain (reply with expertise)
- Mentions by larger accounts (respond promptly)
Task 6: Mentions Check
When: 1 hour after Window B Duration: 10 min (automated)
Actions: 1. Check all mentions since last scan 2. Categorize: needs reply, acknowledge, skip 3. Flag high-priority mentions (from target accounts, investors, media) 4. Generate mention report
Task 7: Evening Review
When: End of day (your timezone) Duration: 10 min (automated) + 10 min (manual reflection)
Automated actions: 1. Collect final metrics for all posts today 2. Compare against daily targets from goals config 3. Calculate content mix compliance 4. Generate daily performance summary
Manual actions (using daily review template): 1. Record what worked and what didn't 2. Identify one thing to try differently tomorrow 3. Draft tomorrow's content ideas 4. Update evolution state if any significant learnings
---
Weekly Tasks
Sunday Evening: Weekly Performance Review
When: Sunday evening (your timezone) Duration: 30 min (automated analysis) + 15 min (manual review)
Automated actions: 1. Run full analytics for the week 2. Calculate week-over-week trends 3. Identify top 3 and bottom 3 performing posts 4. Generate content mix analysis 5. Produce competitor activity summary
Manual actions (using weekly review template): 1. Review automated report 2. Decide next week's A/B test 3. Adjust content calendar if needed 4. Update watchlist and core circle
---
Monthly Tasks
End of Month: Monthly Strategy Review
When: Last day of month Duration: 30 min (automated) + 30 min (manual)
Actions: 1. Run full monthly analytics 2. Compare against monthly targets from goals config 3. Run competitor analysis framework 4. Update strategy parameters in evolution state 5. Refresh content calendar themes 6. Profile audit (bio, pinned tweet, header)
---
Task Dependencies
Morning Scan
↓
Window A Posting Reminder (uses scan results)
↓
Midday Content Collection
↓
Window B Posting Reminder (uses midday scan)
↓
Engagement Follow-up (uses today's post data)
↓
Mentions Check
↓
Evening Review (uses all day's data)---
Error Handling
If API Fails
1. Retry with exponential backoff (3 attempts max) 2. Log error in validation report 3. Report failure to user with clear error description 4. NEVER proceed with fabricated data
If Data Anomaly Detected
1. Flag immediately in report 2. Cross-check with alternative sources 3. Exclude suspicious data from analysis 4. Alert user to investigate
If Cron Job Missed
1. Run the missed task as soon as possible 2. Adjust subsequent tasks if they depend on the missed one 3. Note the gap in daily review 4. Check if the miss was a system issue or a configuration problem
---
Validation Principles (Non-Negotiable)
These principles apply to ALL automated tasks:
1. NEVER fabricate data — If API fails, report failure honestly 2. Mark missing data as null — Never substitute 0 or estimates 3. Cross-validate — When possible, verify data from multiple sources 4. Flag anomalies — Don't silently ignore suspicious data 5. Log everything — All task executions and their outcomes should be traceable
---
Cron Schedule v1.0
Engagement Playbook
Systematic community building, relationship development, and growth through genuine interaction.
---
The Engagement Funnel
Every person on X exists somewhere on this spectrum relative to you. Your engagement strategy should move people down the funnel:
Stranger → Sees your content (impression)
↓
Lurker → Reads regularly but doesn't follow (dwell time)
↓
Follower → Follows, occasionally likes (passive engagement)
↓
Fan → Regularly engages, replies, bookmarks (active engagement)
↓
Advocate → Quotes, retweets, recommends you to others (amplification)
↓
Customer/Partner → Uses your product, invests, collaborates (conversion)Different content types move people through different stages:
- Value content (technical, tutorials) moves strangers → lurkers → followers
- Personality content (humor, stories) moves followers → fans
- Engagement content (questions, conversations) moves fans → advocates
- Product content (demos, launches) moves advocates → customers
---
Core Circle Strategy
The highest-leverage engagement tactic: identify and nurture 20-30 key accounts in your space.
Building Your Core Circle
Configure in watchlist. Include:
Tier 1 — Daily Engagement (5-10 accounts)
- Accounts with 2-10x your follower count in your niche
- Active posters who reply to comments
- People whose audience overlaps with your target audience
- Goal: build genuine reciprocal engagement
Tier 2 — Regular Engagement (10-15 accounts)
- Thought leaders in your space
- Peer founders/builders at a similar stage
- Industry analysts or media accounts
- Goal: become a recognized name in their reply sections
Tier 3 — Opportunistic Engagement (5-10 accounts)
- Investors active in your space
- Potential customers or partners
- Very large accounts where a great reply can get massive reach
- Goal: strategic visibility when the opportunity is right
Engagement Cadence
| Tier | Frequency | Time Investment |
|---|---|---|
| Tier 1 | Daily | 15 min/day |
| Tier 2 | 3-4x per week | 10 min/day |
| Tier 3 | When opportunity arises | 5 min/day |
---
Reply Strategy
Replies are the most powerful engagement tool. They have the highest algorithm weight, build relationships fastest, and expose you to new audiences.
Reply Quality Framework
From best to worst:
| Level | Type | Example | Impact |
|---|---|---|---|
| S | Data/Evidence | "This matches what we've seen — our data shows [specific number]" | Very high |
| A | Novel Perspective | "What if we think about this differently: [new angle]" | High |
| B | Personal Story | "I experienced exactly this when [brief relevant story]" | High |
| C | Thoughtful Question | "Curious about [specific aspect] — have you tested [alternative]?" | Medium |
| D | Agreement + Extension | "This is spot on. I'd add that [new related point]" | Medium |
| F | Empty Agreement | "So true!" / "Great point!" / "This 🔥" | Zero/Negative |
Rules:
- Never post Level F replies. They waste the opportunity and make you look like a bot.
- Aim for Level A-B on Tier 1 accounts (where you want relationship depth)
- Level C-D is fine for Tier 2-3 (maintain visibility without massive time investment)
- Respond within 30 minutes of the original post when possible (early replies get more visibility)
Replying to Your Own Posts
When people reply to YOUR content:
- Reply to every comment in the first hour (signals active conversation to the algorithm)
- Be selective after the first hour (respond to quality comments, questions, and disagreements)
- Add new information in replies (makes the thread more valuable)
- Ask follow-up questions (keeps the conversation going)
- Never be defensive about disagreements — engage with curiosity
---
Quote Tweet Strategy
Quote tweets let you amplify others' content while adding your own perspective. Use them strategically:
When to quote tweet:
- You have a genuine, value-adding perspective on someone else's post
- You want to signal-boost a smaller account's great content
- You're reacting to industry news with analysis
- You want to start a conversation branching from someone else's idea
When NOT to quote tweet:
- Just to agree (use a reply instead)
- To attack or mock (creates negative signals)
- To self-promote without adding value
Template:
[Your unique take on the quoted content]
[Why you agree/disagree, with reasoning or evidence]
[Optional: what this means for your space]---
DM Strategy
Direct messages build the deepest relationships on X. Use them intentionally, not spammily.
When to DM
- After 3+ meaningful public interactions with someone
- When someone shows genuine interest in your work
- When you have something specific and valuable to offer them
- When they explicitly invite DMs ("DM me if...")
- When a public conversation would benefit from going private
DM Anti-Patterns
- Cold DMs pitching your product (spam)
- Generic messages ("Hey, love your content!")
- Sending DMs before any public interaction history
- Asking for favors before building any relationship
- Copy-paste messages sent to multiple people
DM Templates
After good public exchanges:
Hey [name] — enjoyed our exchange on [topic]. I'm working on [brief, relevant context]. Would love to stay connected and swap notes on [shared interest].
Offering genuine value:
[Name] — saw you're dealing with [specific challenge they mentioned]. We ran into the same thing and found [solution]. Happy to share details if useful.
Networking for collaboration:
[Name] — been following your work on [specific topic]. I'm building [Product] which touches on similar themes. Would be great to compare notes sometime.
---
X Spaces Strategy
X Spaces (live audio) build deeper relationships than text ever can.
As a Host
- Frequency: Start with bi-weekly, move to weekly as audience grows
- Format: 30-60 min focused discussion on a specific topic
- Guests: Invite 2-3 speakers from your core circle or industry
- Promotion: Announce 2-3 days in advance, remind 1 hour before
- Repurpose: Record and turn into thread summaries, clips, or blog posts
As a Participant
- Join Spaces hosted by accounts in your core circle
- Request to speak when you have a genuine contribution
- Use the chat feature to add value even if not speaking
- Follow up with speakers/hosts via DM after the Space
Spaces Topics That Work
- Industry trends and predictions
- Technical deep-dives (e.g., "How we built X")
- Founder roundtables (shared challenges)
- Q&A sessions on your domain expertise
- Hot take debates (respectful disagreement)
---
X Communities Strategy
X Communities are topic-specific groups that can dramatically expand your reach.
Finding Communities
- Search for communities in your niche (X's community discovery)
- Check which communities thought leaders in your space are active in
- Look for communities with 1K-100K members (big enough for reach, small enough for visibility)
Community Engagement Rules
- Provide value first: Post helpful content, answer questions, share resources
- Follow community norms: Each community has its own culture and rules
- Don't cross-post everything: Curate what you share in communities
- Engage with other community posts: Don't just broadcast
- Moderate self-promotion: Communities penalize or ban promotional accounts
---
X Lists for Intelligence
Create private X Lists to organize your monitoring and engagement:
| List Name | Purpose | Check Frequency |
|---|---|---|
| Core Circle | Daily engagement targets | Daily, first thing |
| Competitors | Content strategy intelligence | 2-3x per week |
| Industry Leaders | Trend awareness, reply opportunities | Daily |
| Investors | Fundraising-relevant signals | 2-3x per week |
| Potential Customers | Pain points, buying signals | Weekly |
| Media/Press | Breaking news, PR opportunities | Daily |
Using Lists Effectively
- Check your "Core Circle" list before your main feed (more focused engagement)
- Set notifications for key accounts (never miss their posts)
- Review "Competitors" list during weekly review for strategy insights
- Use lists to avoid the noise of the main algorithm feed
---
Engagement Metrics to Track
Relationship Quality Metrics
| Metric | What It Measures | How to Track |
|---|---|---|
| Reply rate to your posts | Content quality + community engagement | X Analytics |
| Reply-back rate from core circle | Relationship depth | Manual observation |
| DM conversations initiated | Networking effectiveness | Count weekly |
| X Spaces participations | Community involvement | Count weekly |
| Mentions by others | Organic advocacy | X Search alerts |
| Quote tweets of your content | Content worth amplifying | X Analytics |
Health Signals
- Healthy: Increasing replies, more substantive conversations, DM relationships forming
- Stagnant: Likes without replies, same people always engaging, no new connections
- Declining: Fewer impressions, lower engagement rates, unfollows increasing
---
Engagement Playbook v1.0
Growth Benchmarks
Industry benchmarks and realistic expectations for X account growth. Use these to calibrate your goals and assess progress.
---
Engagement Rate Benchmarks
By Account Size
| Follower Count | Good ER | Great ER | Exceptional ER |
|---|---|---|---|
| 0-500 | 2% | 5% | 10%+ |
| 500-1K | 1.5% | 3% | 7%+ |
| 1K-5K | 1% | 2.5% | 5%+ |
| 5K-10K | 0.8% | 2% | 4%+ |
| 10K-50K | 0.5% | 1.5% | 3%+ |
| 50K-100K | 0.3% | 1% | 2%+ |
| 100K+ | 0.2% | 0.7% | 1.5%+ |
Note: Engagement rate naturally decreases as accounts grow because larger accounts have a higher percentage of inactive or low-engagement followers. A declining ER with growing follower count is normal and expected.
By Content Type
| Content Type | Typical ER | Notes |
|---|---|---|
| Threads (educational) | 2-5% | Highest for accounts under 10K |
| Hot takes / contrarian | 1.5-4% | High reply rate, sometimes polarizing |
| Technical insights | 1-3% | High bookmark rate |
| Build-in-public updates | 1-3% | Strong from loyal followers |
| Questions / polls | 2-4% | High reply rate by design |
| Product announcements | 0.5-2% | Lower unless very engaged audience |
| Generic commentary | 0.2-0.5% | Avoid this content type |
---
Follower Growth Benchmarks
Monthly Growth Rate by Stage
| Stage | Followers | Realistic Monthly Growth | Accelerated Growth |
|---|---|---|---|
| Cold Start | 0-100 | 20-50 new followers | 50-100 |
| Early | 100-500 | 30-80 | 80-200 |
| Building | 500-1K | 50-150 | 150-500 |
| Growth | 1K-5K | 100-500 | 500-2K |
| Scaling | 5K-10K | 200-800 | 800-3K |
| Established | 10K-50K | 500-2K | 2K-10K |
Key insight: Growth is non-linear. The first 1,000 followers are the hardest. After 1K, network effects and algorithm signals start compounding.
Growth Catalysts
Events that typically cause step-function follower growth:
- Viral thread (single thread can add 1K-10K followers)
- Engagement from a very large account (reply, retweet, or quote tweet)
- Industry event or news where you provide timely, valuable commentary
- Product launch that gets organic coverage
- X Spaces with notable guests
- Being featured in a newsletter or podcast
---
Content Performance Benchmarks
Impressions per Post (by follower count)
| Follower Count | Low | Average | High |
|---|---|---|---|
| 0-500 | 20-50 | 50-200 | 200-1K |
| 500-1K | 50-200 | 200-500 | 500-5K |
| 1K-5K | 200-500 | 500-2K | 2K-20K |
| 5K-10K | 500-2K | 2K-5K | 5K-50K |
| 10K-50K | 1K-5K | 5K-20K | 20K-200K |
Thread Impressions (by follower count)
Threads typically get 3-10x the impressions of single tweets:
| Follower Count | Average Thread | Great Thread | Viral Thread |
|---|---|---|---|
| 0-1K | 500-2K | 2K-10K | 10K-100K |
| 1K-10K | 2K-20K | 20K-100K | 100K-1M |
| 10K-50K | 10K-50K | 50K-500K | 500K-5M |
---
Business Conversion Benchmarks
X Activity → Business Outcomes
These are rough benchmarks. Actual results vary widely by industry, product, and audience:
| Metric | Typical Range | Notes |
|---|---|---|
| Profile visit → Follow rate | 10-30% | With optimized profile |
| Follower → Bio link click (ever) | 5-15% | Over lifetime of following |
| Bio link click → Signup/Subscribe | 10-30% | Depends on landing page |
| X follower → Paying customer | 0.1-1% | Over 6+ months |
| X mention → Inbound inquiry | Variable | Higher for B2B/services |
Founder-Specific Benchmarks
| Goal | X Signals That Indicate Progress |
|---|---|
| Brand awareness | Increasing impressions, mentions, profile visits |
| Lead generation | Bio link clicks, DM inquiries, "how did you hear about us" = X |
| Fundraising | Engagement from investor accounts, DMs from investors, meeting requests |
| Hiring | Applications mentioning your X content, DMs from candidates |
| Thought leadership | Quoted by others, invited to Spaces/podcasts, media mentions |
---
Timeline Expectations
From Zero to Traction
Realistic timelines (with consistent daily effort):
| Milestone | Timeline | Required Effort |
|---|---|---|
| First 100 followers | 2-4 weeks | Daily posting + replies |
| First 500 followers | 1-3 months | Consistent posting + engagement |
| First 1,000 followers | 2-5 months | Content strategy + core circle |
| First viral thread | 1-6 months | Weekly threads + iteration |
| First inbound lead from X | 1-3 months | Product integration + value content |
| Recognized in your niche | 3-6 months | Consistent voice + quality content |
| First 5,000 followers | 6-12 months | Full operations + thread strategy |
Important: These assume consistent, daily effort with strategic content. Posting sporadically or without strategy will take significantly longer.
---
How to Use These Benchmarks
1. Set goals: Use the benchmarks for your follower count range to set realistic targets in goals config 2. Diagnose problems: If you're consistently below "Low" benchmarks, something fundamental needs to change (content quality, timing, niche focus) 3. Calibrate expectations: Don't compare your 500-follower account to a 50K-follower account 4. Track progress: Weekly comparison against benchmarks shows if you're improving 5. Celebrate wins: If you're hitting "Great" or "Exceptional" benchmarks, your strategy is working
---
Growth Benchmarks v1.0
Operations Methodology
The core operating system for X account operations. Built on a Plan-Do-Check-Act (PDCA) closed loop that runs at daily, weekly, monthly, and quarterly cadences.
---
Philosophy
X operations is not "post and hope." It is a disciplined system where every action generates data, every data point informs the next action, and the strategy continuously evolves based on empirical results.
Plan → Do → Check → Act → (repeat, but smarter)The goal is to find YOUR optimal operating formula — the specific combination of content types, posting times, engagement tactics, and voice that maximizes results for your unique account, audience, and objectives.
---
Daily Loop
Morning Phase: Plan + Warm Up (30-45 min)
1. Scan & Collect (15 min)
- Check overnight activity: mentions, replies, DMs
- Scan core circle watchlist for engagement opportunities
- Review trending topics in your niche (X search, industry feeds)
- Check competitor accounts for content inspiration
- Note any breaking news or hot topics relevant to your space
2. Plan Today's Content (10 min)
- Select today's content theme from content calendar
- Choose 2-3 tweet ideas (mix of value, opinion, story, or engagement — see content strategy)
- If thread day: finalize thread draft (should be prepared day before)
- Identify 1-2 product integration opportunities (see product integration)
- Check if any scheduled posts need adjustment based on breaking news
3. Warm Up the Algorithm (15-20 min)
- Reply to 10-15 accounts from your core circle (2-10x your follower count)
- Focus on accounts that posted in the last 30-60 minutes (early replies get more visibility)
- Every reply must add value: data, a different perspective, a genuine question, or a personal story
- This is not optional — it directly impacts the reach of your subsequent posts
Execution Phase: Create + Post + Engage (throughout the day)
4. Post Content (2-3 posts spaced 2-3 hours apart)
- Post at your configured optimal windows (see cron schedule)
- Stay active for 30-60 minutes after each post
- Reply to every comment in the first hour
- No external links in main tweet body (links go in first reply)
5. Active Engagement (15-20 min, 2-3 times during the day)
- Check for new mentions and reply to high-quality ones
- Engage with your core circle's new posts
- Look for real-time opportunities (trending topics, viral discussions)
- Post in relevant X Communities (2-3x per week)
Evening Phase: Check + Reflect (15-20 min)
6. Daily Performance Check
- Collect metrics for today's posts (impressions, engagement rate, replies, bookmarks)
- Compare against your baseline metrics from goals
- Note which content type performed best/worst today
- Record any anomalies or surprises
7. Quick Reflection (5 min) Use the daily review template:
- What worked today? (content, timing, engagement)
- What didn't work? Why?
- One thing to try differently tomorrow
- Any insight worth saving to evolution state
8. Plan Tomorrow
- Draft tomorrow's content (especially if tomorrow is a thread day)
- Identify tomorrow's engagement targets from watchlist
- Queue any scheduled posts
---
Weekly Loop (Sunday evening, ~45 min)
Use the weekly review template:
1. Performance Analysis (20 min)
- Run analytics for the week (use
scripts/analytics_reporter.py) - Calculate: total tweets, total impressions, avg engagement rate, best/worst performing
- Compare week-over-week trends
- Identify top 3 and bottom 3 tweets — analyze WHY each performed as it did
2. Content Audit (10 min)
- Review content mix ratio: were you hitting 40% value / 25% opinion / 25% story / 10% engagement?
- Track which content pillars are overrepresented or underrepresented
- Assess thread performance (if any posted this week)
- Check product integration frequency — too much? too little?
3. Engagement Review (10 min)
- Review core circle engagement — did you reply to enough accounts? Quality of replies?
- Check relationship development — any accounts moving from cold to warm?
- Review DM conversations — any new connections worth nurturing?
- Community engagement — participation in X Communities and Spaces
4. Next Week Planning (5 min)
- Set next week's content calendar (adjust themes based on learnings)
- Identify any scheduled events, launches, or trending topics to capitalize on
- Set one specific A/B test for next week (see A/B Testing section below)
- Update watchlist if needed (add/remove accounts)
---
Monthly Loop (end of month, ~1 hour)
Use the monthly review template:
1. Goal Progress Evaluation
- Compare current metrics against monthly targets from goals config
- Calculate: follower growth %, engagement rate trend, impressions trend
- Assess business metrics: website referrals, leads, mentions by target accounts
- Decide: on track, ahead, or behind?
2. Strategy Assessment
- Which content pillars drove the most growth this month?
- Which posting times consistently performed best?
- Which engagement tactics produced the strongest relationship signals?
- Is your persona/voice resonating? (check reply quality and tone of incoming engagement)
3. Competitor Check
- Run competitor analysis framework (see competitor framework)
- Note any strategy shifts from benchmark accounts
- Identify new tactics worth testing
4. Strategy Adjustments
- Adjust content mix ratios based on performance data
- Refine posting schedule if data shows better windows
- Update goals if significantly ahead or behind
- Add new A/B tests for next month
5. Evolution State Update
- Update
.evolution/strategy-state.jsonwith current best-performing parameters - Document key learnings in
.evolution/reflections.json - Update profile (bio, pinned tweet, header) if positioning has evolved
---
Quarterly Loop (end of quarter, ~2 hours)
1. Major Strategy Review
- Review 3-month growth trajectory against original goals
- Assess whether primary objective is still correct (brand vs. leads vs. fundraising)
- Evaluate if target audience definition needs refinement
- Compare your account growth rate against industry benchmarks (see growth benchmarks)
2. Persona Evolution
- Has your voice naturally evolved? Does the profile still match?
- Are there new personality anchors or running themes that emerged?
- Update
config/profile.jsonwith evolved voice and persona attributes
3. Goal Reset
- Set new quarterly goals based on current trajectory
- Adjust growth stage if you've crossed a threshold (e.g., early -> growth)
- Recalibrate KPI targets
4. Skill Update
- Document any new tactics or frameworks discovered
- Update reference documents with new learnings
- Archive outdated strategies
---
A/B Testing Protocol
Systematic testing is the engine of continuous improvement. Run one test per week.
Test Design
- Variable: Change ONE thing at a time (posting time, content format, hook style, CTA approach)
- Control: Keep everything else the same
- Sample size: Test for at least 5-7 posts before drawing conclusions
- Metric: Define the success metric before starting (engagement rate, reply count, impressions)
Test Categories
| Category | Example Tests |
|---|---|
| Timing | Morning vs. evening posts for same content type |
| Format | Text-only vs. text+image for same insight |
| Hook style | Question hook vs. bold claim vs. story hook |
| Thread length | 5-tweet vs. 10-tweet threads |
| CTA approach | Soft CTA vs. direct CTA vs. no CTA |
| Content pillar | Technical depth vs. builder's journey for same topic |
| Product mention | Subtle background vs. contextual reference |
Results Tracking
After each test cycle: 1. Record results in weekly review 2. If significant: adopt the winning variant as new default 3. If inconclusive: extend the test or note as neutral 4. Update evolution state with confirmed learnings
---
Posting Frequency by Growth Stage
Research-backed guidelines (adjust based on your capacity and A/B test results):
| Growth Stage | Daily Tweets | Daily Replies | Weekly Threads | Space between Posts |
|---|---|---|---|---|
| Early (0-1K) | 3-5 | 10-15 | 1 | 2-3 hours |
| Growth (1K-10K) | 5-10 | 15-20 | 1-2 | 2-3 hours |
| Established (10K-50K) | 10-15 | 20-30 | 2 | 1-2 hours |
| Authority (50K+) | 5-10 | 10-15 | 1-2 | 2-3 hours |
Note: Authority accounts can post less because each post has massive organic reach. Early accounts need more volume to find what works and build relationship signals.
---
Content Mix Ratios
Target ratio (adjust based on A/B testing):
| Content Type | Target % | Purpose |
|---|---|---|
| Value tweets | 40% | Tips, insights, how-tos, tutorials — builds authority |
| Opinion tweets | 25% | Contrarian takes, hot takes, predictions — builds thought leadership |
| Story tweets | 25% | Personal experiences, build-in-public, lessons — builds connection |
| Engagement tweets | 10% | Questions, polls, "which do you prefer?" — builds community |
Promotional content cap: No more than 20% of total posts should be directly promotional (Tier 3 in product integration). Product mentions through Tier 1 (background) and Tier 2 (contextual) don't count toward this cap.
---
Methodology v1.0
Multimodal Content Guide
How to use images, video, diagrams, and other visual elements to make your X content more engaging, more memorable, and more human.
---
Why Multimodal Matters
- Native video gets ~10x more distribution than text-only posts
- Tweets with images receive 2-3x more engagement than text-only
- Visual content increases dwell time (a key algorithm signal)
- Multimodal posts feel more like a real person sharing, less like a bot or corporate account
- The "活人感" (human feel) is largely created through visual authenticity
---
Visual Types and When to Use Each
1. Screenshots
When: Showing real results, product demos, data, code output, conversations.
Why it works: Screenshots are inherently authentic. They prove you're not making things up. They're the visual equivalent of "show, don't tell."
Best practices:
- Crop to show only the relevant portion (no full desktop screenshots)
- Use device frames for product screenshots (makes them look polished)
- Annotate with arrows or highlights when drawing attention to specific areas
- Ensure text is readable on mobile (zoom in if needed)
- Dark mode screenshots perform well in tech audiences
Types of screenshots:
- Terminal output showing a cool result
- Product UI demonstrating a feature
- Dashboard metrics showing growth/progress
- Code snippets in an editor with syntax highlighting
- Chat/conversation screenshots (with permission)
- Error messages with your fix (educational)
2. Diagrams and Architecture Drawings
When: Explaining systems, workflows, mental models, comparisons.
Why it works: Complex ideas become instantly accessible. Diagrams get bookmarked (high algorithm value). They demonstrate deep understanding.
Best practices:
- Keep diagrams simple — 5-7 elements maximum
- Use clean, high-contrast colors (readable on both light and dark backgrounds)
- Include a brief text explanation alongside the diagram
- Hand-drawn style diagrams often feel more authentic than polished corporate diagrams
- Use tools: Excalidraw (hand-drawn style), Mermaid (code-generated), tldraw, Figma
Diagram types:
- Architecture diagrams (how things connect)
- Flow charts (how things work step by step)
- Comparison matrices (A vs B)
- Mental model visualizations
- Before/after illustrations
3. Code Snippets
When: Sharing technical insights, tutorials, debugging stories.
Why it works: Developers and technical audiences love scannable code. It's immediately actionable and bookmark-worthy.
Best practices:
- Use a code screenshot tool (Carbon, Ray.so, Snappify) for beautiful formatting
- Keep snippets short (10-20 lines max per image)
- Use syntax highlighting appropriate to the language
- Include brief context text above the code image
- For longer code: break into multiple images (one per concept)
4. Memes and Humor Images
When: Adding personality to industry commentary, celebrating/commiserating shared experiences, reacting to news.
Why it works: Memes are the lingua franca of X. They show you're part of the community, not above it. They're highly shareable.
Best practices:
- Use well-known meme templates that your audience will recognize
- The humor should come from the tech insight, not just the meme format
- Self-deprecating > mocking others
- Don't force it — if the humor isn't natural, skip the meme
- Create memes using: imgflip, Figma, or simple image editors
- Original memes (your own photos/screenshots turned into memes) feel more authentic
Anti-patterns:
- Overusing memes (dilutes your authority)
- Memes that punch down or mock specific people
- Corporate/forced humor that feels inauthentic
- Memes that only work if you explain them
5. Data Visualizations
When: Sharing research, trends, comparisons, build-in-public metrics.
Why it works: Data visualizations stop the scroll because they pack dense information into a glanceable format. They position you as someone who does rigorous analysis.
Best practices:
- Clean, minimal charts (no chartjunk)
- Clear labels and a title that states the insight, not just the topic
- Highlight the key data point or trend
- Use contrasting colors for the most important data
- Source your data (adds credibility)
6. Video and GIF
When: Product demos, quick tutorials, reactions, explainers.
Why it works: Native video gets the highest distribution from the algorithm. Short-form video (30-90 seconds) is particularly effective.
Video types:
- Screen recording with voiceover (product demo, tutorial)
- Talking head (personal takes, reactions — highest authenticity)
- Animated explainer (architecture, workflows)
- Short clips from X Spaces or podcasts
Best practices:
- Hook in the first 3 seconds (autoplay means no time to waste)
- Add captions/subtitles (most people watch without sound)
- Keep under 2 minutes for highest completion rate
- Native upload only (external links are penalized)
- Vertical or square format for mobile viewing
GIF usage:
- Reaction GIFs in replies add personality
- Short screen recordings as GIFs for quick product demos
- Use sparingly in original posts (they don't get the same algorithm boost as video)
---
Multimodal Strategy by Content Pillar
| Content Pillar | Primary Visual | Secondary Visual |
|---|---|---|
| Technical Depth | Code screenshots, diagrams | Screen recordings, data viz |
| Industry Pulse | Data visualizations, comparison diagrams | Memes, reaction images |
| Builder's Journey | Dashboard screenshots, product screenshots | Selfie/workspace photos, memes |
| Community Value | Resource screenshots, comparison tables | Polls (built-in X feature) |
| Personal Touch | Personal photos, memes | GIFs, hand-drawn sketches |
---
The "活人感" (Human Feel) Checklist
Before posting any multimodal content, check:
- [ ] Does this feel like a real person made it, or does it look AI-generated / stock-photo / corporate?
- [ ] Would I send this in a group chat with friends? (if yes, the vibe is right)
- [ ] Is there any imperfection that makes it feel authentic? (perfect is suspicious)
- [ ] Does the visual add genuine value, or is it decoration?
- [ ] Is the tone consistent with my voice? (see persona guide)
Authenticity Signals
- Slightly imperfect screenshots (real workspace, real data)
- Hand-drawn or sketch-style diagrams
- Photos from your actual workspace or life
- Screenshots with your actual browser/editor/terminal
- Memes that reference your specific experience
Red Flags (feels fake/corporate)
- Stock photos
- Over-designed graphics with gradients and drop shadows
- AI-generated images used as "real" content (obvious to most audiences)
- Perfectly polished everything (no human would be this consistent)
- Generic visuals that could belong to any account
---
Thread Visual Strategy
Threads with images in each tweet get significantly more engagement. Plan visuals for each thread position:
| Tweet Position | Visual Strategy |
|---|---|
| Hook (Tweet 1) | Eye-catching image that creates curiosity: before/after, surprising data, or a compelling screenshot |
| Body (Tweets 2-N) | One relevant visual per tweet: diagram, code, screenshot, or data supporting that tweet's point |
| CTA (Final Tweet) | Summary image, your product screenshot, or a visual bookmark reminder |
Not every thread tweet needs an image, but aim for visuals in at least 60-70% of thread tweets.
---
Tools Recommended
| Purpose | Tools |
|---|---|
| Code screenshots | Carbon (carbon.now.sh), Ray.so, Snappify |
| Diagrams | Excalidraw, tldraw, Mermaid, Figma |
| Memes | imgflip, Figma, Canva |
| Data visualization | Observable, Datawrapper, simple charting libraries |
| Screen recording | CleanShot X (macOS), OBS, Loom |
| Image editing | Figma, Canva, Preview (macOS) |
| Video editing | CapCut, Descript, iMovie |
---
Multimodal Guide v1.0
Persona & Voice Guide
How to develop, maintain, and evolve an authentic online persona that feels human, builds recognition, and serves your goals.
---
Why Persona Matters
People don't follow accounts. They follow people. Your persona is the answer to "Why should I pay attention to this person specifically?" in a sea of similar content.
A well-defined persona:
- Makes your content instantly recognizable (even before reading your name)
- Builds trust through consistency (people know what to expect)
- Creates emotional connection (people relate to people, not brands)
- Differentiates you from others sharing similar insights
---
Persona Discovery Framework
Answer these questions to define your authentic persona. The key word is authentic — your persona should be a focused version of who you really are, not a character you play.
Identity Questions
1. What do you know deeply that most people don't? (Your unique expertise) 2. What are you building and why does it matter to you personally? (Your mission) 3. What's your origin story? (How you got here — the human version, not the LinkedIn version) 4. What opinions do you hold that are unpopular in your space? (Your contrarian edges) 5. What are you genuinely passionate about outside of work? (Your dimensionality)
Voice Questions
6. How do you talk to smart friends about your work? (Your natural register) 7. What makes you laugh in your industry? (Your humor style) 8. How do you handle disagreement? (Your conflict style) 9. What are you comfortable being vulnerable about? (Your authenticity boundaries) 10. What would you NEVER post about? (Your red lines)
Record your answers in profile config under the voice section.
---
Voice Attributes Matrix
Rate yourself on each dimension (these become your voice guardrails):
| Attribute | Spectrum | Your Setting |
|---|---|---|
| Technical Depth | Surface ←→ Deep | e.g., "High — I explain the 'why' behind technical decisions" |
| Humor | Serious ←→ Playful | e.g., "Moderate — self-deprecating, occasional tech memes" |
| Formality | Casual ←→ Formal | e.g., "Casual-professional — like speaking at a conference afterparty" |
| Vulnerability | Guarded ←→ Open | e.g., "Moderate — share failures and struggles, keep personal life private" |
| Boldness | Cautious ←→ Provocative | e.g., "High — willing to take contrarian positions with reasoning" |
| Warmth | Distant ←→ Approachable | e.g., "Approachable — reply to everyone, use inclusive language" |
Voice Consistency Rules
Once you define your attributes, maintain them:
Always do:
- Use your natural speaking rhythm (short sentences if that's how you talk, long if that's your style)
- Maintain consistent humor level (don't suddenly become funny if you're normally serious)
- Keep technical depth consistent (don't dumb down or suddenly become academic)
- React to news/events in your characteristic way
Never do:
- Switch between radically different tones (confuses followers and algorithm)
- Use language that doesn't sound like you (corporate-speak if you're casual, slang if you're formal)
- Pretend to know things you don't (authenticity is the foundation)
- Copy someone else's voice (your audience will notice, and it won't feel natural)
---
Language Mix Strategy
For bilingual or multilingual operators:
When to Use English
- Technical content targeting international audiences
- Industry commentary and predictions
- Engaging with English-speaking thought leaders
- Thread hooks (English reaches wider audience on X)
When to Use Native Language
- Personal reflections and emotional content (feels more authentic)
- Content targeting your home market
- Cultural references and humor that don't translate
- Community-specific discussions
Mixing Within Posts
- Code-switching (mixing languages naturally) can be a persona differentiator
- Use it intentionally: English for technical terms, native language for emotional emphasis
- Some accounts build recognition through their specific language mix pattern
- Ensure the mix feels natural, not forced
---
Personality Anchors
Personality anchors are recurring elements that build recognition. They're the equivalent of a signature style.
Types of Anchors
Recurring themes: Topics you always come back to
- "The discovery problem in AI" (always analyzing through this lens)
- "Founder survival tactics" (always grounding advice in survival reality)
Catchphrases or frameworks: Distinctive language you coin
- A specific metaphor you use repeatedly
- A framework name you've created
- A way of phrasing things that's distinctively yours
Running jokes: Self-aware humor that loyal followers get
- A recurring complaint about a specific technology
- A running joke about your build process
- A meme format you've made your own
Format signatures: Consistent structural choices
- Always starting threads with a specific format
- A particular emoji usage pattern
- A consistent sign-off style
Building Anchors
- Don't manufacture anchors — notice what naturally recurs in your content
- When something gets positive response, lean into it
- Reference your own previous content occasionally ("As I keep saying...")
- Let anchors evolve naturally — forcing them feels fake
---
Adaptation Rules
Your core persona stays constant, but tone adapts to context:
| Context | Adaptation |
|---|---|
| Technical thread | Deeper, more precise language; less humor |
| Industry hot take | More assertive, bolder claims; personality through conviction |
| Build-in-public update | More vulnerable, honest about difficulties |
| Reply to thought leader | Slightly more formal, ensure value-add is clear |
| Community question | Warmer, more inclusive, teaching mode |
| Product launch | More energetic, but still authentically you (not marketing-speak) |
| Handling criticism | Calm, curious, open to being wrong — never defensive |
---
The "活人感" (Human Feel) Checklist
Before posting, check:
- [ ] Would I say this out loud to a smart friend? (if yes, the voice is right)
- [ ] Does this sound like ME specifically, or could any account in my space have posted this?
- [ ] Is there any personality in this post? (insight alone isn't enough — add the human layer)
- [ ] Am I being authentic, or performing? (audiences can tell the difference)
- [ ] Would I be embarrassed by this in 5 years? (authenticity ≠ recklessness)
Signals That Your Persona Is Working
- People reply with personality (not just "great point" but genuine reactions)
- Followers reference your specific ideas/frameworks/jokes
- New followers say "I've been reading your stuff for a while" (recognition)
- People describe you in specific terms ("the person who always talks about X in a Y way")
- You get invited to Spaces, podcasts, and conversations because of your perspective
Signals That Something's Off
- Engagement feels hollow (likes but no replies or conversations)
- You feel exhausted maintaining your online presence (you're performing, not being yourself)
- Followers are confused by inconsistent tone
- You're getting engagement but from the wrong audience
- You feel unable to share certain genuine thoughts (voice too constrained)
---
Persona Evolution
Your persona should evolve as you grow. Schedule quarterly persona reviews:
1. Re-read your voice attributes: Do they still match how you naturally communicate? 2. Check your anchors: Which ones still resonate? Any new ones emerging? 3. Assess audience alignment: Is your persona attracting the right people? 4. Update profile: Does your bio, photo, and pinned tweet reflect who you are now? 5. Update config: Refresh config/profile.json with any evolved attributes
Evolution should be gradual, not sudden. Sharp persona pivots confuse your audience and disrupt algorithm relationship signals.
---
Persona & Voice Guide v1.0
Product Integration Framework
How to "夹带私货" (weave in product promotion) naturally and effectively. The ultimate goal of X operations for founders is to build an audience that knows, trusts, and eventually uses/buys/invests in what you're building.
---
Philosophy
The worst product promotion on X feels like advertising. The best feels like a smart person sharing what they're building as part of a broader conversation.
Core principle: If you removed the product mention, the tweet should still be valuable. The product is the proof, not the point.
---
Three Tiers of Integration
Tier 1: Background Presence (Target: 30% of posts)
The product exists in your world but isn't the subject of the post.
How it works: Your bio, profile, and pinned tweet do the work. When people engage with your valuable content and click your profile, they see what you're building. No explicit mention needed in the tweet itself.
Examples:
- Post a technical insight about your domain — people who click your profile discover your product
- Share an industry hot take — your bio says "Building [Product] to solve this"
- Reply to a thought leader with deep expertise — your profile provides the context
When to use: Most of the time. This is your default mode.
Tier 2: Contextual Reference (Target: 50% of promotional posts)
The product is mentioned as an example, proof point, or natural part of a broader insight.
How it works: You're discussing a real problem, trend, or insight, and your product naturally comes up as relevant context. The post would still be valuable without the mention, but the mention adds specificity and credibility.
Examples:
"The discovery problem for AI Agents is underrated.
When we built [Product], we found that agents fail not because
they can't execute — but because they don't know what tools are
available.
This is the same problem search engines solved for humans.
Agents need their own search layer.""Spent the last week benchmarking [approach A] vs [approach B]
for tool routing.
Results surprised me: [specific finding].
This is why we went with [approach] in [Product] —
the performance difference at scale is 3x."Template:
[Broader insight about your domain]
[Specific evidence from building your product]
[Generalized lesson that applies beyond your product]When to use: When you have genuine insights from building. Never force a product mention into content that doesn't naturally call for it.
Tier 3: Direct Promotion (Target: 20% of promotional posts)
The product is the subject of the post. Launch announcements, feature releases, milestones, demos.
How it works: Unambiguous promotion, but still packaged with value, personality, or story.
Examples:
"[Product] v2.0 is live.
What's new:
→ [Feature 1]: [why it matters]
→ [Feature 2]: [why it matters]
→ [Feature 3]: [why it matters]
Built because [specific user need or story behind the feature].
Try it: [link in first reply]""6 months ago I quit my job to build [Product].
Month 1: 0 users, pure prototype
Month 3: 50 users, first paying customer
Month 6: [milestone]
Here's what I'd do differently if I started over:
[Thread with genuine lessons]"When to use: Product launches, major milestones, funding announcements, significant traction updates. Max 1-2 direct promotional posts per week.
---
Overall Promotional Ratio
Your total content mix should follow this pattern:
Total Posts: 100%
├── Non-promotional (Tier 1 + pure value): ~80%
├── Contextual mentions (Tier 2): ~10%
└── Direct promotion (Tier 3): ~10%When in doubt, err toward less promotion. Trust is built slowly and lost quickly.
---
Product-Content Alignment Matrix
Map your product's features and values to content that naturally references them:
| Product Aspect | Content Angle | Integration Tier |
|---|---|---|
| Core problem you solve | Industry analysis of the problem | Tier 2 |
| Technical architecture | Deep-dive on your approach vs alternatives | Tier 2 |
| User stories/feedback | Sharing user wins (with permission) | Tier 2-3 |
| New feature launch | Launch thread with context and demo | Tier 3 |
| Milestone (users, revenue, funding) | Build-in-public celebration with lessons | Tier 3 |
| Team/hiring | Culture posts, "why we hired for X" | Tier 2-3 |
| Competitive landscape | Thoughtful analysis (respectful, not attacks) | Tier 1-2 |
| Vision/mission | Founder reflection on why this matters | Tier 2 |
---
CTA (Call-to-Action) Optimization
CTA Types by Strength
| CTA Type | Conversion | Audience Friction | When to Use |
|---|---|---|---|
| "Follow for more [topic]" | Low per action, high LTV | Very low | End of value threads |
| "Bookmark this" | Medium (signals quality) | Very low | Resource/list content |
| "What's your experience?" | High engagement | Low | Discussion prompts |
| "Check out what we built" | Medium-high | Medium | Tier 2 contextual |
| "Try it free: [link in reply]" | High | Medium-high | Tier 3 launches |
| "DM me for early access" | Very high quality | High | Beta/early stage |
| "Sign up: [link]" | Direct conversion | High | Only for established trust |
CTA Best Practices
- Never put links in the main tweet — always "link in reply" (algorithm penalty for links)
- Soft CTAs work better on X than hard sells ("Check this out" > "Sign up now")
- Match CTA to relationship stage: new followers get "follow for more," engaged followers get "try it"
- One CTA per post maximum. Multiple CTAs dilute each other
- The best CTA is no CTA — genuinely valuable content promotes itself
---
Timing Product Integration with Business Events
Launch Playbook (1-2 week cycle)
| Timing | Content | Tier |
|---|---|---|
| 2 weeks before | Tease the problem you're solving | Tier 2 |
| 1 week before | Behind-the-scenes build process | Tier 2 |
| 3 days before | "Something big coming" + genuine excitement | Tier 2-3 |
| Launch day | Launch thread with demo + story + CTA | Tier 3 |
| Day 2 | User reactions, early feedback | Tier 2-3 |
| Day 3-7 | Specific use cases, deep-dives on features | Tier 2 |
| Ongoing | Lessons learned from the launch | Tier 1-2 |
Fundraising Playbook
- Increase Tier 2 content showing traction, market insights, technical depth
- Post about the problem space (not "we're fundraising")
- Share industry predictions that demonstrate domain expertise
- Engage with target investor accounts through value-add replies
- After close: celebrate milestone with genuine story (Tier 3)
Hiring Playbook
- Post about your team culture and engineering challenges (Tier 2)
- Share technical problems you're working on (attracts talent)
- "We're hiring" posts with context on why this role matters (Tier 3)
- Engage with potential candidates' technical posts
---
Anti-Patterns
Things that make product promotion feel spammy:
| Anti-Pattern | Why It Fails |
|---|---|
| Every tweet mentions your product | Feels like a corporate account, people unfollow |
| Product link in main tweet body | Algorithm penalty + feels salesy |
| "We're excited to announce..." language | Corporate voice, zero personality |
| Only posting about your product | No value for followers who aren't already customers |
| Attacking competitors to promote yourself | Looks insecure, generates backlash |
| Fake urgency ("limited spots!") | Erodes trust, especially among tech-savvy audiences |
| Ignoring engagement to post more promos | Algorithm deprioritizes one-directional accounts |
---
Measuring Product Integration Effectiveness
Track these metrics to assess whether your integration is working:
| Metric | Source | What It Tells You |
|---|---|---|
| Profile visits after value posts | X Analytics | Are people curious about you? |
| Bio link clicks | X Analytics / UTM | Are visitors converting to your property? |
| "How did you hear about us?" = X | Signup survey | Direct attribution |
| Mentions of your product by others | X Search | Organic word-of-mouth |
| DMs asking about your product | X DMs | High-intent interest |
| Investor/partner inquiries from X | DMs/Email | Business development signal |
---
Product Integration Framework v1.0
Profile Optimization Guide
Your profile is the conversion page for every new visitor. Optimize it before investing in content strategy.
---
Why Profile Matters
When someone sees your tweet in their feed and considers following you, they visit your profile. The decision to follow happens in 3-5 seconds based on:
1. Profile photo — "Is this a real person I want to hear from?" 2. Bio — "What value will I get from following?" 3. Pinned tweet — "Is their content actually good?" 4. Recent tweets — "Are they consistently posting quality content?"
A well-optimized profile can double your follow rate from profile visits.
---
Profile Photo
Use a real face photo. Avatars, logos, and illustrations significantly reduce follow rates.
Guidelines:
- Clear, well-lit headshot with neutral or simple background
- Natural, approachable expression (not overly formal corporate shots)
- Consistent across platforms for recognition
- Professional but human — you're a person, not a brand
- Update periodically (every 1-2 years) to stay current
---
Display Name
- Use your real name (builds trust, especially for founders)
- Optional: add a brief descriptor or emoji that reinforces your niche
- Keep it recognizable — don't change frequently
Examples:
Jane Smith(clean, professional)Jane Smith | Building ProductX(adds context)- Avoid:
Jane | AI Guru | 10x Developer | Speaker | Author(cluttered)
---
Bio Formula
The bio needs to answer three questions in 160 characters: 1. Who are you? (role + credibility) 2. What do followers get? (value proposition) 3. Why should I care? (proof or hook)
Formula: [Identity/Role] | [What you share/build] | [Proof or personality hook]
Examples by role:
Founder:
Building [ProductName] — [what it does]. Previously [credential]. Sharing the raw founder journey + [your domain] insights.
Indie Developer:
Solo building [ProductName]. Sharing real numbers, code, and lessons. [Credential or notable metric].
Tech Professional:
[Role] at [Company]. Writing about [2-3 specific topics]. Formerly [credential].
Bio Anti-Patterns
- Vague labels: "Entrepreneur | Visionary | Dreamer"
- Too many roles: "CEO | Advisor | Speaker | Author | Investor | Dad"
- Cliches: "Thought leader", "Passionate about", "Serial entrepreneur"
- No value proposition: listing who you are without saying what followers get
---
Header Image
The header banner is underused real estate. Use it to reinforce your positioning:
- Option A: One clear sentence about your mission + product screenshot
- Option B: Key credential or achievement + your domain topic
- Option C: Product/project visual with tagline
- Keep it clean and readable on mobile (most X traffic is mobile)
---
Bio Link
Your bio link is the primary traffic driver from X to your properties.
Priority order (pick the highest-value destination): 1. Newsletter signup — highest conversion and lifetime value from X audience 2. Lead magnet / free resource — builds email list while providing value 3. Product landing page — direct conversion path 4. Link aggregator (Linktree, etc.) — only if you genuinely need multiple links
Update your bio link to match current campaigns or launches.
---
Pinned Tweet Strategy
Your pinned tweet is your permanent first impression. It should be your highest-converting piece of content.
What to Pin
Rotate every 2-4 weeks based on your current priority:
| Priority | Pin This |
|---|---|
| Growing followers | Your best-performing thread (most engagement/bookmarks) |
| Building authority | Your deepest technical insight or contrarian take |
| Launching product | Product announcement with demo/screenshot |
| Building email list | Free resource or newsletter pitch |
| Just getting started | Introduction thread: who you are, what you're building, what you'll share |
Pinned Tweet Format
The ideal pinned tweet:
- Hooks immediately (first line must stop the scroll)
- Delivers clear value or tells a compelling story
- Includes a call to action (follow for more, check out, sign up)
- Has strong engagement metrics (social proof for new visitors)
Rotation Schedule
- Check pinned tweet performance weekly
- Rotate when you have something that outperforms the current pin
- Always pin around launches, announcements, or milestone moments
- After a viral tweet, consider pinning it while momentum is high
---
Profile Audit Checklist
Run this checklist monthly:
- [ ] Profile photo is a clear, current headshot
- [ ] Display name is clean and recognizable
- [ ] Bio clearly states who you are + what followers get
- [ ] Bio includes proof/credential (not just claims)
- [ ] Header image reinforces positioning
- [ ] Bio link points to highest-priority destination
- [ ] Pinned tweet is current and high-performing
- [ ] Recent tweets (top 5) represent the quality you want to convey
- [ ] No broken links in bio or pinned tweet
---
Profile Optimization Guide v1.0
Thread Playbook
Threads are the single highest-leverage growth mechanism on X. A well-crafted thread can generate 5,000-10,000 new followers and 100,000+ impressions, compared to 0-2 followers from a typical single tweet.
---
Thread Architecture
Every high-performing thread follows this structure:
Tweet 1: HOOK (stop the scroll, create curiosity)
↓
Tweet 2: CONTEXT (set the stage, establish credibility)
↓
Tweets 3-N: VALUE DELIVERY (the meat — one point per tweet)
↓
Tweet N+1: SUMMARY (key takeaway, tie it together)
↓
Final Tweet: CTA (what you want the reader to do next)Optimal Thread Length
| Length | Best For | Performance |
|---|---|---|
| 3-5 tweets | Quick insights, reactions | Good engagement, lower viral potential |
| 5-7 tweets | Tutorials, analyses | Best balance of engagement and completion rate |
| 8-12 tweets | Deep-dives, comprehensive guides | Highest viral potential, lower completion rate |
| 12+ tweets | Only for exceptional content | Risk of drop-off; use sparingly |
The sweet spot for most founders is 5-7 tweets. Long enough to deliver substantial value, short enough to maintain attention.
---
Hook Formulas
The hook (Tweet 1) determines 90% of your thread's performance. If it doesn't stop the scroll, nothing else matters.
Proven Hook Types
1. Bold Claim
[Specific, surprising claim that challenges conventional wisdom]
Here's why → 🧵Example: "90% of AI startups are solving the wrong problem. Here's what they're missing →"
2. Specific Number
I [did/analyzed/spent] [specific number] [thing].
Here's what I learned → 🧵Example: "I analyzed 500 viral tech tweets. Here are the 7 patterns they all share →"
3. Contrarian Take
Unpopular opinion: [contrarian statement]
Before you disagree, hear me out → 🧵Example: "Unpopular opinion: You don't need more followers. You need better followers."
4. Personal Story
[Specific, relatable scenario with tension]
Here's what happened → 🧵Example: "Last month our main server went down during a demo with our biggest potential customer. What I did next saved the deal."
5. Curiosity Gap
[Intriguing question or statement that creates information gap]
The answer surprised me → 🧵Example: "Why do some founders with 500 followers close more deals from X than others with 50K?"
6. List Tease
[N] [valuable things] that [benefit]:
↓ 🧵Example: "7 developer tools I use daily that most people haven't heard of:"
7. Before/After
6 months ago: [painful state]
Today: [improved state]
Here's exactly what changed → 🧵Hook Anti-Patterns
- Starting with "Thread:" or "🧵" without a hook (no one will read further)
- Vague promises ("Great stuff coming up...")
- Too much context in the hook (save it for tweet 2)
- Hooks that over-promise and under-deliver (erodes trust)
---
Body Tweet Guidelines
Each body tweet (tweets 2 through N) should:
1. Make one clear point — Don't cram multiple ideas into one tweet 2. Be standalone-worthy — Each tweet should make sense even if read in isolation 3. Include a visual when possible — Images increase dwell time and engagement (see multimodal guide) 4. Use formatting for scanability — Line breaks, bullet points, numbered lists 5. Build on the previous tweet — Create a narrative flow that compels reading the next one
Transition Techniques
Between tweets, use connective phrases:
- "But here's what most people miss:"
- "The second pattern is even more interesting:"
- "Now, this is where it gets counterintuitive:"
- "The data confirms this:"
- Use numbered points for list threads (makes position clear)
Body Tweet Templates
For tutorial/how-to threads:
Step [N]: [Clear action]
[Brief explanation of what to do and why]
[Screenshot or code snippet]For analysis/insight threads:
[Finding/Pattern N]:
[What the data/evidence shows]
[Why this matters / what it means]
[Optional: supporting image]For story threads:
[Next event in the narrative]
[Key detail or dialogue that makes it vivid]
[Brief reflection or lesson from this moment]---
CTA (Final Tweet)
The final tweet converts engagement into lasting value. Options:
For follower growth:
If you found this useful:
1. Follow me @[handle] for more [topic]
2. Retweet the first tweet to help others find this
3. Bookmark the thread for reference
I write about [topic] every [frequency].For product awareness:
This is exactly the problem we're solving at [Product].
[Brief product context — one sentence]
[Link in reply if they want to check it out]
Follow for more [topic] insights.For email list:
I share deeper analysis like this in my weekly newsletter.
[Brief value proposition — what subscribers get]
Link to subscribe → [in first reply to this tweet]For engagement:
What's your experience with [thread topic]?
Drop your thoughts below — I'll reply to everyone.---
Thread Scheduling
Best Times to Post Threads
- 08:00-10:00 in target audience timezone — morning focus time, people are browsing
- Tuesday through Thursday — highest professional engagement days
- Avoid weekends for professional threads (lower reach, save for lighter content)
Preparation Timeline
| When | Action |
|---|---|
| 2-3 days before | Draft full thread, identify visuals needed |
| Day before | Revise, prepare images, finalize |
| Morning of | Final review, post during optimal window |
| Post 30 min | Reply to every comment, retweet the hook |
| 24 hours later | Share key insight from thread as standalone tweet with link to thread |
---
Thread Types
1. Tutorial Thread
Goal: Teach something specific and actionable Structure: Hook → Steps → Summary → CTA Example topic: "How to set up [X] in 10 minutes" Typical length: 7-10 tweets
2. Analysis Thread
Goal: Provide unique insight or breakdown Structure: Hook → Findings → Implications → CTA Example topic: "I analyzed [N] [things]. Here's what the data shows." Typical length: 5-8 tweets
3. Story Thread
Goal: Share a compelling narrative with a lesson Structure: Hook → Setup → Conflict → Resolution → Lesson → CTA Example topic: "How we almost lost our biggest customer (and what I learned)" Typical length: 5-7 tweets
4. Resource Thread
Goal: Curate valuable resources for your audience Structure: Hook → Resources (one per tweet) → Summary → CTA Example topic: "10 tools every [role] should know about" Typical length: 8-12 tweets
5. Contrarian Thread
Goal: Challenge popular thinking with evidence Structure: Hook (contrarian claim) → Evidence → Reframing → What to do instead → CTA Example topic: "Why [popular approach] is actually hurting your [outcome]" Typical length: 5-7 tweets
6. Build-in-Public Thread
Goal: Share your journey with transparency Structure: Hook (milestone/turning point) → Context → What happened → Metrics → Lessons → CTA Example topic: "Month 6 of building [Product]: from 0 to [metric]" Typical length: 5-8 tweets
---
Thread Metrics
Track these to optimize future threads:
| Metric | What It Tells You |
|---|---|
| Impressions (first tweet) | Hook effectiveness |
| Engagement rate (first tweet) | Overall hook + topic appeal |
| Completion rate (last tweet impressions / first tweet impressions) | Thread quality |
| Bookmark count | Save-worthy value |
| Reply count | Conversation-worthy content |
| New followers (day of posting vs average) | Thread's growth impact |
| Quote tweets | Content worth amplifying |
Benchmarks (for 1K-10K follower accounts):
- Good thread: 20K+ impressions, 50+ engagements
- Great thread: 50K+ impressions, 200+ engagements
- Viral thread: 100K+ impressions, 500+ engagements, 100+ new followers
---
Thread Repurposing
Extract maximum value from every thread:
| Source | Repurpose Into | Timing |
|---|---|---|
| Full thread | 5-7 standalone tweets (one per body tweet, rephrased) | Over the following week |
| Thread hook | Standalone tweet with different hook format | 2-3 weeks later |
| Full thread | Blog post or newsletter edition | Within 1 week |
| Thread insights | Replies to related discussions | Ongoing |
| Full thread | X Space topic | Next scheduled Space |
| Thread topic | Follow-up thread (deeper dive or part 2) | 2-4 weeks later |
---
Thread Playbook v1.0
Daily Review — [Date]
Today's Posts
| # | Content Summary | Pillar | Tier | Posted At | Impressions | ER | Likes | Replies | Bookmarks |
|---|---|---|---|---|---|---|---|---|---|
| 1 | |||||||||
| 2 | |||||||||
| 3 |
Engagement Activity
- Replies sent to core circle: __ / target: __
- Replies received on my posts: __
- New followers today: __
- DM conversations: __
- Community posts: __
What Worked
-
What Didn't Work
-
One Thing to Try Differently Tomorrow
-
Content Mix Compliance (This Week Running Total)
| Type | Actual | Target | Status |
|---|---|---|---|
| Value | __% | 40% | |
| Opinion | __% | 25% | |
| Story | __% | 25% | |
| Engagement | __% | 10% |
Tomorrow's Plan
- Content idea 1:
- Content idea 2:
- Key engagement targets:
- Thread prep needed: Yes / No
Notes / Insights Worth Saving
-
Monthly Review — [Month Year]
Goal Progress
| KPI | Start of Month | End of Month | Target | Status |
|---|---|---|---|---|
| Followers | ||||
| Avg engagement rate | ||||
| Avg impressions/tweet | ||||
| Weekly threads | ||||
| Key relationships built | ||||
| Bio link clicks | ||||
| Business leads from X |
Month-over-Month Trends
| Metric | Last Month | This Month | Change |
|---|---|---|---|
| Total impressions | |||
| Total engagement | |||
| Follower growth | |||
| Best single tweet ER | |||
| Thread performance avg |
Content Strategy Assessment
What Worked Best This Month
1. 2. 3.
What Consistently Underperformed
1. 2.
Content Pillar Performance
| Pillar | Posts | Avg ER | Avg Impressions | Verdict |
|---|---|---|---|---|
| Technical Depth | ||||
| Industry Pulse | ||||
| Builder's Journey | ||||
| Community Value |
Product Integration Assessment
- Tier 1 (background) posts: __
- Tier 2 (contextual) posts: __
- Tier 3 (direct) posts: __
- Measurable business impact:
- Adjustment needed:
Engagement & Relationship Assessment
- Core circle engagement consistency:
- New meaningful relationships this month:
- DM → real conversation conversions:
- X Spaces hosted/participated:
- Community engagement:
Competitor Insights (from monthly analysis)
- Key tactic observed:
- Gap identified:
- Tactic to test:
Persona Check
- Is my voice still authentic?
- Am I attracting the right audience?
- Any persona drift to correct?
- Profile updates needed:
Next Month Strategy
Goals
-
Content Mix Adjustments
-
Engagement Focus Shift
-
A/B Tests Planned
1. 2.
Product Integration Plan
-
Key Learnings to Save
-
Performance Report — [Period]
Data Quality
- Tweets analyzed: __
- Data completeness: __% (tweets with full metrics)
- Validation status: PASS / PARTIAL / FAIL
- Anomalies detected: __
Summary Metrics
| Metric | Value | Benchmark | vs Benchmark |
|---|---|---|---|
| Total tweets | |||
| Total impressions | |||
| Average impressions/tweet | |||
| Engagement rate | |||
| Average likes/tweet | |||
| Average replies/tweet | |||
| Average bookmarks/tweet | |||
| Follower change |
Engagement Breakdown
| Type | Total | Per Tweet Avg | % of Total Engagement |
|---|---|---|---|
| Likes | |||
| Replies | |||
| Retweets | |||
| Quote Tweets | |||
| Bookmarks |
Content Type Performance
| Content Type | Count | Avg Impressions | Avg ER | Best Performer |
|---|---|---|---|---|
| Value | ||||
| Opinion | ||||
| Story | ||||
| Engagement | ||||
| Thread |
Posting Time Analysis
| Time Window | Posts | Avg Impressions | Avg ER | Verdict |
|---|---|---|---|---|
| Window A | ||||
| Window B | ||||
| Off-window |
Top Performers
| Rank | Tweet (summary) | Impressions | ER | Key Factor |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |
Underperformers
| Rank | Tweet (summary) | Impressions | ER | Likely Cause |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |
Recommendations
Based on this data: 1. 2. 3.
---
Generated by x-founder-operations analytics. All metrics validated through the data integrity workflow.