Skill

structure-transcript

Add section headers, logical groupings, and paragraph breaks to a cleaned transcript, while preserving the speaker's wording. Use when the user asks to structure a transcript, add headers, organize by topic, or make a transcript readable without rewriting it.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-transcription

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Reorganize a cleaned transcript into a readable document with headers and sections — without paraphrasing.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 19, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Structure transcript

Reorganize a cleaned transcript into a readable document with headers and sections — without paraphrasing.

Input

Preferably <stem>.cleaned.md. Falls back to raw if cleaned is unavailable (warn user that fillers will remain).

What to do

Identify topic shifts and thematic groupings.

Insert markdown headers (##, ###) naming each section descriptively.

Merge fragmented paragraphs on the same topic.

Split overly long paragraphs at natural breaks.

Preserve every content word.

What NOT to do

Do not paraphrase or reword

Do not drop content

Do not add information the speaker didn't say

Do not insert editorial commentary

Output convention

<source_stem>.structured.md

Example transformation

Before:

So we started the project in January and the first thing we did was set up the infrastructure. That took about three weeks. Then we moved on to the API layer which was actually the hardest part because we had to integrate with the legacy system.

After:

Project Timeline

Infrastructure Setup (January, ~3 weeks)

So we started the project in January and the first thing we did was set up the infrastructure. That took about three weeks.

API Layer

Then we moved on to the API layer which was actually the hardest part because we had to integrate with the legacy system.