Skip to content
Theone Coleman.Shared openly.

// Practical lesson / Codex CLI or IDE extension

Create a resource-review skill.

Write a small instruction-only skill for checking a draft.

What you’ll make possible

Prepare and try a repeatable editorial review in a disposable Codex project.

A skill makes a repeatable workflow explicit. For this task the input is a draft, and the output is a list of claims needing evidence. It should neither rewrite the draft nor publish it.

Create .agents/skills/resource-review/SKILL.md inside the disposable project with this original example:

---
name: resource-review
description: Review a supplied resource draft for missing attribution and unsupported claims. Do not use for publishing.
---

Read only the draft and supplied sources. Return:
1. Claims supported by a specific source.
2. Claims that need evidence, especially usage, prices and benefits.
3. Missing creator attribution or unclear wording.
Do not invent evidence, edit files or publish anything.

// Your turn

Try this.

  1. Create the folder and SKILL.md above. Keep it separate from any existing operating instructions.

  2. In Codex CLI or the IDE, use /skills to check discovery, then explicitly mention $resource-review with a non-sensitive sample draft.

  3. Include an unsupported sentence such as “Everyone gets a discount” in the sample. The review should flag the missing evidence.

  4. Inspect whether it stayed within the requested review. Improve the instructions if it rewrote content or treated a claim as verified without a source. Model output still needs your judgement.

References & credits1 sources

Sources checked . Features and terms can change.