Meeting Notes
Chatverlauf einwerfen — jede Aufgabe bekommt Verantwortliche und eine Deadline
Verwandelt Chatverläufe und Transkripte in strukturierte Notizen: Entscheidungen, Aufgaben (Verantwortliche + Deadline, ohne Ausnahme), Diskussionszusammenfassung, Agenda fürs nächste Mal.

In 3 Schritten installieren
Keine Anmeldung. Keine CLI-Tools. Wählen Sie Ihre AI, kopieren Sie eine Zeile und fügen Sie sie ein.
Lieber selbst machen? Kaufen Sie den Skill ($4.99), laden Sie die ZIP-Datei aus Ihrer Kaufbestätigung herunter, entpacken Sie sie in das oben angezeigte Verzeichnis und starten Sie Ihre AI-Sitzung neu — gleiches Ergebnis. Haben Sie ihn schon gekauft? Ihr AI-Assistent kann ihn für Sie herunterladen.
Beweise aus der Praxis
Echte Menschen haben genau diese Aufgabe mit AI-Agenten erledigt.
Turn voice notes into Linear tickets and review analytics
Anwendungsfall ansehen →AnwendungsfallRecord meetings and suggest answers live from uploaded files
Anwendungsfall ansehen →AnwendungsfallNegotiate hotel rooms by phone call
Anwendungsfall ansehen →Was ist enthalten
Eine SKILL.md (die Anleitung) + eine Startvorlage. Eine Vorschau:
Meeting Notes
When to use
- The meeting is over and all you have is a transcript or a chat log that needs to become readable minutes
- The discussion sprawled and "what we talked about" needs compressing into "what we decided and who's doing what"
- A cross-team meeting needs its conclusions synced so absentees get it in 3 minutes
- The boss or client wants a "one-pager" on the meeting outcome
- A long-running project needs a paper trail: when it was decided, who called it, and why
Workflow
- Read everything, grab the conclusions first
- Input: the full chat log / transcript, attendee list if available
- Action: find every decision, approval, rejection, and open item; ignore small talk and tangents
- Output: conclusion list, one sentence each, noting who called it (e.g. "Called by Ana: …")
- Extract action items
- Input: conclusion list + source text
- Action: break each action into "what to do" and find its owner and deadline; where the source is silent, mark "to confirm" instead of guessing
- Output: action list, each with task, owner, and deadline
- Compress the discussion
- Input: the discussion passages behind each conclusion
- Action: keep only the key disagreements, rationale, and data that shaped the conclusion; cut repeated and emotional remarks
- Output: 3–8 discussion bullets, each stating who argued what and on what basis
- Collect next-time topics
- Input: "let's revisit" / "decide later" type remarks in the source
- Action: list them separately as next-time topics, noting where each got stuck
- Output: next-time topic list, one line each + what's blocking it
- Assemble the final draft from the template
- Input: conclusions + actions + discussion summary + next-time topics
- Action: assemble per template.md: header info → conclusions → action table → discussion summary → next topics, with 1–3 key source quotes
- Output: markdown minutes ready to forward
Output spec
- The first 3 lines must state: what meeting, when, who attended, and the core conclusions — no scrolling to find the point
- Action items in a table with columns: task / owner / deadline / status; each item executable and verifiable
- Deadlines as concrete dates (e.g. Oct 15), never fuzzy words like "next week" or "ASAP"
- Names consistent throughout: full name or one fixed short form, never switching mid-document
- Discussion summary covers only conclusion-relevant disagreements and rationale, not the whole play-by-play
- Key conclusions carry a source quote (speaker + the gist of their words) for traceability
- Title format "date + topic" (e.g. 1011-Q4 Campaign Review) for easy archiving and search
- For minutes being broadcast, add a "sent to" line after the action table stating who received it
Vorschau der Startvorlage
Meeting Notes
Header
- Topic:
- Time:
- Attendees:
- Notetaker:
Conclusions (read this first)
Action items
Das Skill-Paket selbst (SKILL.md + Vorlage) ist auf Englisch verfasst.


