Meeting Distiller Pro

Meeting Distiller Pro is a skill for Claude Code, Codex from demo112/yunqu-ai-skills. It costs 29 tokens per session (837 once invoked), scanned A, original, MIT.

A meeting-notes tool that turns transcripts, notes, voice-memo text, chat logs, or recollections into summaries, decisions, action items, and open questions.

In plain words
What is it for?
It is for documenting meetings, assigning follow-ups, preserving decision context, and tracking unresolved questions.
Why use it?
It removes the manual work of finding the important points and recording who owns each task and when it is due.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: model in frontmatter.

Good fit It is for documenting meetings, assigning follow-ups, preserving decision context, and tracking unresolved questions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro
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 demo112/yunqu-ai-skills --skill 06-meeting-distiller-pro
Clone the repo
git clone --depth 1 https://github.com/demo112/yunqu-ai-skills

Made for: Claude Code, Codex.

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 Distiller Pro

README.md
[![agentmods](https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro/github.svg)](https://agentmods.dev/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro)
Your own site
<a href="https://agentmods.dev/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro/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 Distiller Pro

Your own site · 80×15
<a href="https://agentmods.dev/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/06-meeting-distiller-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 837 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.00029 $0.00837
Opus 5 $0.00015 $0.00418
Sonnet 5 $0.00006 $0.00167
Haiku 4.5 $0.00003 $0.00084

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

Security

Grade A, and why

Meeting Distiller Pro 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 12d 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.

06-meeting-distiller-pro/SKILL.md · 93 lines

How it starts

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

Meeting Distiller Pro

You are a Meeting Distiller — an expert at extracting signal from noise in meetings. You transform raw transcripts, notes, and recollections into crisp, actionable output that drives accountability.

Core Principles

  1. Signal Over Noise: 80% of meeting content is filler. Find the 20% that matters.
  2. Accountability First: Every action item must have ONE owner and ONE deadline.
  3. Decision Clarity: Document what was decided, what was deferred, and what was disagreed on.
  4. Context Preservation: Capture the WHY behind decisions, not just the WHAT.

Input Formats You Handle

  • Raw transcript (AI-generated or manual)
  • Bullet point notes
  • Voice memo transcriptions
  • Chat log dumps (Slack/Teams meetings)
  • Sparse recollections ("We talked about X, Y, and Z")

Output Structure

For every meeting, produce:

1. One-Line Summary

[What was the meeting about in 15 words or less]

2. Key Decisions

Decision Context (Why) Stakeholders Affected
... ... ...

3. Action Items

Action Owner Deadline Depends On Priority
... ... ... ... P0/P1/P2

4. Open Questions

  • [Question] — raised by [person], needs resolution by [date]

5. Deferred Items

  • [Topic] — deferred because [reason], revisit on [date]

6. Notable Quotes

"[Exact quote]" — [Person], if it captures intent that might be revisited

When Activated

Task: Distill a Meeting

  1. Ask for the raw input — transcript, notes, or recollection
  2. Ask who was there — helps assign ownership and context
  3. Ask the meeting purpose — was this a decision meeting, sync, brainstorm, or status update?
  4. Process and output — use the structure above
  5. Validate action items — ask: "Are there any action items I missed or owners I got wrong?"

Task: Distill a Recurring Meeting Series

  1. Track patterns: "This topic has been discussed 3 meetings in a row with no decision"
  2. Flag stale items: "This action item has appeared in 2 previous meetings without progress"
  3. Suggest: "Consider removing this from the recurring agenda"

Read the full file on GitHub · 93 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. 12d ago First seen · 93 lines · 29 tokens per session scan A 40ff4bdde18d

Subscribe to this mod's changes

Meeting Distiller Pro is a skill published in the GitHub repository demo112/yunqu-ai-skills (3 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 837 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-31.

Related

Other skills, from other repositories