hilbertraumai/hilbertraum/meeting-protocol
Claude Code and agent skill by hilbertraumai/hilbertraum
- community
Checking that the SKILL.md file is still in the repository.
Use when the user shares a meeting transcript, rough notes, or agenda and wants clean, structured minutes — decisions, action items, and open questions.
Install
npx vskill@latest install hilbertraumai/hilbertraum/meeting-protocolSKILL.md
Meeting Minutes
Honesty rules — these lead and always apply, even if the rest of this skill is shortened to fit the context:
- Work only from the selected material — never add facts, names, dates, or decisions the source
does not contain.
- Separate what was decided from what was merely discussed. If the notes are ambiguous about
whether something was agreed, say so plainly instead of resolving it yourself.
- Do not infer attendees from first names unless they are clearly attendees; do not infer deadlines;
do not infer agreement from silence.
- Keep every date, name, and figure exactly as printed, including the date format, and quote wording
that carries weight (a decision, a commitment, a deadline) close to the original so the user can verify it. Cite the source for document-grounded items.
- Answer in the user's language: German notes → German minutes (Beschlüsse, Aufgaben, offene Fragen);
English notes → English minutes.
Use this skill when the user shares a meeting transcript, rough notes, an agenda, or an audio transcript and wants professional meeting minutes.
Produce the minutes in this order. Omit a section only if the source genuinely has nothing for it; never pad it with a guess.
1. Short summary
2–5 factual bullets. No invented decisions.
2. Meeting context
Only items present in the source — date/time, attendees, organization/project, meeting purpose. Write "Not stated" for anything absent.
3. Topics discussed
Grouped by topic, concise.
4. Decisions made
If no decision is explicit, write "No explicit decisions found in the provided material."
5. Action items
- Owner must be explicitly stated, else "Not stated"; same for the deadline.
- Do not turn a general idea into an action item unless the source clearly assigns an action.
- "We should maybe…" is an open question or a proposal, not an action item.
6. Open questions
Unresolved questions, parking-lot items, missing decisions.
7. Risks / follow-ups
Only source-grounded concerns.
8. Formal minutes version
A polished version that can be pasted into an email or record.
Formal motions/votes. If — and only if — the source uses formal motion language, record for each motion: the motion text; the mover and seconder if stated; the result (passed / failed / tabled / referred / postponed / unknown); and the vote tally if stated. A motion is distinct from general discussion and is normally disposed of as passed, defeated, tabled, referred, or postponed. Never invent parliamentary detail the source does not contain.
(The honesty rules that govern these minutes are stated at the top of this skill.)
Security
- Security scanPassed, 96 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingapp-skills/meeting-protocol/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/hilbertraumai/hilbertraum/meeting-protocol)