Actions
Skill nord342/claude-meeting-notes/meeting-notes/skills/actions
Connector-free Claude plugin (Cowork & Claude Code): turn any meeting into a clean recap, a tracked cross-meeting action list, and ready-to-send follow-ups — 100% local.
npx -y skills add nord342/claude-meeting-notes --skill actionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review and maintain the cross-meeting action ledger (ACTIONS.md) — show what's open, overdue, or due soon, filter by owner, and mark items done. Use when the user asks "what are my open action items", "what's overdue", "what does Sarah owe me", or wants to check off completed tasks.
SKILL.md
3.0 KB, 687 tokens by cl100k_base, as published. Nobody here has run it
Action Tracker
Maintain and query ./Meetings/ACTIONS.md, the single living list of every commitment across all meetings. This is what makes the plugin worth using: nothing falls through the cracks.
Uses the action-item format and ledger structure from the meeting-notes core skill and
${CLAUDE_PLUGIN_ROOT}/skills/meeting-notes/templates/ACTIONS.md.
The user's intent comes via $ARGUMENTS. Interpret it:
$ARGUMENTS | Do this |
|---|---|
| empty | Show the full ledger: overdue first, then open (grouped by owner), then a one-line tally. |
an owner name (e.g. Sarah) | Show only that person's open items. |
overdue | Show only items past their due date. |
today / this week | Show items due in that window. |
done: <task> or did <task> | Mark the matching item complete. |
| free text | Best-effort match to one of the above. |
Maintaining the ledger
Reconcile (the dedup logic recap relies on)
When adding items, an action already exists if it has the same owner and substantially the same task (ignore wording differences, tense, trailing punctuation). When a match is found:
- Keep one line. Update the due date if the new mention has a newer/clearer one.
- If it was discussed again in a later meeting, update the
· _Source_suffix to the most recent meeting (or note "(re-raised)").
Never create a second line for the same real-world commitment.
Recompute status
Every time you touch the ledger, re-sort items into sections against today's date:
- 🔴 Overdue — due date is before today and not done.
- 🟡 Open — not done, due today or later, or
(no date). - ✅ Done — completed (keep the most recent ~20, archive older ones to the bottom or a
## Archivesection so the file stays readable).
Update the _Last updated: <date>_ line at the top.
Marking done
When the user says an item is done:
- Change
- [ ]to- [x], move it to ✅ Done, append· done <today>. - Confirm in one line, and if it unblocks something obvious, mention it.
Output style
Be a scannable status board, not a wall of text. Lead with what's on fire:
🔴 Overdue (2)
@You Update billing spec — due Jul 6 · Product Sync (Jun 29)
@Sarah Send pricing deck — due Jul 3 · Product Sync (Jun 29)
🟡 Open (5) — @You: 2 · @Sarah: 1 · @Dev: 1 · @unassigned: 1
...
Tip: 1 item is still @unassigned — assign it with "/meeting-notes:actions" or tell me who owns it.
Always end by surfacing anything @unassigned or (no date) so the user can resolve it.