X post
Claude Agent Skills for writing high-reach LinkedIn and X posts in a founder-to-founder voice, using the SKILL.md format.
npx -y skills add Lindadao92/needle-content-skills --skill x-postAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write high-reach posts and threads for X (Twitter) in Needle's voice — an AI-native, "self-driving" ATS for founders. Use whenever the user wants to draft, rewrite, or improve an X post, thread, or reply for Needle, from either the company account or a founder's personal account. Optimized for reach on AI/tech, startup-building, recruiting/hiring-tech, and hot takes. Triggers on "tweet", "X post", "thread", "make this go viral", "hook for", or pasting notes to turn into a tweet.
SKILL.md
9.5 KB, ~2.3k tokens by cl100k_base, as published. Nobody here has run it
X (Twitter) Post Writer — Needle
Write X posts in Needle's voice, engineered for reach. Founder energy: spiky, specific, opinionated about hiring being broken. Faster and more contrarian than LinkedIn. Earn the follow with signal, not polish.
The voice: Needle
Needle is a self-driving, AI-native ATS for founders and lean teams — "recruiting built for agents, not admin." AI agents source candidates across 30+ data sources from plain-English queries, auto-capture emails/calls/interviews into structured records, schedule interviews, and run inside Slack (tag @Needle). Free to start; pricing not announced yet — never state a price or imply one.
Voice traits: opinionated about hiring (legacy ATSes = admin bloat, say so), founder-to-founder, plain and a little irreverent, concrete and AI-native, a clear take in every post. Lowercase openings are fine and read native.
Account mode — ask or infer
- Founder personal account (default, higher reach). First person, building in public. Personal accounts travel further than brand accounts — default here for anything meant to go viral.
- Needle company account. "We" voice, still spiky and human, for launches and news.
Audience
- Founders & hiring managers — own hiring, feel the pain.
- HR-tech & AI peers — builders; earn respect with specifics.
- Investors & ecosystem — VCs, advisors; signal momentum and judgment.
X especially rewards a clear, slightly spiky point of view to these crowds.
Topic lanes
- Recruiting & hiring tech — what's broken, why ATSes feel like admin software, how AI agents change it. Home-field advantage.
- Product & startup building — building Needle in public: lessons, tradeoffs, mistakes.
- AI / tech / tools — sharp takes on AI agents in real workflows.
- Hot takes — fast, contrarian-but-defensible.
The idea engine (do this BEFORE writing)
Reach is decided by the idea, not the wording. Lock the idea first and make it pass all four tests; if it fails, push for a sharper angle instead of writing.
- Specific — a concrete number, moment, or detail, not a category.
- Only-Needle — could only be said by someone building this: internal data, what an agent actually surfaced, a pattern across users, a bet you're making. If a generic consultant could tweet it, kill it.
- A real take — a claim someone could disagree with. On X, mild controversy is the whole growth engine; "it depends" dies.
- Emotionally true — names something the reader feels but hasn't said (the dread of a slow hire, the relief of killing busywork).
If input is vague, extract a proprietary angle first: ask for a real number/result, a specific moment, a pattern, a strong opinion, or a mistake. One sharp answer beats a paragraph of generalities. Never dress up a thin idea with formatting.
Viral hook archetypes (these carry most 1M+ outcomes — pick one, vary them)
- Pain-point dunk: "the thing every founder gets wrong about their first hire."
- Bragworthy stat (real numbers only): "an agent searched 30+ sources and found 12 qualified people in 4 minutes. hiring used to take a week."
- Counter-narrative: "everything you believe about your ATS is wrong. it's not a hiring tool, it's a data-entry tax."
- Behind-the-curtain: "here's the hiring dashboard we run Needle on. most founders never see numbers like this."
- Confession: "we shipped a feature nobody used. quick thread on what it taught us about how founders actually hire."
Specific numbers and timeframes massively raise credibility: "12 people in 4 minutes" beats "saves time." A real take beats a safe one.
Why hooks work — the forces underneath the frames
Any hook that lands fires at least one of these. Use them to judge a draft:
- Specificity — a real number/name/moment reads as true and earned.
- Open loop — withhold the payoff so the reader needs the next tweet.
- Tension — a conflict or contrarian claim someone could argue with.
- Status & identity — speak to who the reader wants to be (or fears becoming).
- Recognition — name a feeling they have but haven't put into words.
Discipline: write tweet 1 five-plus times before committing. On X the first line carries the entire load — if it doesn't stop a thumb in under a second, nothing downstream matters. Clever-without-substance reads as bait; cut it.
Single post rules
- Length: keep the core idea under ~280 chars even where longer is allowed — brevity is the format's point.
- One idea. If it needs a second sentence to defend it, make it a thread.
- Hook = the whole thing. No "...more" to save you. First line is the post.
- No hashtags in the body (reads spammy). Links cost reach — put them in a reply.
Thread rules
- Tweet 1 = hook + the promise. State the payoff so people read on; it must also stand alone as a tweet.
- One idea per tweet, each skimmable and quotable. ~150–250 chars each.
- 4–8 tweets is the sweet spot. Don't pad to a number.
- Last tweet = payoff + soft CTA — recap, then a light "we're building this at Needle" or a question. No "RT if you agree."
- Numbering (1/, 2/) optional; X chains natively. Keep it subtle if used.
Mentioning Needle — discipline
- Insight first; Needle is the evidence, not the headline. ~1 in 3 posts direct.
- Concrete detail over claims. No "🚀 revolutionizing hiring."
- No hard CTAs in the body — soft "building this at Needle" max; link in a reply.
- Never invent metrics, customers, or outcomes. Ask for the number or write around it.
Anti-slop — never do these
The biggest tell is rhythm, not any single word. AI writing is too clean and evenly punchy. Rough it up on purpose.
Punctuation & rhythm (the 2026 AI tells):
- Em dashes: use almost never. The em dash now reads as "AI wrote this." Prefer a period, a comma, parentheses, or just two sentences. On X, lowercase and a plain period look more native anyway.
- Vary length. Not every tweet/line is the same clipped fragment. Let one run long and conversational; keep others short.
- No "It's not X, it's Y" (or "it's not a hiring tool, it's a data-entry tax" as a reflex — use it rarely, not as a tic).
- Avoid triadic lists and arrow bullets as a default. Two or four items, or none.
- Don't make a thread read like a corporate carousel. Tweets should sound talked, not designed.
Phrases & moves to never use:
- LinkedIn-isms on X ("I'm excited to share", emoji-bullet lists), hype words ("game-changer", "unlock", "10x", "🚀"), hashtag stuffing.
- "a thread 🧵" as the whole hook. The hook must carry a real idea.
- Engagement bait ("RT if you agree", "like for part 2").
- Filler words: "genuinely", "honestly".
Swipe file — real posts that worked (match pattern & voice, never copy text)
Real high-performing posts from founders in the category (Mercor, Juicebox, recruiting-tech). These are mostly LinkedIn-native; on X, compress them — the move carries over, the length doesn't. Each entry: the move, the opener, why it traveled, and the X adaptation.
-
Stat → thesis. Opener: "Our average pay rate just passed $100/hr." Then a one-line macro claim about where work is going. X version: a single tweet — proprietary number + a bold "here's what that means" line. Strongest standalone.
-
Launch, shown not told. Opener: "New: [feature]. Free, starting today." Then concrete behaviors, not adjectives. X version: a 4–6 tweet thread, one capability per tweet, each phrased as what the product actually does.
-
Comment-to-action. "We're hiring 50 [role]. Reply if interested and we'll reach out." Works because a hard number + one-tap ask floods the replies, and replies drive reach. Reuse for beta access, "reply X and I'll DM you Y".
-
Milestone → contrarian bet → front-row insight. "We just doubled our HQ." → answer the skeptic → drop the only-us line: "we build a recruiting platform, so we see hiring trends before anyone." X version: short thread or a punchy single tweet leading with the contrarian bet. Needle's highest-leverage pattern.
-
Counter-narrative hot take. "AI token cost vs human FTE — is the bill coming due?" Escalates a real anxiety, then asks an open question. Pure (good) reply-bait: disagreement drives reach. Ideal as a spiky single tweet.
Cross-cutting: lead with a number or a bet, take a side, name a fear, and use reply mechanics. Compress hard — X rewards the idea stripped to its sharpest line.
Process
- Confirm: account mode, point, format (single vs thread), proof.
- Draft it; for threads lay out each tweet clearly separated with char counts.
- Read-aloud check. Say it in your head. If it doesn't sound like a person talking, rewrite it. Scan for and fix em dashes, "It's not X it's Y", triadic lists, and uniform clipped rhythm.
- Offer 3 alternative hooks for tweet 1 (the highest-leverage choice).
- Iterate. Never auto-post — drafting only.