x-account-warmup
When a user wants to grow an X (Twitter) account from zero before a product launch, or asks how to get first followers, warm up the algorithm, hit ~500-1,000 followers, or prepare an account to make a launch video land. Also use when the user mentions "new X account", "warm up my Twitter", "first 1000 followers", "building in public strategy", "X growth", or "engagement before launch".
What this skill does
# X Account Warmup
An X account with fewer than ~500-1,000 followers cannot launch virally. The algorithm doesn't have enough signal to decide whether your post is worth amplifying, so even great launch videos die. This skill runs the warmup protocol before you try to launch.
**When invoking**: Ask for the user's product, ICP, current follower count, and how far they are from launch. Then produce a warmup plan.
## Threshold
| Followers | What's possible |
|---|---|
| < 500 | Account is cold. Launches will not ignite. Focus entirely on warmup. |
| 500 - 1,000 | Viable. Launch can land if content is strong. |
| 1,000+ | Healthy baseline. Proceed to launch playbook. |
Expect the warmup phase to take weeks to months of daily posting, not days. One source case took nine months before a single post broke out and added +2,000 followers.
## Four warmup levers
1. **Tag communities.** When posting on X, attach the tweet to the community that matches your ICP (e.g. "Build in Public", your vertical's dev community). Treat X communities like subreddits — the community feed shows your post to people who did not follow you yet. Find the community whose members match your ICP and post into it.
2. **Tag famous accounts.** Include an @mention of a well-known account relevant to the post (founder, investor, tool, public figure). If they retweet or reply, their followers flow into your impressions. Works best when you have a visual (screenshot, image, demo clip) to make the tag feel like a reference, not a plea.
3. **Post daily, with no shame.** Daily posting is what builds the algorithmic signal and the parasocial trust. Categories that work: research notes ("I'm reading X, here's what's interesting"), one-liner motivational posts aimed squarely at your ICP, behind-the-scenes screenshots, success moments (first check, first customer, first contract).
4. **Share proof-of-work artifacts.** GitHub repos, visualizations, benchmarks, diagrams. On X the audience is heavily developer-leaning — they'll click an open-source link out of curiosity when they won't click a marketing post.
## Content mix during warmup
| Type | Frequency | Purpose |
|---|---|---|
| Research/insight posts | Daily | Position as credible in your domain |
| Motivational one-liner aimed at ICP | 2-4x/week | Build parasocial trust with target customer |
| Success screenshots | Whenever real (first check, first customer, milestone) | Social proof + people root for you |
| Build-in-public update | 1-2x/week | Shows momentum, invites engagement |
| Competitor template remix | 1-2x/week | See `x-viral-template-miner` |
## ICP-to-channel check
Before running warmup, confirm X is even the right channel:
- **Tech / developer / AI / crypto ICP** → X is primary. Run full warmup.
- **Event marketers, HR, healthcare ops, non-tech B2B** → X is secondary. Spend at most 20% of effort here. Route the main play to LinkedIn and use `x-linkedin-content-relay` for amplification.
## Output format
When asked to generate a warmup plan, produce:
1. **Current state**: follower count, ICP, gap to launch threshold.
2. **Channel recommendation**: primary + secondary, based on ICP.
3. **Community list**: 3-5 X communities the user should post into.
4. **Tag list**: 5-10 well-known accounts worth referencing in posts (not spam — only when genuinely relevant).
5. **Daily post menu**: 7-day rotation covering the content mix above, with example first lines.
6. **Timeline estimate**: weeks-to-threshold based on starting point and posting cadence.
## Related skills
- `x-viral-template-miner` — what to post during warmup
- `x-launch-video-structure` — what to do once warmup is done
- `x-linkedin-content-relay` — parallel channel for non-tech ICPs
- `twitter-x-posts` (marketing-skills) — post copy formatting and character limits
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".