agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/triage-inbox/SKILL.md

triage-inbox

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 “Triage Inbox”. A useful skill states the six fields from Skills and routines. An inbox needs a sorted work list and draft replies so the owner can reach inbox zero without living in Gmail. No mail was sent. No archive/delete unless explicitly approved. Security-looking messages are never auto-ignored. Bucketed list with draft replies attached to needs-reply items, plus a "handle today"…

3 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 3 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:

    No mail was sent. No archive/delete unless explicitly approved.

    line 29
  2. Distinctive:

    Do not send, delete, or unsubscribe without approval.

    line 39

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

Triage Inbox

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Triage Inbox”.

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

1. When to use it

An inbox needs a sorted work list and draft replies so the owner can reach inbox zero without living in Gmail.

2. Required inputs and access

  • Gmail (or named mailbox) connector
  • VIP list and ignore list if the owner saved them
  • Time window (default since last run)

3. Sequence of work

  1. Fetch messages in the window. Do not mark read unless asked.
  2. Bucket into needs reply, fyi, newsletter, receipt, or ignore.
  3. Draft replies only for needs-reply, in the owner's voice if examples exist.
  4. Flag anything that looks like a bill, legal deadline, or security alert.

4. How to validate the result

No mail was sent. No archive/delete unless explicitly approved. Security-looking messages are never auto-ignored.

5. What to return

Bucketed list with draft replies attached to needs-reply items, plus a "handle today" top five.

6. What requires approval

Do not send, delete, or unsubscribe without approval. Newsletter unsubscribe is L2+ and listed separately.

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