agentleFS
Sign inStart free
rickbauer327-cellrickbauer327-cell/solo-stack-starter/skills/meeting-notes-to-actions/SKILL.md

meeting-notes-to-actions

Skill2 starsChanged 58 days agoMITView on GitHub

Use when the user has meeting notes, a call transcript, or a voice-memo dump and wants decisions, action items, and a follow-up email out of it. Works for client calls, discovery calls, and internal check-ins.

9 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

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .solo/business.md if present (for tone and to recognize client names).

    line 11
  2. Distinctive:

    Before writing the email, show the user the decisions and actions and ask one question: "Anything wrong or missing?" Skip this check only …

    line 23
  3. Very specific:

    If the meeting was a discovery call, add a final section ## Proposal inputs summarizing problem, success criteria, constraints, and budget …

    line 64
  4. Distinctive:

    Do not invent dates, owners, or commitments.

    line 72
  5. Distinctive:

    Do not include the "Flags" section in anything sent to the client.

    line 73
  6. Distinctive:

    Do not summarize the whole conversation — only decisions, actions, questions.

    line 74

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

Meeting Notes → Actions

Turn messy notes into three things: a decision log, an owned action list, and a follow-up email the user can send in 30 seconds.

Step 1 — Load context

Read .solo/business.md if present (for tone and to recognize client names). Proceed without it if missing — this skill works standalone.

Step 2 — Get the notes

Accept a pasted transcript, a file path, or bullet notes. If it's a transcript, identify speakers; if names are missing, use roles (Client, Me).

Step 3 — Extract, then verify

Extract:

  • Decisions — things that were agreed. Quote or closely paraphrase; do not upgrade "we could" into "we will".
  • Actions — each with an owner and a due date if stated. If no date, mark (no date set) rather than inventing one.
  • Open questions — anything raised but unresolved.
  • Risks / flags — budget hesitation, scope drift, unclear decision-maker, missed deadlines mentioned.

Before writing the email, show the user the decisions and actions and ask one question: "Anything wrong or missing?" Skip this check only if the user said "just do it".

Step 4 — Write the outputs

Write meetings/<YYYY-MM-DD>-<client-or-topic-slug>.md:

# <Topic> — <date>
Attendees: ...

## Decisions
- ...

## Actions
| Owner | Action | Due |
|-------|--------|-----|
| Me    | ...    | ... |
| <Client name> | ... | ... |

## Open questions
- ...

## Flags
- ...

## Follow-up email (draft)
Subject: <Topic> — recap and next steps

Hi <name>,

Thanks for the time today. Quick recap so we're aligned:

<2–4 decision bullets>

Next steps:
<action bullets, grouped: yours / theirs, with dates>

<One line on the biggest open question, if any.>

<Sign-off from business.md tone>

If the meeting was a discovery call, add a final section ## Proposal inputs summarizing problem, success criteria, constraints, and budget signals — formatted so /proposal-writer can use it directly.

Tone rules

  • Email under 150 words. Recaps that get read are short.
  • The client's actions come after the user's own — it reads as collaborative, not as assigning homework.
  • Neutral wording for flags in the file; flags never appear in the email.

Do not

  • Do not invent dates, owners, or commitments.
  • Do not include the "Flags" section in anything sent to the client.
  • Do not summarize the whole conversation — only decisions, actions, questions.

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