Transcript steps

Extract ordered instructions without losing prerequisites or warnings.

Turn the supplied instructional transcript into a short, usable procedure.

Start with Objectives: a few bullets describing what the procedure achieves, each within 15 words. Then provide Instructions as a numbered list. Preserve the order shown in the transcript. Give each step one main action and use simple, concrete language.

Keep the required tools, quantities, settings, conditions, checks, and warnings. Place a warning before the action it affects. Remove greetings, sponsorship, repetition, and demonstrations that add no necessary instruction.

Do not silently repair gaps by inventing steps. Mark a missing prerequisite or unclear instruction briefly where it matters. Preserve exact commands and identifiers. Return the objectives and procedure without extra commentary.

Example

Fictional route-validation tutorial

Before 140 words

Hello and welcome to this walkthrough. Today we will validate a copy of a route file before anyone uses it for dispatch. You need the route-check tool and the supplied routes.csv file. First, copy routes.csv to routes-review.csv, because we are going to use the copy rather than change the original. Please be careful here: replacing the original would overwrite the source data, so keep the original file. Next, run route-check routes-review.csv --strict. That is the command shown on the screen, and I will repeat it: route-check routes-review.csv --strict. If it exits with a nonzero status, read route-check.log and stop the procedure. Do not mark the file approved after a failed check. If the command exits with status 0, rename routes-review.csv to routes-approved.csv. That is the end of the procedure; this walkthrough does not upload the file or dispatch any routes.

After 92 words

Objectives - Validate a route-file copy without changing the original. - Mark the copy approved only after a successful check. Instructions 1. Have route-check and the supplied routes.csv available. 2. Keep the original routes.csv; replacing it would overwrite source data. 3. Copy routes.csv to routes-review.csv. 4. Run route-check routes-review.csv --strict. 5. If the exit status is nonzero, read route-check.log. 6. If the exit status is nonzero, stop without approving the file. 7. If the exit status is 0, rename routes-review.csv to routes-approved.csv. 8. End the procedure without an upload or route dispatch.

Examples illustrate the method. They do not measure model output.

Files and sources

prompt.txt Complete prompt as plain text.
SKILL.md The same prompt with a skill header.
llms.txt (JSON) Prompt, metadata, example, and sources.
LICENSE MIT license text.

Adapted from Fabric · extract_instructions. Source notes.