agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/queue-social/SKILL.md

queue-social

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 “Queue Social”. A useful skill states the six fields from Skills and routines. One idea must become a week's worth of posts across named channels, sitting in a review queue — none of them published. Nothing was posted, scheduled, or boosted. Each draft is original to this idea (not a pasted competitor post). Channel and day are explicit. Queue table plus…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 them into the Notion queue or a workspace file.

    line 25
  2. Distinctive:

    Do not publish, schedule, or reply on X or any network.

    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

Queue Social

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Queue Social”.

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

1. When to use it

One idea must become a week's worth of posts across named channels, sitting in a review queue — none of them published.

2. Required inputs and access

  • The idea, brief, or Notion page
  • Voice examples (attached or a Notion style page)
  • Named channels and the week to fill (default next seven days)

3. Sequence of work

  1. Restate the idea in one sentence. Reject a catch-all "post more".
  2. Pull voice examples. Match length and stance; do not invent a brand voice.
  3. Draft seven items (or the named count) with day, channel, hook, body, CTA, and asset note. Label each DRAFT.
  4. Write them into the Notion queue or a workspace file. Do not schedule on X or any network.
  5. List what still needs an image or a fact check.

4. How to validate the result

Nothing was posted, scheduled, or boosted. Each draft is original to this idea (not a pasted competitor post). Channel and day are explicit.

5. What to return

Queue table plus the Notion (or file) pointer, and a "needs asset or source" list.

6. What requires approval

Do not publish, schedule, or reply on X or any network. Do not email the list to a social tool.

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.

Check your setup, free