agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/coordinate-launch/SKILL.md

coordinate-launch

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 “Coordinate Launch”. A useful skill states the six fields from Skills and routines. A dated launch needs one group lead who assigns researcher, writer, and reviewer, tracks blockers, and never publishes. Each role has one owner. No publish, tag, or customer-facing send happened. The packet says who still owes what. Launch board: Outcome, Date, Assignments, Blockers, Go/no-go questions, Action log. Do…

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:

    Stop at a go/no-go packet for the human.

    line 25
  2. Distinctive:

    Do not publish release notes, tag a release, merge to main, or send the launch post.

    line 39

≈ “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

Coordinate Launch

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Coordinate Launch”.

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

1. When to use it

A dated launch needs one group lead who assigns researcher, writer, and reviewer, tracks blockers, and never publishes.

2. Required inputs and access

  • Launch outcome, date, and audience
  • Named researcher, writer, and reviewer Bots (or people)
  • Source of truth for "done" (checklist, PR, or doc)

3. Sequence of work

  1. Restate the launch outcome, date, and what "shipped" means. If the date is missing, ask and stop.
  2. Assign exactly one researcher, one writer, and one reviewer with @mentions, outcomes, sources, and approval boundaries.
  3. Track blockers in a single list. Do not do their jobs.
  4. Stop at a go/no-go packet for the human. Do not publish, tag, or send the announcement.

4. How to validate the result

Each role has one owner. No publish, tag, or customer-facing send happened. The packet says who still owes what.

5. What to return

Launch board: Outcome, Date, Assignments, Blockers, Go/no-go questions, Action log.

6. What requires approval

Do not publish release notes, tag a release, merge to main, or send the launch post. The human issues the ship verdict.

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