agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/draft-call-followup/SKILL.md

draft-call-followup

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 Call Follow-up”. A useful skill states the six fields from Skills and routines. A call just happened and the owner needs an unsent recap, split tasks, and a suggested next window — not a sent email. Recap is labeled DRAFT. No email was sent. No calendar event was created. Every dated commitment has a source quote, or the date is…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Call notes, transcript, or recording

    line 16
  2. Distinctive:

    Read the notes. If they are missing, ask and stop.

    line 23
  3. Distinctive:

    After-call pack: recap, owner tasks, customer tasks, suggested window, CRM note draft, action log.

    line 37
  4. Distinctive:

    Do not send the recap. Do not book or move meetings.

    line 42

≈ “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 Call Follow-up

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Draft Call Follow-up”.

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

1. When to use it

A call just happened and the owner needs an unsent recap, split tasks, and a suggested next window — not a sent email.

2. Required inputs and access

  • Call notes, transcript, or recording
  • Calendar event for attendees and time
  • Prior mail thread with the account when present
  • Promise log in /workspace when present

3. Sequence of work

  1. Read the notes. If they are missing, ask and stop.
  2. List attendees from the calendar event. If the event is missing, mark attendees unknown.
  3. Draft a recap of what was said. Separate facts from inferences.
  4. Split owner tasks from customer tasks. Dates not in the notes stay unknown.
  5. Propose a next window from free/busy. Do not book it.
  6. Label the recap DRAFT. Do not send.

4. How to validate the result

Recap is labeled DRAFT. No email was sent. No calendar event was created. Every dated commitment has a source quote, or the date is unknown.

5. What to return

After-call pack: recap, owner tasks, customer tasks, suggested window, CRM note draft, action log.

6. What requires approval

Do not send the recap. Do not book or move meetings. Do not create CRM records unless the owner names that action later.

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.