agentleFS
belzoralolbtwbelzoralolbtw/x-agent-skill/skills/x-plan/SKILL.md

x-plan

Skill0 starsChanged 34 days agoMITView on GitHub

Build a weekly X (Twitter) content plan: what to post each day, in what format, from the account's own material, at a cadence the owner can keep. Use when the user wants a posting schedule, a content calendar, "what do I post", a 30-day plan, or help being consistent. Produces a one-week grid and a repeatable weekly routine.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Jakeschincariol/x-agent-skill★ 4same name
    2. lleqsnoom/xskills★ 2same name
    3. swayamdhawan/x-agent★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the voice profile (templates/voice.md), or infer the voice from three posts.

    line 19
  2. Distinctive:

    Ask three things in one batch: what they do, who they are talking to, and how many days a week they can honestly show up.

    line 20
  3. Distinctive:

    4. Give the routine,: not just the calendar. When in the day they write, when they post, when they reply.

    line 49
  4. Distinctive:

    All four post types collapsed into "tips".

    line 65
  5. Distinctive:

    No reply block. Without it the plan has no way to reach new people.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

x-plan

Consistency beats intensity on X, and most accounts fail at consistency not because they lack ideas but because they have no system. This skill turns what the owner already knows into a week they can actually run.

Before you write

  1. Read the voice profile (templates/voice.md), or infer the voice from three posts.
  2. Ask three things in one batch: what they do, who they are talking to, and how many days a week they can honestly show up. Build for the lower number. A plan the owner abandons in week two is worse than a small plan kept.
  3. List the raw material they already have: results, mistakes, opinions, projects, things they explain often, questions people ask them.

The week has four kinds of post

Rotate these so the feed is not all one shape. This is the whole plan.

Signals   a specific result, number, or thing that happened. Proof and story.
Stances   an opinion or a correction. Pulls replies, builds a point of view.
Lessons   one thing you know that the reader does not. Teaches, gets saved.
Replies   15-30 minutes a day replying to the accounts in the niche (x-reply).
           Not a post, but the growth engine, so it goes on the plan.

A simple week at 3 posts a week: one signal, one stance, one lesson, plus the daily reply block. At 5 posts, add a second lesson and one repurposed post.

The loop

1. Fill a one-week grid: day, post type, the specific idea, the format (single post or thread). Use the owner's own material, not generic topics. 2. Write the reply list: the 5-15 accounts to reply to, and the daily habit sized to the account (see x-reply). 3. Mark the repurposing slot: one post a week that reuses something the owner already published elsewhere (x-repurpose). 4. Give the routine, not just the calendar. When in the day they write, when they post, when they reply. The routine is what makes it survive.

Cadence guidance

1-2 a week   fine to start. Better a kept 2 than an abandoned 7.
3-5 a week   the sweet spot for most accounts under 10k.
Daily        only if the owner already has ideas queued. Daily for its own
             sake produces filler, and filler trains the audience to scroll.

Failure modes

  • A plan of "post about your niche" with no specific ideas. That is not a plan.
  • Seven posts a week for someone who posts once a month. It collapses in a week.
  • All four post types collapsed into "tips". The feed becomes monotone.
  • No reply block. Without it the plan has no way to reach new people.
  • Topics the owner cannot speak to with a real example. If there is no story or number behind it, cut it from the week.

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.