meeting-task-extraction

meeting-task-extraction is a skill for Claude Code, Codex from Autter-dev/agentic-sales-skills. It costs 21 tokens per session (838 once invoked), scanned A, original, MIT.

A method for turning meeting notes, transcripts, or spoken recaps into a checklist of action items. It records who owns each task, its deadline, and its priority.

In plain words
What is it for?
It is for extracting tasks, owners, deadlines, and priorities from meetings, then formatting them for a task manager or customer relationship management system.
Why use it?
It removes the need to manually find commitments and follow-up work in a long meeting record. It can also point out when the notes do not contain enough information.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for extracting tasks, owners, deadlines, and priorities from meetings, then formatting them for a task manager or customer relationship management system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/autter-dev/agentic-sales-skills/meeting-task-extraction
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 Autter-dev/agentic-sales-skills --skill meeting-task-extraction
Clone the repo
git clone --depth 1 https://github.com/Autter-dev/agentic-sales-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-task-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/meeting-task-extraction/github.svg)](https://agentmods.dev/skills/autter-dev/agentic-sales-skills/meeting-task-extraction)
Your own site
<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/meeting-task-extraction"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/meeting-task-extraction/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-task-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/meeting-task-extraction"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/meeting-task-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 838 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.00021 $0.00838
Opus 5 $0.00010 $0.00419
Sonnet 5 $0.00004 $0.00168
Haiku 4.5 $0.00002 $0.00084

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

Security

Grade A, and why

meeting-task-extraction 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 10d 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.

03-meetings-and-demos/skills/meeting-task-extraction/SKILL.md · 97 lines

How it starts

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

Meeting Task Extraction

You are a project manager. Your job is to extract every action item from meeting notes, transcripts, or verbal recaps — categorize them by owner, assign deadlines, and format them as a ready-to-use checklist for your task manager or CRM.

When to Activate

  • User shares meeting notes, a transcript, or verbally recaps a meeting
  • User asks "what are my action items?" or "what did we commit to?"
  • User wants to log tasks from a meeting into their CRM or task manager

How This Works

Step 1: Receive Meeting Input

Accept any of the following:

  • Full meeting transcript
  • Bullet-point meeting notes
  • Verbal recap from the user
  • Email thread with meeting discussion

If the input is sparse, ask clarifying questions:

  • Did anyone commit to sending something?
  • Were there any deadlines mentioned?
  • Is there a next meeting scheduled?
  • Did you promise to follow up on anything?

Step 2: Extract Action Items

For every action item, capture:

  • Task description: Clear, specific, actionable (starts with a verb)
  • Owner: Who's responsible (you, the prospect, a colleague, shared)
  • Deadline: Explicit date if mentioned, inferred date if not (e.g., "before next meeting" = meeting date minus 1 day)
  • Priority: Critical path (blocks the deal) vs. nice-to-have (helpful but not blocking)
  • Related context: Why this task matters, what conversation it came from

Step 3: Categorize by Owner

Your Action Items (things you committed to):

  • Follow-up email
  • Materials to send (case studies, proposals, technical docs)
  • Internal tasks (get pricing approved, schedule technical resource)
  • Research tasks (competitor comparison, reference customer)

Their Action Items (things the prospect committed to):

  • Internal reviews or approvals
  • Sharing information (org chart, budget, requirements doc)
  • Scheduling follow-ups with other stakeholders
  • Testing or evaluating something

Shared / Mutual Items:

  • Schedule the next meeting
  • Joint presentations or workshops
  • Shared document collaboration

Read the full file on GitHub · 97 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 97 lines · 21 tokens per session scan A cd988c0d1d8e

Subscribe to this mod's changes

meeting-task-extraction is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 838 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

meeting-autopilot

Turn meeting transcripts into operational outputs — action items, decisions, follow-up email drafts, and ticket drafts. Not a summarizer. An operator. Accepts VTT, SRT, or plain text. Multi-pass LLM extraction.

cacheforge-ai/cacheforge-skills · 52 tokens

fs-electric-studio

OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.

nexu-io/open-design · 53 tokens

html-ppt-zhangzara-cobalt-grid

OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.

nexu-io/open-design · 54 tokens

huashu-bento-insight

OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.

nexu-io/open-design · 48 tokens

huashu-takram-soft-tech

OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.

nexu-io/open-design · 50 tokens

html-ppt-product-launch

OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.

nexu-io/open-design · 47 tokens