digest
Extract insights from transcripts into actionable artifact files.
Best use case
digest is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Extract insights from transcripts into actionable artifact files.
Teams using digest should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/digest/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How digest Compares
| Feature / Agent | digest | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Extract insights from transcripts into actionable artifact files.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /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
```bash
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):
```bash
uv run --project ~/.claude/skills/digest digest --path /other/project list
```
### 2. Extract and analyze
For each session with new content:
```bash
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:
```bash
uv run --project ~/.claude/skills/digest digest note notes/digest/opportunities.md --project "project-name" "- Insight here [session_id:line]"
```
Or pipe multiple lines:
```bash
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:
```bash
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.Related Skills
ai-daily-digest
Daily AI news digest covering technical advances, business news, and engineering impact. Aggregates from research papers, tech blogs, HN, newsletters. Use daily for staying current on AI developments.
youtube-ai-digest
Browses AI-related YouTube videos from subscribed channels, fetches transcripts, generates summaries, and creates Markdown reports. Use when the user mentions YouTube AI videos, video summaries, channel subscriptions, or asks about recent AI content from YouTube creators.
ai-digest
Digest AI/tech articles into structured learning documents. Use when user says "digest this article", "/ai-digest", "analyze this AI news", or provides URL/content to summarize.
tech-news-digest
Generate tech news digests with unified source model, quality scoring, and multi-format output. Five-layer data collection from RSS feeds, Twitter/X KOLs, GitHub releases, Reddit, and web search. Pipeline-based scripts with retry mechanisms and deduplication. Supports Discord, email, and markdown templates.
api-digest
Use when user asks for digest ("дайджест", "саммари", "что нового", "digest", "summary") - fetches data via API and generates detailed analysis
analyzing-tdigest-metrics
Analyze percentile metrics (tdigest type) using OPAL for latency analysis and SLO tracking. Use when calculating p50, p95, p99 from pre-aggregated duration or latency metrics. Covers the critical double-combine pattern with align + m_tdigest() + tdigest_combine + aggregate. For simple metrics (counts, averages), see aggregating-gauge-metrics skill.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
frontend-responsive
Implement responsive designs that work across mobile, tablet, and desktop screen sizes. Use this skill when applying mobile-first development patterns, using responsive breakpoints, creating fluid layouts with percentage-based widths, choosing relative units (rem/em) over pixels, ensuring touch-friendly tap targets, or optimizing images for mobile. Applies when working on any frontend layout code, media queries, responsive utilities, and when testing UI across different screen sizes.
Frontend Responsive Design Standards
Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that works across all screen sizes. Use this skill when creating or modifying UI layouts, responsive grids, breakpoint styles, mobile navigation, or any interface that needs to adapt to different screen sizes. Apply when working with responsive CSS, media queries, viewport settings, flexbox/grid layouts, mobile-first styling, breakpoint definitions (mobile, tablet, desktop), touch target sizing, relative units (rem, em, %), image optimization for different screens, or testing layouts across multiple devices. Use for any task involving multi-device support, responsive design patterns, or adaptive layouts.
frontend-playbook
The complete build-to-production pipeline for Ethereum dApps. Fork mode setup, IPFS deployment, Vercel config, ENS subdomain setup, and the full production checklist. Built around Scaffold-ETH 2 but applicable to any Ethereum frontend project. Use when deploying any dApp to production.
frontend-patterns
Frontend development and API integration patterns for React, TypeScript, and state management
frontend-pages-components
Build responsive frontend pages, reusable components, layouts, and styling using modern best practices.