agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/daily-digest/SKILL.md

daily-digest

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 “Daily Digest”. A useful skill states the six fields from Skills and routines. The owner wants a source-linked digest of what changed and what needs attention, mapped to stated priorities, not a dump of every channel. Every item has a source link or message pointer. Noise the owner previously marked is absent. No messages were sent. No meetings were changed. A…

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Every item has a source link or message pointer.

    line 29
  2. Distinctive:

    Do not send messages, change meetings, or file tickets without approval.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 11 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

Daily Digest

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Daily Digest”.

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

1. When to use it

The owner wants a source-linked digest of what changed and what needs attention, mapped to stated priorities, not a dump of every channel.

2. Required inputs and access

  • Priority document or a pinned list of current priorities
  • Approved channels (Slack, mail, calendar, notes)
  • Time window (default since yesterday in the Bot timezone)

3. Sequence of work

  1. Re-read the priority document. If it is missing, ask and stop.
  2. Scan only approved sources for the window.
  3. Drop anything that does not map to a priority.
  4. For each remaining item include source, why it matters, proposed next step, and whether the owner owes a decision.

4. How to validate the result

Every item has a source link or message pointer. Noise the owner previously marked is absent. No messages were sent. No meetings were changed.

5. What to return

A short digest plus a "Decisions needed" section. Action log of sources scanned.

6. What requires approval

Do not send messages, change meetings, or file tickets without approval.

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.