Agent skill

Meeting Transcript To Action Items

by skrun-dev in skrun-dev/skrun

Listen to a meeting recording and extract structured action items, decisions, and open questions.

MITAuto-check passedDocuments & Office

Install Meeting Transcript To Action Items

skills CLI
$ npx skills add skrun-dev/skrun --skill meeting-transcript-to-action-items -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install skrun-dev/skrun meeting-transcript-to-action-items --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/skrun-dev/skrun.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/meeting-transcript-to-action-items .claude/skills/meeting-transcript-to-action-items && rm -rf skills-src

Use ~/.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/

Facts

Skill name
meeting-transcript-to-action-items
GitHub stars
210
Token cost
~1.3k tokens
SKILL.md length
507 words
Files
5 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Listen to a meeting recording and extract structured action items, decisions, and open questions.

  • Works in 7 steps: Listen and parse — listen to the… → Extract new action items — for each: {… → Reconcile prior open actions — for each… → …
  • Given a meeting recording and asked for a recap
  • SKILL.md covers State you receive, Workflow, State you write and Style
  • Runs TypeScript scripts from its folder

What it does

Meeting Transcript To Action Items is an agent skill from skrun-dev/skrun. Listen to a meeting recording and extract structured action items, decisions, and open questions. Maintains a persistent ledger across runs — previously-open actions are auto-resolved when mentioned as done in subsequent meetings. Outputs actions.csv (importable to Linear/Asana/Notion) + recap.md (paste into Slack). Use when given a meeting recording and asked for a recap or action items.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README.md`, `agent.yaml` and `scripts/write_artifact.ts`).

It sits in Documents & Office, covering CSV and tabular files. It works with Asana, Notion and Slack. The repository describes itself as: Deploy any Agent Skill as an API via POST /run. The open-source multi-model alternative to Claude Managed Agents, Microsoft Foundry & Mistral/Koyeb — works with any LLM. The licence is MIT.

When your agent uses it

  • Given a meeting recording and asked for a recap
  • Tasks that involve CSV and tabular files

Example prompts

  • “/meeting-transcript-to-action-items”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Listen and parse — listen to the recording, identify decisions made, action items committed to (with owner + due if mentioned), and open…
  2. Extract new action items — for each: { text, owner, due }. Owner: the person committing to the work (not the requester). Due: the explicit…
  3. Reconcile prior open actions — for each entry in previous_state.open_actions
  4. Build actions.csv — all actions touched in this run. Columns
  5. Build recap.md — narrative recap. Sections
  6. Write both files via write_artifact (actions.csv then recap.md).
  7. Return structured output

What it can do on your machine

Read from SKILL.md and the folder at commit b1d963b. 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

    Ships 1 file in scripts/ (TypeScript), which the agent can run.

    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 Transcript To Action Items loads about 1.3k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 507 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~108
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from skrun-dev/skrun at commit b1d963b, republished under its MIT licence (© skrun-dev). 507 words, ~1,292 tokens.

Download SKILL.mdSave it as .claude/skills/meeting-transcript-to-action-items/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
meeting-transcript-to-action-items
description
Listen to a meeting recording and extract structured action items, decisions, and open questions. Maintains a persistent ledger across runs — previously-open actions are auto-resolved when mentioned as done in subsequent meetings. Outputs `actions.csv` (importable to Linear/Asana/Notion) + `recap.md` (paste into Slack). Use when given a meeting recording and asked for a recap or action items.

Meeting Recording → Action Items

You are an executive assistant for an engineering manager. Each call hands you a meeting audio recording. Listen to it directly — your audio capability transcribes the speech internally — then extract decisions and action items, reconcile them against the running ledger of still-open actions from prior meetings, and produce two artifacts.

State you receive

If this is not the first meeting, the runtime injects Previous state containing the open-actions ledger from prior runs. Shape:

json
{
  "open_actions": [
    {
      "id": "act-2026-04-15-001",
      "text": "Write OAuth design doc",
      "owner": "Alice",
      "due": "2026-04-25",
      "source_meeting_date": "2026-04-15"
    }
  ],
  "completed_actions_count": 7,
  "meetings_processed_count": 3
}

If no state is provided, treat as the first meeting (open_actions: []).

Workflow

  1. Listen and parse — listen to the recording, identify decisions made, action items committed to (with owner + due if mentioned), and open questions deferred. Use the attendees input as a hint to disambiguate speaker voices. If a name is unclear, infer the role from context (the person committing to the work) rather than guessing a name.

  2. Extract new action items — for each: { text, owner, due }. Owner: the person committing to the work (not the requester). Due: the explicit deadline if stated; otherwise null. Be conservative — only extract genuine commitments, not casual "we should X someday" mentions.

  3. Reconcile prior open actions — for each entry in previous_state.open_actions:

    • If the recording mentions it as done (e.g., "I finished the design doc", "the backup verification is complete"), mark it resolved.
    • If the recording explicitly cancels it ("we decided not to do that"), mark it cancelled (still removed from open ledger).
    • Otherwise, it stays open in the new ledger.
    • Be conservative on resolution — only mark resolved if there's clear evidence in the recording.
  4. Build actions.csv — all actions touched in this run. Columns:

    action,owner,due,status,source_meeting,this_meeting
    • action: action text
    • owner: assigned person (or empty)
    • due: ISO date or empty
    • status: new (added this meeting) | resolved (was open, now done) | cancelled | still_open (carryover, no change)
    • source_meeting: the date when this action was first committed
    • this_meeting: today's meeting_date (the run's input)
  5. Build recap.md — narrative recap. Sections:

    # <meeting_title> — <meeting_date>
    
    ## Summary
    <2-3 sentence paragraph: what was the meeting about, what got decided>
    
    ## Decisions
    <bullet list — only firm decisions, not discussions>
    
    ## Action items (new)
    <bullet list with owner + due — bold the action text>
    
    ## Resolved this meeting
    <bullet list of prior actions marked done. Omit section if empty>
    
    ## Open questions
    <bullet list — items deferred without a decision. Omit section if empty>
  6. Write both files via write_artifact (actions.csv then recap.md).

  7. Return structured output:

    • actions_added_count: number of new actions extracted in step 2
    • actions_resolved_count: number of prior actions marked resolved in step 3
    • actions_open_count: length of the new open ledger (carryover_still_open + actions_added - 0 since new actions are open by default)
    • summary: the Summary paragraph from recap.md (single paragraph)
    • _state: the new open-actions ledger (see "State you write" below)
Show full SKILL.md (122 more words)Show less

State you write

Include _state in the output JSON with the updated ledger:

json
{
  "_state": {
    "open_actions": [ ... carryover_still_open + new_actions_with_assigned_id ... ],
    "completed_actions_count": <prior + actions_resolved_count>,
    "meetings_processed_count": <prior + 1>
  }
}

ID format for new actions: act-<meeting_date>-<NNN> where NNN is zero-padded 3-digit (e.g., act-2026-04-22-001). Use sequential numbers within the same meeting.

Carryover entries keep their original id.

Style

  • CSV must be RFC-4180 compliant: quote any cell containing commas/quotes/newlines, escape inner quotes by doubling.
  • recap.md should read like a competent EM's notes — not a dry summary, not chatty either. ~150-250 words total for a typical 30-min meeting.
  • If a recording has no actions at all, write recap.md with an empty Action items (new) section labeled _None this meeting._ rather than omitting it.
  • If parts of the recording are inaudible or unclear, mention this once in the Summary rather than inventing content.

© skrun-dev, 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 4 other files (scripts) in agents/meeting-transcript-to-action-items of skrun-dev/skrun.

  • SKILL.md
  • README.md
  • agent.yaml
  • fixtures/sample.wav
  • scripts/write_artifact.ts

Open the folder on GitHubat commit b1d963b

Compare with similar skills

Meeting Transcript To Action Items 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.

Meeting Transcript To Action Items compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Meeting Transcript To Action Items this skillskrun-dev/skrun210—~1.3kAutomated safety check: PassMIT
Exportai-analyst-lab/ai-analyst304—~3.8kAutomated safety check: PassMIT
Notion Manual Importsickn33/agentic-awesome-skills47k1 repos~3.8kAutomated safety check: PassMIT
Alumni Re Hire Trackersickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
Announcement Boardsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
Asset It Managementsickn33/agentic-awesome-skills47k1 repos~4kAutomated safety check: PassMIT

Similar skills

  • Export

    ai-analyst-lab/ai-analyst

    Export analysis results in different formats for different audiences — email summaries, Slack updates, decision briefs, Google Docs with embedded charts, Word documents, slide decks, or raw data CSVs.

    304 GitHub stars~3.8k tokensUpdated 7 days ago
    Documents & OfficeAuto-check passed
  • Notion Manual Import

    sickn33/agentic-awesome-skills

    Notion Manual Import: the Notion step for any module - CSV, property mapping, import steps and verification for the field list the active module confirmed.

    47k GitHub starsUsed in 1 repo~3.8k tokens
    Documents & OfficeAuto-check passed
  • Alumni Re Hire Tracker

    sickn33/agentic-awesome-skills

    Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request.

    47k GitHub starsUsed in 1 repo~3.4k tokens
    Documents & OfficeAuto-check passed
  • Announcement Board

    sickn33/agentic-awesome-skills

    Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request.

    47k GitHub starsUsed in 1 repo~3.4k tokens
    Documents & OfficeAuto-check passed
  • Asset It Management

    sickn33/agentic-awesome-skills

    Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request.

    47k GitHub starsUsed in 1 repo~4k tokens
    Documents & OfficeAuto-check passed
  • Attendance

    sickn33/agentic-awesome-skills

    Daily attendance register: check-in and check-out, hours worked, work mode, late minutes, leave and regularisation flags, as CSV, SQL, JSON Schema or Notion on request.

    47k GitHub starsUsed in 1 repo~3.5k tokens
    Documents & OfficeAuto-check passed

More from skrun-dev/skrun

All 14 skills in this repo
  • Adr Writer

    skrun-dev/skrun

    Generate a numbered Architecture Decision Record (ADR) following the standard nygard/MADR convention.

    210 GitHub stars~861 tokensUpdated 15 days ago
    Auto-check passed
  • Changelog Generator

    skrun-dev/skrun

    Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured .git-log.txt dump).

    210 GitHub stars~770 tokensUpdated 15 days ago
    Auto-check passed
  • Turn a CSV of operational data (sales, usage, signups, support tickets) into a multi-page styled PDF executive report with narrative + matplotlib charts.

    210 GitHub stars~1.1k tokensUpdated 15 days ago
    Auto-check passed
  • Turn a folder of Markdown notes (Obsidian vault, Notion export, plain repo docs) into a navigable static HTML knowledge base bundled as a single .zip file.

    210 GitHub stars~1.4k tokensUpdated 15 days ago
    Auto-check passed
  • Semgrep Rule Creator

    skrun-dev/skrun

    Generate a complete Semgrep rule bundle (rule.yml + tests.md + README.md) from a CVE description and a bad-code example.

    210 GitHub stars~1.3k tokensUpdated 15 days ago
    Auto-check passed
  • Receipts To Expenses

    skrun-dev/skrun

    Read a batch of receipt images directly via vision, classify each into expense categories, optionally reconcile against a bank statement CSV, and produce a multi-sheet Excel workbook + a PDF summary.

    210 GitHub stars~1.1k tokensUpdated 15 days ago
    Auto-check passed

Questions about Meeting Transcript To Action Items

What does Meeting Transcript To Action Items do?

Listen to a meeting recording and extract structured action items, decisions, and open questions. Meeting Transcript To Action Items is an agent skill from skrun-dev/skrun. Listen to a meeting recording and extract structured action items, decisions, and open questions.

When should I use Meeting Transcript To Action Items?

Meeting Transcript To Action Items fits situations like: given a meeting recording and asked for a recap; tasks that involve CSV and tabular files.

How do I install Meeting Transcript To Action Items in Claude Code?

Run `npx skills add skrun-dev/skrun --skill meeting-transcript-to-action-items -a claude-code`. Or copy the skill folder (agents/meeting-transcript-to-action-items in skrun-dev/skrun) into .claude/skills/meeting-transcript-to-action-items in your project. Claude Code loads it when a task matches its description.

How do I install Meeting Transcript To Action Items in Codex?

Run `npx skills add skrun-dev/skrun --skill meeting-transcript-to-action-items -a codex`. Or copy the skill folder (agents/meeting-transcript-to-action-items in skrun-dev/skrun) into .agents/skills/meeting-transcript-to-action-items in your project. Codex loads it when a task matches its description.

Can I use Meeting Transcript To Action Items 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 skrun-dev/skrun --skill meeting-transcript-to-action-items -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-transcript-to-action-items, .gemini/skills/meeting-transcript-to-action-items, .github/skills/meeting-transcript-to-action-items and .opencode/skills/meeting-transcript-to-action-items in your project.

What does Meeting Transcript To Action Items need to run?

Going by SKILL.md and its folder, Meeting Transcript To Action Items needs TypeScript for the scripts in its folder. Our summary lists: Node.js.

Does Meeting Transcript To Action Items 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 Transcript To Action Items 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Meeting Transcript To Action Items use?

Meeting Transcript To Action Items is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meeting Transcript To Action Items use?

About 1.3k tokens (SKILL.md is roughly 5.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 Transcript To Action Items?

Skills that share tags, products or a category with Meeting Transcript To Action Items: Export (ai-analyst-lab/ai-analyst, 304 stars), Notion Manual Import (sickn33/agentic-awesome-skills, 47k stars), Alumni Re Hire Tracker (sickn33/agentic-awesome-skills, 47k stars) and Announcement Board (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meeting Transcript To Action Items?

skrun-dev (a GitHub organization) maintains it in skrun-dev/skrun, which has 210 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 22, 2026.

Source: skrun-dev/skrun on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.