# LAB11: build and evaluate the constraints skill

Allow 45–70 minutes. Use a new CP04 exercise folder and improve its shipped skill. Alternatively, start from preserved CP03, create the skill directory, `SKILL.md`, and reference yourself, then compare with a separately extracted CP04 reference. CP03 does not supply those skill files. Record the starting state and make one bounded description or missing-information improvement.

1. Confirm the `datasheet-to-constraints` directory and `SKILL.md` name. Inspect the YAML and relative reference path.
2. Read the procedure as if you were performing it manually. Check that inputs, steps, output columns, and missing-data behavior are explicit.
3. Start a new Codex task in the project root. Explicitly select the skill and submit the relevant source-extraction request. Save the prompt and actual output.
4. In another fresh task, run the relevant implicit request. Record whether the skill was selected, and evaluate the table independently of the selection claim.
5. Run the unrelated README request in a fresh task without naming the skill. Record whether the extraction workflow was inappropriately applied.
6. Run the chapter's refined course scenario: a different ESP32-S3 board, with no exact variant or schematic, using only that description and no additional sources. Check that the answer identifies the missing evidence rather than assuming product 5477.
7. Revise one demonstrated weakness, then repeat the affected tests. Keep the before/after records and avoid changing several variables at once.

Submit the skill, supporting reference, prompts, actual observations, and verdicts. Include interface/version, source scope, skill identity, and any limitations. If activation cannot be observed in the available interface, record what can be established and what remains uncertain; do not infer a pass from the final answer's tone.


## Evidence record

Record checkpoint, changed files, exact actions, actual results, and limitations. Preserve the starting exercise copy. Expected behavior is a criterion, not an observed run.