Package the input requirements, instructions, example, checks, and recovery notes together. A portable instruction kit is a starting point; a tool-specific Skill also needs its supported format and installation method.
In this guide
Save the actual inputs and checks
- A short purpose statement and intended reader.
- Required input fields and permitted source material.
- Ordered task instructions and the expected deliverable.
- A small original example input and a reference output.
- Review checks and what to do when a file or fact is missing.
- Environment, version, and account requirements for the chosen tools.
What should the saved kit contain?
Package the repeated job so another operator can run it. Replace the input file for the next product without hiding the expected output or review rule.
| File | Content |
|---|---|
| instructions.md | Fit-writing request and required outputs |
| inputs/TRAY-S.md | P1 dimensions and P2 packing-list question |
| examples/fit-reference.md | Fit answer retaining the open parts question |
| checks.md | Dimensions unchanged; no borrowed bundle claim |
Use a simple folder layout
task-kit/ README.md # Who this serves and how to begin input-template.md # Required fields and source IDs instructions.md # Ordered steps and stop conditions example-input/ # Original teaching/sample files reference-output/ # Clearly labeled comparison material review-checklist.md # What a person must verify run-notes.md # Version, dates, failures, review decision
Run one fresh task from the saved pack
- Give the pack to someone who did not assemble it, or follow it from a fresh working folder.
- Check whether the input requirements and execution location are understandable without the old chat.
- Keep the run's output and failures together. Correct instructions where the handoff was ambiguous.
- Record a version when the procedure or tool requirements materially change.
When should it become a tool-specific Skill?
Choose the actual supported environment first, then follow that tool's file structure, metadata, installation, and invocation requirements. Keep external software and credentials under the user's control.
A Markdown prompt alone is a portable instruction, not proof of installation compatibility with every AI tool.
References
Continue the task
Choose a reusable format and keep the observed corrections and costs with the procedure.