mcpField
X
x-thread-strategy

x-thread-strategy

github.com/ootto-aiMarketing & growth31162 installsUpdated 2w ago
Repository

About x-thread-strategy

x-thread-strategy is a skill for planning evidence-led X threads. It helps social and campaign teams build a clear argument, keep posts understandable on their own, and review outcomes without overstating what metrics prove.

Key features

  1. 01Select a defensible thread claim
  2. 02Structure evidence and progression
  3. 03Make each post independently legible
  4. 04Place caveats near supported claims
  5. 05Review outcomes and recurring confusion

Use cases

  1. 01Turn sourced research into an X thread
  2. 02Explain a multi-step process or comparison
  3. 03Revise future threads using reader feedback

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ootto-ai/claude-content-skills --skill x-thread-strategy

After installing, type/x-thread-strategyin Claude Code to confirm it loaded.

Details

From the project README

X Thread Strategy

Build a thread that rewards a reader for continuing: one defensible point, a clear sequence, and evidence they can evaluate.

1. Choose the thread-worthy claim

Ask for the source material, the audience's immediate question, the claim that can be defended, and what the reader should do with it. A thread needs progression: a process, comparison, analysis, or lesson with several necessary steps. If one post can carry it, do not inflate it.

2. Create the argument spine

Write the opening claim, why it matters, the sequence of evidence or steps, the limitation, and the ending action. Each post must move the reader forward; eliminate setup that merely repeats the hook. Keep links, screenshots, and examples attached to the exact claim they support.

3. Make each post independently legible

Use direct language, one idea per post, and enough context that a quote-post does not distort the point. Put caveats near the claim they qualify. If a post depends on data, name the source and date rather than implying current truth.

4. Publish with an evidence loop

Plan the first reply only when it adds a useful resource, correction policy, or data source. Track saves, qualified replies, and link outcomes appropriate to the campaign rather than treating impressions as proof. Feed recurring confusion back to social-listening or revise the next thread.

Hard rules

  • Do not invent data, quotes, experiments, screenshots, or access to a platform.
  • Never split a weak idea into a thread to simulate substance.
  • Do not promise a result the source cannot support.
  • Avoid engagement bait, pile-ons, and commentary on individuals without verifiable context.
  • Preserve disclosure and attribution for partner, customer, or sponsored material.

Failure modes

FailureDo this instead
The thread repeats its hook ten timesGive every post a distinct evidentiary or instructional job.
Context disappears in quote-postsInclude a precise claim and caveat in each standalone post.
The thread chases a fast-moving eventVerify the source and timestamp or leave it as a question, not a fact.
The ending is a forced CTAClose with the one useful next action the evidence supports.

Where it sits

Use content-research, social-listening, or campaign-brief to supply an approved source. Use cross-platform-distribution to define X's role within a wider plan. Use social-analytics-report to review outcomes and content-repurposer only after the original thread has a clear lesson worth adapting.

Comments

Markdown supported