agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/remix-content/SKILL.md

remix-content

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 “Remix Content”. A useful skill states the six fields from Skills and routines. One source draft must become review-ready social and email variants that stay unpublished. Every variant is labeled DRAFT. Every claim traces to the source. Nothing was posted, scheduled, or mailed. Remix pack with source claims, per-channel DRAFT variants, character counts, and an action log. Do not publish or…

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:

    Read the source. If it is missing, ask and stop.

    line 22
  2. Distinctive:

    Write one variant per named channel, inside that channel's limits.

    line 24
  3. Distinctive:

    Every variant is labeled DRAFT.

    line 30
  4. Distinctive:

    Do not publish or schedule.

    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

Remix Content

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Remix Content”.

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

1. When to use it

One source draft must become review-ready social and email variants that stay unpublished.

2. Required inputs and access

  • Source draft (Notion, chat, or attached file)
  • Brand voice examples if the owner attached them
  • Named channels (default X, LinkedIn, email, short page)

3. Sequence of work

  1. Read the source. If it is missing, ask and stop.
  2. Extract claims. Do not add statistics the source does not contain.
  3. Write one variant per named channel, inside that channel's limits.
  4. Map each variant sentence back to a source claim.
  5. Label every variant DRAFT. Do not publish, schedule, or send.

4. How to validate the result

Every variant is labeled DRAFT. Every claim traces to the source. Nothing was posted, scheduled, or mailed.

5. What to return

Remix pack with source claims, per-channel DRAFT variants, character counts, and an action log.

6. What requires approval

Do not publish or schedule. Do not post to X, LinkedIn, Slack, or a CMS. Do not send the email variant. Do not edit the live source page unless named.

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.