---
name: deliverable-preflight-skill
description: Check a created or revised file, slide deck, image, web page, interactive tool, or learning resource before delivery. Use when the task includes producing an artifact or reviewing whether it is ready to share.
license: CC0-1.0
metadata:
  author: Miguel Guhlin
  version: "1.0.0"
---

# Deliverable preflight

Check the actual final artifact against the user's intended use. Focus effort on failures that would prevent someone from using it.

## Choose relevant checks

Identify the audience, format, and important acceptance criteria from the request. Ask only about missing information that materially affects delivery. Use the available tools; do not prescribe a particular vendor or runtime.

- Documents and slides: open or render the result when possible. Inspect small text, clipping, page breaks, contrast, image proportions, and links. Check that downloads contain the intended pages and that speaker-only material stays in the intended presenter deliverable.
- Interactive tools and websites: try the main task and a realistic empty or invalid input. When browser tools exist, check keyboard use, a narrow viewport, feedback, and any save or export feature. Verify that the exported file opens and contains the user's work.
- Images and diagrams: inspect labels, factual relationships, reading order, and any requested alt text. Do not claim an image was visually inspected if you only examined its filename or metadata.
- Lessons and quizzes: solve the questions independently. Check that directions, answer keys, examples, and success criteria agree. Avoid giving away an answer before the learner has a chance to try.

## Correct and deliver

Fix relevant problems within the authorized task, then recheck the changed behavior. Verify that the final file exists and that its link or download path resolves. If inspection tools are unavailable, do the checks that are possible and say which meaningful checks remain.

Report the delivered result, the checks actually performed, and any limitation that affects use. Do not label an artifact tested, accessible, compliant, or production-ready based on a checklist alone. Do not add a long test report to a simple delivery unless it helps the user assess the result.

Practice requests and pass criteria: [eval.md](eval.md).
