agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/draft-newsletter/SKILL.md

draft-newsletter

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 “Draft Newsletter”. A useful skill states the six fields from Skills and routines. A weekly issue must be collated from links and notes the owner already saved, and left unsent. Every used item has a citation. Skipped items are listed. No send, no public Doc share, no list change. Unsent issue with title, cited sections, skipped list, word count, and action…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Leave a Google Doc draft unpublished.

    line 26
  2. Distinctive:

    Every used item has a citation.

    line 30
  3. Distinctive:

    Do not send the newsletter.

    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

Draft Newsletter

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Draft Newsletter”.

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

1. When to use it

A weekly issue must be collated from links and notes the owner already saved, and left unsent.

2. Required inputs and access

  • Saved links and notes (Google Docs, a Gmail label, /workspace)
  • Prior issues for voice
  • Working title if the owner named one

3. Sequence of work

  1. Open the saved pile. If it is empty or missing, say so and stop. Do not browse the open web to pad.
  2. Drop dead links and duplicates into a skipped list.
  3. Draft sections that cite each remaining item.
  4. Match attached prior-issue voice. Keep length honest to the pile.
  5. Leave a Google Doc draft unpublished. Do not send Gmail.

4. How to validate the result

Every used item has a citation. Skipped items are listed. No send, no public Doc share, no list change.

5. What to return

Unsent issue with title, cited sections, skipped list, word count, and action log.

6. What requires approval

Do not send the newsletter. Do not schedule a send. Do not publish the Google Doc. Do not add subscribers.

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