We build.
We create.
We evaluate.

Inspect. Inspect factual support, relevance, completeness, tone, and internal consistency. Track changes to the brief, persistent constraints, and places where an answer quietly substitutes an easier task. Compare the explanation that is actually provided with the evidence available to the reader.

Verify. Trace each requirement to the response. Check claims against sources or supplied context, compare alternative answers on the same dimensions, and distinguish an incorrect statement from an unsupported one. Test whether a correction carries through the next turn.

Return. Return a clear preference or rubric judgment, the passages that support it, the consequence of each issue, and a specific correction. Keep uncertainty visible when the available evidence cannot settle the question.

Inspect. Read the skill’s scope, triggers, prerequisites, and completion requirements. Examine tool selection, arguments, execution order, instruction conflicts, handoffs, and recovery after failures. Check whether the workflow uses the right information at the right point.

Verify. Connect the brief to the visible execution trace. Confirm that commands ran in the intended environment, required files exist, and verification supports the completion claim. Exercise a missing dependency or ambiguous input to see whether the workflow recovers coherently.

Return. Provide a trace-backed explanation of where the workflow succeeded or broke down. Revise the relevant SKILL.md instructions, tool steps, or checks so another run has a clearer path to a verifiable result.

Inspect. Inspect setup instructions, dependency assumptions, commands, diffs, interfaces, and error handling. Look for missing edge cases, accidental changes outside the task, and code that depends on an undocumented local state. Review whether the tests exercise the requirements.

Verify. Reproduce the setup in a clean environment when the task calls for it. Run relevant checks, inspect generated files, and try meaningful boundary and failure cases. A passing test is useful evidence; its value depends on what the assertion proves.

Return. Hand over a reproducible issue, the command or input that exposes it, expected and observed behavior, and a focused repair. Include the revised code and verification notes when implementation is part of the work.

Inspect. Inspect source relevance, publication context, conflicting accounts, missing qualifications, and the relationship between conclusions and evidence. Review calculations, table labels, units, denominators, and whether a chart accurately represents the underlying values.

Verify. Open the cited material and trace important claims to the passages or data that support them. Recalculate consequential totals, compare sources with different perspectives, and separate observations from interpretations. Check time-sensitive statements against the requested date or period.

Return. Produce a source map, corrected claims or calculations, and concise notes explaining the strength and limits of the evidence. Organize the result so another person can follow the references and reproduce the important checks.

Inspect. Inspect required sections, slide count, narrative progression, repeated or contradictory claims, and the relationship between headlines and evidence. Review hierarchy, text size, contrast, chart units, source notes, alignment, and consistency across the deck.

Verify. Compare the slides with the source material and the stated audience. Read the sequence without presenter commentary, inspect charts against their data, and check exports at realistic viewing sizes. Confirm that the editable file and final export contain the intended content.

Return. Return slide-specific annotations with reasons and concrete changes: a clearer headline, a missing source, a corrected chart, or a reordered argument. Where useful, prepare revised slides or alternative layouts that address the identified issue.

Inspect. Review scene organization, objects, scale, geometry, normals, modifiers, UVs, and material relationships. Inspect lighting, camera framing, external textures, and render or export settings. Relate technical issues to visible effects and the requirements of the brief.

Verify. Check the file with its expected dependencies, inspect the relevant views, and reproduce the required render or export. Confirm that source changes appear in the delivered result and that the receiving person has the assets needed to continue working.

Return. Provide an annotated inspection, the affected objects or settings, and a prioritized list of fixes. When revision is included, deliver the updated scene, required assets, and a clear account of what was checked in the final output.