Convert a YouTube or podcast transcript into a stepped written tutorial with code blocks where the speaker references commands.
Reads a YouTube or podcast transcript (SRT, VTT, or plain text with timestamps) and produces a stepped, written tutorial. Each step that names a command, file path, or URL is rendered with a fenced code block and a back-reference to the timestamp.
transcript_path: SRT, VTT, or plain .txt with timestamps.topic: the tutorial subject (e.g., "Set up a Postgres replica with pgBouncer").video_url: used to render ?t=Xs deep links per step.HH:MM:SS,mmm --> HH:MM:SS,mmm./, ~, ./, or matching <verb> '<command>'. Quote-strip and lowercase.[<HH:MM:SS>](<video_url>?t=<seconds>) back-link at the end of each step.tutorials/<slug>.md where slug is derived from topic.tutorials/<slug>.md with: H1 (topic), Prerequisites bullet list, numbered steps with code blocks and timestamp anchors, Troubleshooting bullet list. Stdout reports step count and unmatched verb-cue lines.
Re-read the markdown and confirm every fenced code block is preceded by a verbal description in the step body. Spot-check three timestamp links by computing seconds from HH:MM:SS and confirming the math. If more than 30% of paragraphs produced no step boundaries, the transcript may be a discussion rather than a how-to — surface a warning rather than emit a hollow tutorial.
Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/transcript-to-tutorial.
Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Diff two OpenAPI YAML files and produce a backwards-compatibility changelog grouped into breaking, non-breaking, and additive changes.
Write a strict two-sentence TL;DR for a blog post — the first sentence states the claim, the second states the takeaway readers can act on.
Write a 600 to 800 word case study from a customer interview transcript structured as Problem, Solution, Impact, with named metrics and a single pull-quote.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.
Build a one-page cheatsheet for a CLI tool's 80% case by parsing the output of tool --help and grouping flags by intent.