agentleFS
Lethe044Lethe044/agentskill-kit/skills/meeting-notes-to-actions/SKILL.md

meeting-notes-to-actions

Skill48 starsChanged 17 days agoMITView on GitHub

Converts raw meeting notes or a transcript into decisions, action items with owners and due dates, and open questions. Use when the user pastes meeting notes, asks for a summary of a call, or wants a follow-up message for attendees.

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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only list an action item when someone committed to it or was asked to do it.

    line 39
  2. Very specific:

    Never invent an owner or a date.

    line 40
  3. Distinctive:

    Start every task with a verb and keep it specific enough to tell when it is done.

    line 41
  4. Distinctive:

    Keep names exactly as written in the notes.

    line 42
  5. Distinctive:

    Keep the summary neutral. Do not add opinions or judge what people said.

    line 43
  6. Distinctive:

    Read all of the notes before writing anything.

    line 47
  7. Distinctive:

    If asked for a follow-up message, write a short one that repeats the action table and nothing else.

    line 50
  8. Distinctive:

    If the notes are too short to contain decisions or tasks, say so and return only the summary.

    line 54

“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 to actions

When to use

  • The user pastes notes or a transcript and asks for a summary.
  • The user needs a follow-up email or chat message after a meeting.
  • Action items are buried in a long discussion.

Output format

## Summary
Two to three sentences on the purpose and the outcome.

## Decisions
- What was decided, and by whom if it is stated.

## Action items
| Owner | Task | Due |
| --- | --- | --- |
| Name | A verb-first task that can be checked | Date or "not set" |

## Open questions
- Things that were raised and not resolved.

Rules

  1. Only list an action item when someone committed to it or was asked to do it. Ideas that nobody took are open questions.
  2. Never invent an owner or a date. Write unassigned or not set instead.
  3. Start every task with a verb and keep it specific enough to tell when it is done.
  4. Keep names exactly as written in the notes.
  5. Keep the summary neutral. Do not add opinions or judge what people said.

Steps

  1. Read all of the notes before writing anything.
  2. Pull out decisions first, then commitments, then unresolved points.
  3. Fill the format above and remove empty sections.
  4. If asked for a follow-up message, write a short one that repeats the action table and nothing else.

Errors

If the notes are too short to contain decisions or tasks, say so and return only the summary.

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.