agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/scout-x-threads/SKILL.md

scout-x-threads

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Scout X Threads”. A useful skill states the six fields from Skills and routines. The owner wants to learn the craft of high-engagement public X threads — structure, hooks, beat timing — then write original drafts that steal the craft, not the post. No post was published. Drafts are not paraphrases of a single source thread. Engagement numbers have a fetch…

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write original draft threads in the owner's voice.

    line 25
  2. Distinctive:

    Stop. Do not post, reply, quote-post, or follow anyone.

    line 26
  3. Distinctive:

    No post was published. Drafts are not paraphrases of a single source thread.

    line 30
  4. Distinctive:

    Do not post, schedule, like, repost, or reply.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scout X Threads

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Scout X Threads”.

A useful skill states the six fields from Skills and routines.

1. When to use it

The owner wants to learn the craft of high-engagement public X threads — structure, hooks, beat timing — then write original drafts that steal the craft, not the post.

2. Required inputs and access

  • Topic or account set to study
  • X plugin (public posts only)
  • Voice examples if the owner attached them

3. Sequence of work

  1. Scope the study by topic, language, and time window. Do not log into other people's accounts.
  2. Fetch public posts/threads. Record hook, beat count, proof type, CTA, and visible engagement counts as of fetch time.
  3. Extract craft notes (what the structure does). Quote at most a short fragment; never reproduce a thread.
  4. Write original draft threads in the owner's voice. Label DRAFT. Different claims need different proof.
  5. Stop. Do not post, reply, quote-post, or follow anyone.

4. How to validate the result

No post was published. Drafts are not paraphrases of a single source thread. Engagement numbers have a fetch timestamp. Accounts studied are public.

5. What to return

Craft notes, source list with URLs, original DRAFT threads, and a "do not copy" reminder for each source.

6. What requires approval

Do not post, schedule, like, repost, or reply. Do not scrape behind a login the owner did not authorize.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.