meeting

meeting is a skill for Claude Code from aleksander-dytko/ai-pm-workspace. It costs 15 tokens per session (1,310 once invoked), scanned A, original, MIT.

A workflow that turns raw meeting notes into a structured meeting record and adds the user's action items to a task file.

In plain words
What is it for?
Use it to browse recent meeting files, process one file, or turn notes pasted directly into the chat into a structured record.
Why use it?
It separates decisions and follow-up work from unstructured notes, so important commitments are easier to find and track.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Good fit Use it to browse recent meeting files, process one file, or turn notes pasted directly into the chat into a structured record.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aleksander-dytko/ai-pm-workspace/meeting
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add aleksander-dytko/ai-pm-workspace --skill meeting
Clone the repo
git clone --depth 1 https://github.com/aleksander-dytko/ai-pm-workspace

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for meeting

README.md
[![agentmods](https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/meeting/github.svg)](https://agentmods.dev/skills/aleksander-dytko/ai-pm-workspace/meeting)
Your own site
<a href="https://agentmods.dev/skills/aleksander-dytko/ai-pm-workspace/meeting"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/meeting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meeting

Your own site · 80×15
<a href="https://agentmods.dev/skills/aleksander-dytko/ai-pm-workspace/meeting"><img src="https://agentmods.dev/badge/skills/aleksander-dytko/ai-pm-workspace/meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.01310
Opus 5 $0.00008 $0.00655
Sonnet 5 $0.00003 $0.00262
Haiku 4.5 $0.00002 $0.00131

Measured 11d ago against content hash d41be1ac9dac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

meeting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/meeting/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process Meeting Notes

You are helping process raw meeting notes into a structured meeting note. Action items for the user land in Dashboard/tasks.md.

Input Modes

The skill operates in one of three modes based on $ARGUMENTS:

Mode Arguments When to use
Browse (none) or browse List recent files in Meetings/ that look unprocessed
Specific file File path or partial name Process notes from a specific file
Paste Pasted text (long string) Meeting notes pasted directly into the prompt

Workflow

Step 0: Determine mode and get raw notes

If no arguments (Browse mode):

  1. Use the Glob tool with pattern Meetings/*.md to list meeting files. Do NOT use Bash ls - Glob is quieter and shows results already sorted.
  2. Read the top N candidates (up to 5) in parallel and identify files with raw/unstructured notes (no "## Decisions", no structured format).
  3. Show a numbered list of unprocessed files.
  4. Ask: "Which meeting do you want to process?"

If specific file path:

  1. Read the file.
  2. If already structured (has Decisions, Action Items sections): warn and ask to confirm before overwriting.
  3. If raw notes: proceed directly.

If pasted text:

  • Use the pasted text as raw input.
  • Ask for meeting date and title if not obvious from the text.

Step 1: Analyze raw notes

Extract:

  • Meeting title (from filename or content)
  • Date (from filename or content)
  • Attendees (mentioned names)
  • Key topics discussed
  • Decisions made (explicit or implicit)
  • Action items (tasks, follow-ups, commitments - with owners)
  • Open questions (unresolved topics)

Step 2: Cross-reference attendees

  • Read Dashboard/people-profiles.md to verify attendee names and roles.
  • Use tags (e.g., #FirstName) when mentioning people.

Step 3: Search for related context

  • Search Loose Notes/Work/ for related decisions or notes.
  • Check Dashboard/Weekly P-Tasks.md for related P-tasks.
  • Identify which existing notes this meeting relates to - used in the "Related" section.

Read the full file on GitHub · 145 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 145 lines · 15 tokens per session scan A d41be1ac9dac

Subscribe to this mod's changes

meeting is a skill published in the GitHub repository aleksander-dytko/ai-pm-workspace (34 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,310 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

customise-workflow

Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…

anombyte93/prd-taskmaster · 137 tokens

expand-tasks

Expand all TaskMaster tasks with deep research before coding begins. Reads tasks.json, launches parallel research agents per task in waves using the research-expander agent. Writes findings back to tasks.json. Part of the prd-taskmaster toolkit. Use after PRD is parsed and before implementation. Invoke with…

anombyte93/prd-taskmaster · 68 tokens

eol-process

Run a product sunset end to end — decide, align, plan, prepare, announce, close. Use when you need the whole EOL process, not just one artifact.

deanpeters/Product-Manager-Skills · 39 tokens

epic-breakdown-advisor

Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.

deanpeters/Product-Manager-Skills · 38 tokens

prd-development

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

deanpeters/Product-Manager-Skills · 35 tokens

altitude-horizon-framework

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

deanpeters/Product-Manager-Skills · 33 tokens