Skill

Turn this into a thread

Turn long ideas, transcripts and drafts into Twitter/X threads with a clear sequence and tweets that each make sense alone.


69
Spark score
out of 100
Updated last month
Source checked Oct 8, 2026
Version 19.0.1

Add to Favorites

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-turn-this-into-a-thread | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

This skill develops Twitter/X threads from a clear idea and an ordered outline. Each tweet carries one point and remains readable outside the sequence. Use it for material with genuine steps, turns or distinct supporting points. Keep a single-point idea as one post.

What it does

Turn this into a thread converts a long idea, transcript, article or draft into a Twitter/X sequence whose individual tweets remain useful on their own. It first checks whether the material needs a thread, then builds an ordered outline before writing. The MIT-licensed skill aims for a genuine progression rather than an article cut into fragments or a small thought stretched across extra posts.

Each tweet carries one idea. The sequence should become stronger through its order, while a reader arriving midway can still understand and quote an individual part. The first tweet makes a specific claim and promises something concrete; the last closes that opening loop.

When to use - and when NOT to

Use it when someone explicitly wants a Twitter/X thread or needs to break substantial writing into tweets. A sequence of steps, a story with turns or several distinct points under one argument can justify the format. It is not a LinkedIn workflow.

Ask for the central idea in one sentence first. One point with one supporting detail usually needs a single post, so offer that instead. A thread should earn its length. The workflow cannot promise reach or engagement and should not add repetition merely to hit a target count.

Inputs and outputs

Begin with the material and a confirmed statement of its main idea. Show a skeleton with one line per beat, normally five to nine beats, before drafting the tweets. If seven distinct beats are unavailable, keep the thread shorter. Check whether the ordering matters: when the beats could be shuffled without loss, label the result as a list so readers know they can dip into it.

Write an opening that makes sense alone and states the actual claim rather than announcing a generic thread topic. Subsequent tweets must not depend on an opening word or fragment that only makes sense after the previous tweet. Keep one idea in each, and use at most one honest call to action at the end when it belongs there.

Separate tweets with a line containing only three dashes. The required format is:

First tweet text.

---

Second tweet text.

This layout also works for manual posting. Number the parts only when their order is genuinely instructional; a story need not read like a numbered exercise. If the material supports five tweets rather than seven, state that constraint when handing over the draft.

Integrations

An optional VoiceMoat MCP connector provides a Twitter-specific trained voice profile through get_voice_profile, separate from the LinkedIn profile. score_voice_match checks the draft against that register. improve_post accepts a thread and respects tweet boundaries during revision.

The connector requires a paid Pro or Enterprise plan and the user's OAuth sign-in, without API keys. Its tools read or send post text and account data through voicemoat.com. Without it, this skill makes no network calls.

publish_post splits on the three-dash separator and chains each part as a reply to the previous one; schedule_post queues the same structure. These actions affect real accounts. The first call returns a preview, while a second call requires a one-time code. Show the exact preview and wait for explicit approval before sending that code back. Never make both calls in a single step or confirm a publication independently.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.