Extract insights from transcripts

VerifiedSafe

Process raw transcript logs from AI coding sessions and extract structured insights into organized markdown files in notes/digest/. Helps when you have long conversation logs and need to capture optimization ideas, unresolved items, research leads, completed work, and learned preferences.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#transcript-analysis#note-taking#insights-extraction#cli-tool#artifact-generation

Recommended for

Automated summary

Extracts actionable insights from transcript logs and organizes them into structured artifact files.

Strengths

  • Automatically categorizes insights into multiple files (opportunities, loose ends, etc.)
  • Includes source session references for full traceability
  • Simple CLI with dedicated commands (list, extract, note, mark)
  • Handles timestamps and note formatting automatically

Limitations

  • Requires a specific transcript format with session IDs
  • Manual marking of processed sessions can be forgotten
  • Only processes already recorded transcripts, not live streaming
When to use it

After a conversation session to capture key ideas, action items, and learnings.

When not to use it

When transcripts are not available in the expected format or you need real-time note-taking.

Security analysis

Safe
Quality score88/100

The skill instructs running a dedicated CLI tool with well-defined subcommands (list, extract, note, mark) and fixed arguments. No arbitrary shell execution, file deletion, or external network calls. The commands are confined to a local project directory and handle user input as arguments, not shell-injectable.

No concerns found

How this analysis is made

Examples

Process latest transcript
Run the digest skill on the latest transcript session. First list unprocessed sessions, then extract insights from the newest one, and add notable entries to opportunities and loose ends files.
Extract and note specific session
Use digest to process session abc123: extract its content, add any research ideas to research-backlog.md, and mark the session as processed.
Bulk extract all new transcripts
Run digest list to see unprocessed sessions, then extract each one and add findings to the appropriate artifact files. Report a summary of what was added.

name: digest description: Extract insights from transcripts into actionable artifact files.

/digest

Process raw transcript logs and extract insights directly into artifact files.

Output Files

All in notes/digest/:

| File | What to extract | |------|-----------------| | opportunities.md | Optimization ideas - "could improve", friction points, repeated manual work, better approaches mentioned | | loose-ends.md | Open items - TODOs not done, questions unanswered, "need to" without resolution | | research-backlog.md | Future directions - "interesting", "worth exploring", novel techniques | | blog-grist.md | Significant work completed, problems solved, patterns discovered | | things-learned.md | Preferences, environment facts, workflow learnings |

Instructions

1. Find unprocessed transcripts

uv run --project ~/.claude/skills/digest digest list

If output is "Nothing new to process", stop here.

Use --path <dir> to specify a different base directory (defaults to cwd):

uv run --project ~/.claude/skills/digest digest --path /other/project list

2. Extract and analyze

For each session with new content:

uv run --project ~/.claude/skills/digest digest extract <session_id>

This outputs cleaned message text (user/assistant only, no metadata).

What to look for (include source ref [session_id:line] for each item):

Opportunities (opportunities.md):

  • "could improve", "should optimize", "better way"
  • Friction, repeated steps, workarounds
  • Failed approaches that revealed a gap

Loose ends (loose-ends.md):

  • TODOs not completed in the session
  • Questions raised but not answered
  • "Need to" / "should" without resolution

Research backlog (research-backlog.md):

  • "Interesting", "worth exploring"
  • Techniques mentioned but not tried
  • Links/references saved for later

Blog grist (blog-grist.md):

  • Significant work completed
  • Problems solved in interesting ways
  • Patterns or insights that emerged

Memories (things-learned.md):

  • User preferences ("I prefer...", "don't like...")
  • Environment facts (paths, configs, tools)
  • Workflow patterns to remember

3. Add notes

Use the note command to add entries. It handles timestamp and formatting automatically:

uv run --project ~/.claude/skills/digest digest note notes/digest/opportunities.md --project "project-name" "- Insight here [session_id:line]"

Or pipe multiple lines:

echo "- First insight [abc123:42]
- Second insight [abc123:55]" | uv run --project ~/.claude/skills/digest digest note notes/digest/opportunities.md --project "myproject"

The CLI prepends entries with a timestamp from date '+%Y-%m-%d %H:%M'.

4. Mark processed

After extracting insights from a session:

uv run --project ~/.claude/skills/digest digest mark <session_id>

5. Report

Brief summary:

  • Sessions processed: N (X new lines)
  • Items added: Y opportunities, Z loose ends, etc.

Keep it short. The artifacts speak for themselves.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/extract-insights-from-transcripts-mm78nofd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/extract-insights-from-transcripts-mm78nofd/download' --output '.skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md.part' && mv '.skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md.part' '.skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md' && test -s '.skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/digest' && cp -R '.skill-downloads/extract-insights-from-transcripts-mm78nofd' '.claude/skills/digest'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/extract-insights-from-transcripts-mm78nofd'

openskills read 'extract-insights-from-transcripts-mm78nofd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/extract-insights-from-transcripts-mm78nofd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills