Skip to content
Skills Library
Personal productivity · Writing

transcripted-summarize

/transcripted-summarize

Create cited summaries, recaps, briefs, daily reviews, weekly reviews, and "what did I do" answers from Transcripted meetings and dictations. Use when the user asks to summarize one capture, a date range, a person, a project, a topic, or mixed meeting and dictation history.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create cited summaries, recaps, briefs, daily reviews, weekly reviews, and "what did I do" answers from Transcripted meetings and dictations. Use when the user asks to summarize one capture, a date range, a person, a project, a topic, or mixed meeting and dictation history.

Triggers from the description

what did I do
Original author description

Create cited summaries, recaps, briefs, daily reviews, weekly reviews, and "what did I do" answers from Transcripted meetings and dictations. Use when the user asks to summarize one capture, a date range, a person, a project, a topic, or mixed meeting and dictation history.

How it works

  1. Purpose
  2. Workflow
  3. Default Output
  4. Rules
  5. Quality Check
Original SKILL.md headings · 62 lines, 303 words
SKILL.md preview
---
name: transcripted-summarize
description: Create cited summaries, recaps, briefs, daily reviews, weekly reviews, and "what did I do" answers from Transcripted meetings and dictations. Use when the user asks to summarize one capture, a date range, a person, a project, a topic, or mixed meeting and dictation history.
---

# Transcripted Summarize

Version: 0.1.0

## Purpose

Turn Transcripted meetings and dictations into a clean brief that preserves source traceability. Treat raw transcript and dictation text as the source of truth.

## Workflow

1. Resolve scope first: one meeting, one dictation, a date range, a person, a project, a topic, or mixed captures.
2. Prefer Transcripted MCP tools when available. Fall back to local meeting and dictation markdown files only when MCP is unavailable.
3. Read the relevant source material before summarizing. For a named meeting, read the full meeting when possible.
4. Filter obvious junk: test captures, accidental fragments, setup chatter, and empty or near-empty recordings.
5. Normalize relative dates in the user's local timezone and state the exact dates searched.
6. Summarize with source filenames, dates, speakers, and timestamps when available.
7. Surface uncertainty instead of guessing.

## Default Output

Use these sections when relevant:

```md
## Brief

## Main Threads

## Decisions

## Action Items

## Open Questions

## Risks / Blockers

## Worth Remembering

## Sources

## Uncertainty
```

## Rules

- Do not invent owners, deadlines, decisions, or action items.
- If an owner, deadline, or status is missing, write `unknown`.
- Separate decisions from action items.
- Keep the brief short unless the user asks for depth.
- Cite the source meeting or dictation for important claims.
- When summarizing multiple captures, group repeated themes instead of repeating every similar note.
- If no useful content is found, say so and list what was checked.

## Quality Check

Before answering, check:

- Every decision or action item is grounded in source text.
- Dates are absolute when the user used relative time.
- Unclear speaker names, noisy audio, or missing transcript spans are called out.
- The answer does not expose unrelated sensitive details from other captures.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named transcripted-summarize.

Database snapshot: 13.11.2026 · package version 6bc59b1f2453 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100transcripted-search-memory
    Search Transcripted meeting and dictation history for what was said, when it happened, who mentioned it, where an idea came from, or how a topic changed over time. Use for memory, recall, provenance, timeline, source-finding, and "what did I say about" questions.
  • 95superwhisper
    Find and read the user's own meetings and dictations recorded by the Superwhisper app on this Mac, through the local read-only `superwhisper` CLI — list and search meetings, read summaries, private notes and speaker-attributed transcripts, search dictation history, build recaps,…
  • 100summarize-transcripts
    Generate AI summaries for downloaded YouTube transcripts. Use when you want to add summaries to existing transcript files, batch process transcripts for summarization, summarize a channel's videos, generate frontmatter summaries, or when the user mentions summarize, AI…
  • 100p-activity-digest
    Summarize recent communication activity from Slack and meeting recordings. Use when the user wants to know what happened on Slack, review meeting action items, find mentions, or get a communication summary. Triggers on "summarize Slack", "meeting action items", "what was…
  • 100blurt-dictation-review
    Review the user's own recent Blurt dictations (kept audio + what was typed) to find recognition, polish, punctuation and formatting errors, judge each one, save the real ones as Dictation Lab cases, and turn them into fixes measured on the growing case set. Use when the user…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.