ClaudeSkills
All guides

ClaudeSkills guide

Check the file, then the claim

A checked example has a defined scope. Reproduce the fixture, inspect the exported artifact and test your own task before treating a workflow as production-ready.

Updated 2026-10-04

Understand the verification label

A source can be official without its workflow having been executed here. In this directory, “not tested” means no execution result is claimed. The first-party examples labelled “fixture checked” cover an included deterministic tool running on its included sample input, with artifact inspection. That check does not measure Claude or Codex reasoning quality or guarantee behavior on arbitrary inputs.

Reproduce the supplied example

Use the same package revision, fixture and declared runtime as the example. Compare the actual outputs with the stated file formats and content structure. If the tool cannot run, record the missing dependency or error before changing the input; otherwise you can lose track of what the original check established.

Inspect the exported artifact

A command finishing is one signal, not the entire review. Open documents and check sections, text and links; view images at their intended size and inspect edges or transparency; play videos and check dimensions, duration and legibility. Review factual content and intended use separately from technical file validity.

  • The output opens in the intended viewer and has the expected format.
  • Dimensions, sections, duration and included resources match the task.
  • The factual and creative review is recorded separately from the tool check.

Run a small version of your own task

Change the input to a representative case from your project and define what a good result should contain. Keep the package revision, input and output together with your review notes. Broaden a verification claim only after you have evidence for that broader scope; a polished preview alone is not that evidence.

Related reading