---
id: M05-L03
title: "Package a repeatable procedure"
module: M05
chapters: "11"
checkpoint: CP03
---

# M05-L03 — Package a repeatable procedure

Package a focused procedure for deriving hardware constraints from primary material. Start with the source-checking practice from Module 4 and a preserved CP03 folder. The output is a valid skill file, a focused reference, and a static review.

Choose a skill only when the task needs a reusable sequence and judgment. A one-off request can remain a prompt. General project expectations belong in AGENTS.md. Deterministic transformations may belong in scripts. The constraints procedure needs exact-source identification, units and conditions, uncertainty handling, and reviewable output.

Create `.agents/skills/datasheet-to-constraints/SKILL.md`. YAML frontmatter contains the matching lowercase name and a concise description. The description should identify the task: deriving interface or operating constraints for an exact board or component from supplied primary documents. Exclude unrelated prose and general coding tasks.

Below the metadata, state inputs, steps, and output. Require exact part/board identity, publisher/title/revision when available, and relevant source sections. Separate chip limits from board connections. Preserve units, operating conditions, and the distinction between typical values and limits. Missing data should remain explicit.

The output table needs claim, value/unit, source section/link, confidence or missing data, and design consequence. A row whose source does not support its value is a failure even if the table looks polished. Require the agent to check each row and list only unresolved questions that affect the requested decision.

Add a focused `references/extraction-rules.md` explaining missing-information examples and source identity. Link it relatively from the skill root. Do not copy an entire manufacturer manual or add scripts merely to make the directory look substantial. The first version can be instruction-only.

Read the metadata and procedure independently. Valid frontmatter checks packaging; correct discovery and output require behavior tests in the next lesson. The shared Agent Skills format is distinct from Codex's local `.agents/skills` discovery and invocation behavior. Use the official references and the installed host's actual state when testing.

D10 shows the relationships between metadata, body, reference, and optional scripts. Explain why a missing pin mapping should produce an explicit gap and a next source request rather than a guessed number.

## Resources and completion

Use the Sensor Monitor `CP03` download and its `README.md`; project paths in this lesson are relative to that root. Read Chapter 11 for the full lab and explanatory review answers. Figure IDs: SS11-01, SS11-02, D10. Primary references: [OpenAI AGENTS.md](https://learn.chatgpt.com/docs/agent-configuration/agents-md) and [OpenAI build skills](https://learn.chatgpt.com/docs/build-skills). Complete the [exercise](exercise.md), preserve actual evidence, and use the separate instructor answer key for self-check after attempting the task. Narration scripts are production sources; final transcripts must match the actual narrated edit.