The Skill Writes the Thread. It Can't Tell You It's Worth Writing.

This is the X version of a pack I already wrote up for LinkedIn. Same builder, same MIT license, same shape: it drafts, it audits, it hands the result back to you, and nothing posts until you approve it. If you live in Claude Code and post on X, it is worth ten minutes.

01. Why this exists

drafting is the cheap part now

The builder's line, repeated across every pack in this family: "writing collapsed to the price of a chat subscription." A tweet is the easiest thing an AI can produce. So the value sits in the work around the tweet.

For X that means knowing what your niche posted this week, keeping a list of the accounts worth replying to, and catching a weak draft before it goes out with your name on it. That is what these skills try to turn into a routine.

The skill writes the thread. It cannot tell you the thread is worth writing.

02. What you actually get

one install, no coding

The skills load into Claude Code or Codex and trigger when you ask for something X-shaped. You never call them by name.

03. Install it

a plugin marketplace, no coding

It ships as a plugin. Add the marketplace, install the pack, and the skills are live in your next session.

# Claude Code (CLI, Desktop, Web, IDEs)
/plugin marketplace add sergebulaev/x-skills
/plugin install x-skills@x-skills

# Codex CLI
codex plugin marketplace add sergebulaev/x-skills
codex plugin add x-skills@x-skills

# any other agent
npx skills add sergebulaev/x-skills

Nothing else is required. The optional keys in section 6 only matter if you want it to publish for you or generate images.

04. The loop: draft, audit, approve

the approve step is the job

The flow is always the same. You describe the tweet or thread you want. Post Writer or Thread Builder drafts it. Humanizer scores it and flags the lines that read as generated. Then it stops and shows you the result. Nothing posts until you say so.

Paste without reading and you post like everyone else running the same tool. The gate is where your judgment goes in.

05. The skills that carry it

the rest are useful, these are the reason to install

Thread Builder is the one that separates this from a generic prompt. It treats a thread as a structured object: a hook post, then value posts in order, then a close. Ask a chat model for "a thread about X" and you get eight tweets in a row. This asks what each post is doing.

Hook Extractor is the compounding one. Feed it a tweet that did well and it hands you back the structure with the specifics stripped out. Do that for a month and you have your own file of hooks that already work in your niche.

Reply Drafter matters more on X than anywhere else, because replies are how accounts actually grow here. Give it a tweet URL and it drafts a reply or a quote tweet in your voice, so showing up in other people's threads stops being a willpower problem.

06. The optional paid add-ons

the pack is free, these extend it

The core is free forever. Three integrations extend it and you only add the ones you need. Keys go in a .env file.

You can run the whole thing with zero keys and paste each approved draft into X yourself.

07. The completely free setup

run it with zero paid keys

Every skill in this pack works without Publora, Pixfaro or Apify. With no keys it drops to manual mode: it still drafts and audits, then hands you text to paste yourself instead of publishing. A few prompts make that mode smooth, and you can wire in free automation on top if you want it.

For X, the data scraper is vladkens/twscrape. It rotates through X accounts you add by cookie, so add one or two burner accounts, not your main.

Right after install, paste this into Claude Code in the plugin's folder to turn on free mode:

I will not use Publora, Pixfaro or Apify. Read every SKILL.md and the files
in lib/ (apify_client.py, publora_client.py, pixfaro_client.py). Make all
skills work with zero paid keys: publishing outputs a clean copy-paste
block, images print the prompt and then accept a local file path, data
fetch asks me to paste the content when no scraper is set up. Do not change
any function names or return shapes. Add FREE_MODE=1 to .env.example. Show
me a summary of every change.

That alone is a working free setup. The rest is optional polish, each a one-paragraph prompt to Claude Code: swap the Apify calls in lib/apify_client.py for the scraper above, keeping the return shape and putting the new code in lib/free_scrapers.py so one import flips it back; rewrite lib/publora_client.py to post with Playwright from your saved browser session and stop before the final click unless you pass auto=True; make lib/pixfaro_client.py take a local image path instead of calling the API.

Day to day: the skill drafts and humanizes, then you paste the post yourself or let the Playwright step do it. Need an image, the skill prints a prompt, you make it elsewhere and give back the path. Audience Insights runs off the local data source.

08. The thread is the point

why this pack is built around threads, not tweets

A single tweet does not need a tool. You can write one in the time it takes to open a chat window. The reason this pack exists is the thread, and the reply habit that feeds it.

Thread Builder forces a shape on the draft, Repurposer turns your longer work on other platforms into native threads instead of link dumps, and Reply Drafter keeps you active in other people's threads. Those three are the actual workflow. The rest is support.

09. The catch, in plain words

read this before you install

A skill pack does not give you taste. It drafts a hook in your voice, but it cannot judge whether the idea under it is worth posting. That judgment stays with you, and the approve step is where you apply it.

Your voice needs feeding too. Give the skills three or four of your own real tweets to work from, not a one-line description, or the output slides back to default X.

And note that Publora publishes on your behalf. Read what it does before you paste a key, the same as any integration.

10. Who should use it

the honest verdict

Use it if you already work in Claude Code or Codex and you post on X, or keep meaning to. It removes the blank-editor problem and gives you a structured thread builder and a reply habit for free.

Skip it if you do not use an agent day to day. Installing a plugin marketplace to write one tweet a week is more setup than it is worth.

There is a version of this for every other platform too. All of them, with source links, are on the social media skills hub.

The pack is on GitHub, it is MIT, and it takes ten minutes to try. Worst case, nothing changes. Best case, threads stop being the thing you keep putting off.