Meeting notes
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill meeting-notesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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
Turn raw meeting transcripts, chat logs, or rough notes into clean, structured meeting notes with decisions and action items. Use whenever the user shares a transcript or messy notes, asks for meeting minutes, wants action items extracted, or says things like "clean up my notes from the standup" — even if they don't say the word "minutes".
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, 507 tokens by cl100k_base, as published. Nobody here has run it
Meeting Notes
Convert raw meeting input into notes a person who missed the meeting can act on in under two minutes of reading. Optimize for decisions and action items, not a play-by-play of who said what.
Process
- Read the full input first. Identify: attendees, topics, decisions made, action items (with owner and due date if stated), and open questions.
- Discard filler: greetings, scheduling chatter, repeated points, verbal tics. Keep disagreements — note both positions and how (or whether) they were resolved.
- Pick the output format. Default to standard minutes. If the user asks
for "action items", "a digest", or "a summary for my boss", read
references/formats.mdand use the matching format there. - Render the notes, then list anything you could not determine (missing owners, unclear decisions) under Needs clarification rather than guessing.
Rules
- Never invent owners, dates, or decisions that aren't in the source. An
action item without a stated owner is written as
Owner: unassigned. - Decisions are written as outcomes, not discussion: "Decided to ship v2 behind a feature flag", not "Talked about feature flags".
- Attribute contested opinions ("Priya argued for X; Sam preferred Y"), but don't attribute routine facts.
- Keep the whole output shorter than the input. If your notes are longer, you're transcribing, not summarizing.
- Preserve exact figures, dates, and names verbatim from the source.
Default output: standard minutes
# <Meeting name> — <date>
**Attendees:** ...
## Decisions
- ...
## Action items
- [ ] <task> — Owner: <name>, Due: <date or "not set">
## Discussion
- <topic>: 2–3 sentence summary
## Needs clarification
- ...
Edge cases
- Input is an audio-transcript with speaker labels missing: group by topic instead of speaker and note that attribution wasn't possible.
- Multiple meetings in one paste: ask whether to split into separate notes before proceeding.
- User just wants actions: skip everything except the action-item digest
format in
references/formats.md.