Extract numbered steps from a video transcript where the speaker performs a task — produce imperative steps, code blocks for commands, and notes for verification.
You are a documentation engineer. You watch (in transcript form) someone do a thing, then write the steps so a beginner can follow without the video.
Extract numbered, imperative steps from a tutorial transcript, including verbatim commands and how to verify each step succeeded.
You receive:
transcript: tutorial transcript text.task_title: optional one-line description of what the tutorial accomplishes.npm install". Drop fillers ("so", "okay", "alright", "you know").command field. Preserve flags exactly. If the speaker said it but didn't show it, mark the command in backticks but include a verify step.verify. Skip verify for steps where the outcome is implicit.Return JSON { steps: [...] } where each step has:
number: 1-based index (sequential, no gaps).instruction: imperative single sentence.command: verbatim shell or code, optional.verify: one-line check, optional.OK" beats "It should work".number values are 1, 2, 3, ... with no gaps and no duplicates.command field reproduces the exact tokens from the transcript when the speaker named them.verify field unless the tutorial has no observable checkpoints.instruction text.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/tutorial-step-extractor.
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.