Skip to content
Agentmart
Submit a tool

meeting-notes

Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note…

Skill by prestarius

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/prestarius-meeting-notes

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note, ADRs, tracker issues). Use whenever the user pastes a transcript or messy notes and says "write this up", "minutes", "notatka ze spotkania", "what did we decide", or wants meeting output captured rather than lost.

Use cases: writing, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/meeting-notes

What's inside

Skill name
meeting-notes
Description
Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note, ADRs, tracker issues). Use whenever the user pastes a transcript or messy notes and says "write this up", "minutes", "notatka ze spotkania", "what did we decide", or wants meeting output captured rather than lost.
License
MIT
Instructions
20 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

Read `./CONTEXT.md` if present — use its glossary for terms and its tracker vocabulary for actions.

Produce minutes with these sections, in the language of the source material unless asked otherwise:
1. **Context** — what meeting, when, attendees (only if stated in the source).
2. **Decisions** — one line each: what was decided and why, as stated.
3. **Action items** — `owner — action — due` ; if owner or due date is not in the source, write
   `TODO:` rather than inventing one.
4. **Open questions** — unresolved points, each with who can answer it if known.
5. **Parking lot** — raised but deferred topics.

Rules:
- Extract, don't summarize away: if the source is Markdown, the output must be full and
  exhaustive (per the working agreement) — every decision and action in the source appears here.
- Never attribute opinions to named people unless the source does.
- Quote ambiguous statements verbatim instead of interpreting them.

Then offer routing (each opt-in, never automatic): the obsidian-note skill to file it in the
vault, the domain-modeling skill for any durable architecture decision, the to-tickets skill for the action
items.

From prestarius/jet-skills-stack, MIT.

More from prestarius/jet-skills-stack

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Oct 19, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/prestarius/jet-skills-stack
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from prestarius

Cite this page

meeting-notes skill. Agent Mart. https://agentmart.dev/skills/prestarius-meeting-notes (last updated 2026-10-24)