agentleFS
donnybacondigital-debugdonnybacondigital-debug/claude-code-business-kit/.claude/skills/meeting-to-actions/SKILL.md

meeting-to-actions

Skill0 starsChanged 2 months agoMITView on GitHub

Convert meeting notes or a transcript into decisions, action items with owners and due dates, open questions, and a ready-to-send follow-up email. Use when the user shares meeting notes, a call transcript, "acta", "notas de la reunión", or asks what was agreed or who does what after a meeting.

6 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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    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. Very specific:

    No action without an owner field, even if the owner is ?

    line 52
  2. Distinctive:

    No decision without evidence from the notes.

    line 53

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

People leave meetings with different memories of what was agreed. This skill writes one shared version.

Inputs

  • Notes or a transcript, in any language and any level of mess.
  • Optional: list of attendees and their roles, today's date.

Steps

  1. Separate the content into four buckets.
    • Decisions: something was agreed.
    • Actions: someone will do something.
    • Open questions: raised but not resolved.
    • Context: everything else, which does not go into the output.
  2. Check each decision. Quote or closely paraphrase the words that show it was agreed. If it only sounds like a suggestion, move it to open questions.
  3. Check each action for an owner and a due date.
    • Owner missing → write Owner: ? and add it to the questions.
    • Relative date ("next Friday") → convert to a calendar date using the meeting date, shown in brackets.
    • No date → Due: to agree.
  4. Draft the follow-up email in the language of the meeting. Short, with decisions and actions only, and a line asking people to reply within 24 hours if something is wrong.

Output format

# [Meeting title] · [date]

## Decisions
1. [decision] (evidence: "[quote]")

## Actions
| # | Action | Owner | Due |
|---|---|---|---|

## Open questions
- [question] (who can answer: [name or ?])

## Follow-up email
Subject: [Meeting title]: decisions and next steps

[email body]

Quality checks before answering

  • No action without an owner field, even if the owner is ?.
  • No decision without evidence from the notes.
  • Nothing added that was not in the notes.
  • The email fits on one phone screen (about 150 words or fewer).

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.