Meeting Notes That Assign Themselves
Every meeting becomes decisions, owners, and dated commitments.
A summary tells you what was discussed. Nobody needs that. You need to know what changed and who now owes something.
That is the gap this drop closes. It is a operations skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Anyone running more than four meetings a week.
How it works
The skill file does five things, in this order.
1. Feed the transcript. Plus the attendee list so it can attribute correctly.
2. Extract decisions only. Something that changed. Discussion without a change is not a decision.
3. Attach owners and dates. Unassigned actions are flagged rather than quietly dropped.
4. Separate open questions. What was raised and not resolved goes to next week's agenda.
5. Write the follow-up email. Short, in your voice, ready to send before you leave the room.
What comes back
Decisions, owned actions with dates, open questions, and a follow-up email draft.
The mistake to avoid
Add a rule that any action without a named human is escalated to the meeting owner. The gap between 'we should' and 'Sara will by Thursday' is where projects die.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Turn this meeting transcript into an accountability record.
DECISIONS, only items where something actually changed. Format:
"[Decision]. Previously: [what was true before]."
ACTIONS, table: what | owner (named human) | due date | blocked by.
If an action has no named owner, list it under UNASSIGNED and flag it.
OPEN QUESTIONS, raised, not resolved. Include who raised it.
Then draft a follow-up email under 150 words in this tone: {direct, warm,
no filler}. Do not summarise the discussion. Only state what changed and
what is owed.
<attendees>{names and roles}</attendees>
<transcript>{paste}</transcript>