Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline.
Install Meeting Notes
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiskillstore/marketplace meeting-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/alapha888/meeting-notes .claude/skills/meeting-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .claude/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiskillstore/marketplace meeting-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/alapha888/meeting-notes .agents/skills/meeting-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .agents/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiskillstore/marketplace meeting-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/alapha888/meeting-notes .cursor/skills/meeting-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .cursor/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aiskillstore/marketplace.git --path skills/alapha888/meeting-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiskillstore/marketplace meeting-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/alapha888/meeting-notes .gemini/skills/meeting-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .gemini/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aiskillstore/marketplace meeting-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/alapha888/meeting-notes .github/skills/meeting-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .github/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiskillstore/marketplace --skill meeting-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiskillstore/marketplace meeting-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/alapha888/meeting-notes .opencode/skills/meeting-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meeting-notes" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/meeting-notes into .opencode/skills/meeting-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
meeting-notes- GitHub stars
- 430
- Used in
- 2 other repos
- Token cost
- ~793 tokens
- SKILL.md length
- 317 words
- Files
- 2
- Skills in repo
- 1,108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline.
- Works in 4 steps: Read the raw notes: read the transcript… → Sort into three buckets → Conclusion first: open the minutes with… → …
- The user pastes meeting transcripts
- SKILL.md covers Workflow, Rules, Minimal example and Anti-patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Meeting Notes is an agent skill from aiskillstore/marketplace. Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline. Use when the user pastes meeting transcripts or rough notes and asks for minutes or a summary.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill-report.json`).
It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is MIT.
When your agent uses it
- The user pastes meeting transcripts
- Rough notes and asks for minutes
Example prompts
- “Use the meeting-notes skill to turn raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions…”
- “/meeting-notes”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read the raw notes: read the transcript or jotted notes the user pasted. Find "what was finally decided" first, then look back for the…
- Sort into three buckets
- Conclusion first: open the minutes with ≤3 lines on "what this meeting decided", then expand the three buckets.
- Self-check before output: does every action item have an owner? A deadline? Are decisions affirmative statements? Do open questions have a…
What it can do on your machine
Read from SKILL.md and the folder at commit ad8daf7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Meeting Notes loads about 793 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 317 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aiskillstore/marketplace at commit ad8daf7, republished under its MIT licence (© aiskillstore). 317 words, ~793 tokens.
Download SKILL.mdSave it as
.claude/skills/meeting-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- meeting-notes
- description
- Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline. Use when the user pastes meeting transcripts or rough notes and asks for minutes or a summary.
- license
- MIT
Meeting Notes
Turn messy meeting notes into minutes that let someone who missed the meeting catch up in 3 minutes — and let attendees know exactly what they owe.
Workflow
- Read the raw notes: read the transcript or jotted notes the user pasted. Find "what was finally decided" first, then look back for the reasoning. Minutes record conclusions and points of disagreement, not the full discussion.
- Sort into three buckets:
- Decisions: one per line, phrased as "Decided to do X", never "Discussed X".
- Action items: each must have an owner + a deadline. If the notes name no owner, mark
[unassigned]; if no deadline, mark[TBD]— never invent them. - Open questions: issues left undecided that need a follow-up; state "what is blocking, and who owns the next step."
- Conclusion first: open the minutes with ≤3 lines on "what this meeting decided", then expand the three buckets.
- Self-check before output: does every action item have an owner? A deadline? Are decisions affirmative statements? Do open questions have a next step? Flag any "no" — don't gloss over it.
Rules
- Do not fabricate. Names, dates, and numbers not in the notes must not appear; mark missing ones
[to confirm]. - Do not editorialize. No "Maria's proposal seemed shaky" — only "Maria's proposal was rejected because…" (if a reason was stated).
- Length control: the minutes body must be ≤1/3 of the raw notes. Longer means you didn't distill — redo it.
Minimal example
Input (raw notes excerpt):
...James said the login page is too slow, Maria suggested adding a cache layer, everyone agreed it's worth a pilot; draft the proposal by next Wednesday; pricing strategy still open, invite Finance next time...Output:
## Meeting minutes (example)
**Bottom line**: Pilot a cache layer to speed up the login page; pricing strategy undecided, pending a session with Finance.
### Decisions
- Adopt a cache layer for login-page performance (pilot first, not a full rollout).
### Action items
- [ ] Maria: draft the caching proposal, due next Wednesday `[date to confirm]`
- [ ] [unassigned]: schedule pricing discussion with Finance `[time TBD]`
### Open questions
- Pricing strategy: no decision reached; the action-item owner will book a dedicated session with Finance.Anti-patterns
- ❌ Chronological minutes: replaying two hours of discussion in order is the same as not organizing it.
- ❌ Ownerless action items: "everyone please follow up" — an action item without an owner and a deadline is not an action item.
- ❌ Invented details: guessing dates or names the notes never mentioned turns minutes into fiction.
- ❌ Decisions written as discussion: "Discussed the feasibility of a caching layer" — did the meeting adopt it or not? Minutes need affirmative statements.
© aiskillstore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/alapha888/meeting-notes of aiskillstore/marketplace.
- SKILL.md
- skill-report.json
Open the folder on GitHubat commit ad8daf7
Used in 2 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Meeting Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meeting Notes this skillaiskillstore/marketplace | 430 | 2 repos | ~793 | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Handwriting Stand Uplimin112/min-skill | 362 | — | ~2.5k | Automated safety check: Pass | None | |
| Daily Journalravila4/claude-adhd-skills | 157 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
Daily Journal
ravila4/claude-adhd-skills
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Granola
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
More from aiskillstore/marketplace
All 1,108 skills in this repoCode Stats
aiskillstore/marketplace
Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).
File Search
aiskillstore/marketplace
Modern file and content search using fd, ripgrep (rg), and fzf.
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
Doc Scanner
aiskillstore/marketplace
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.
Find Replace
aiskillstore/marketplace
Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.
Investigating Codebases
aiskillstore/marketplace
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…
Related
Categories
Questions about Meeting Notes
What does Meeting Notes do?
Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline. Meeting Notes is an agent skill from aiskillstore/marketplace. Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a deadline.
When should I use Meeting Notes?
Meeting Notes fits situations like: the user pastes meeting transcripts; rough notes and asks for minutes.
How do I install Meeting Notes in Claude Code?
Run `npx skills add aiskillstore/marketplace --skill meeting-notes -a claude-code`. Or copy the skill folder (skills/alapha888/meeting-notes in aiskillstore/marketplace) into .claude/skills/meeting-notes in your project. Claude Code loads it when a task matches its description.
How do I install Meeting Notes in Codex?
Run `npx skills add aiskillstore/marketplace --skill meeting-notes -a codex`. Or copy the skill folder (skills/alapha888/meeting-notes in aiskillstore/marketplace) into .agents/skills/meeting-notes in your project. Codex loads it when a task matches its description.
Can I use Meeting Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill meeting-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-notes, .gemini/skills/meeting-notes, .github/skills/meeting-notes and .opencode/skills/meeting-notes in your project.
What does Meeting Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Meeting Notes is instructions for the agent only.
Does Meeting Notes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Meeting Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Meeting Notes use?
Meeting Notes is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meeting Notes use?
About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Meeting Notes?
Skills that share tags, products or a category with Meeting Notes: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 362 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meeting Notes?
aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,108 skills in this directory. The repository was last updated on October 7, 2026.
Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.