Write an importable Skill

Goal: turn a read-first project review into reusable instructions. Download the complete project-review ZIP and inspect it before import.

Open

View on GitHub

SKILL.md
references/
  checklist.md

The entry defines metadata and procedure; its checklist uses a relative path:

---
name: project-review
description: Inspect a workspace project and propose a verified, minimal change plan before editing.
---

# Project review

Use when the user asks to inspect a project or prepare a change plan.

1. Confirm the selected workspace. Read its README and applicable project instructions.
2. List relevant files using workspace tools. Never assume a shell path is the workspace.
3. Read `references/checklist.md` and inspect only files relevant to the request.
4. Report the current behavior, likely cause, proposed files and acceptance checks.
5. During this review, do not write files, install dependencies, run project scripts or contact remote services.
6. If the user has already authorized implementation, finish this read-only review, then continue within that authorization; do not ask for duplicate approval.

Report in the user's language. Distinguish observed evidence from assumptions. Never claim a test passed without running it.

# Project review checklist

- What outcome did the user request?
- Which files define the current behavior?
- What project instructions and runtime assumptions apply?
- Is there a reproducible failure or a missing requirement?
- What is the smallest useful change?
- Which existing test or observable behavior can validate it?
- Which parts remain uncertain?

Suggested report: current behavior, evidence, proposed change, acceptance checks, remaining questions.

Import and verify

1. Import and enable the ZIP in Skills; check its displayed name and description.
2. Select a test workspace and this Skill, then ask: “Review this project and propose a minimal change plan; this turn is read-only.”
3. Check that tool records show reads of SKILL.md and references/checklist.md.
4. Expect current behavior, evidence, proposed files, acceptance checks and uncertainties, with no workspace writes.

Skill metadata is shown first; content must be read when relevant. Seeing a name does not prove the procedure ran.

Adapt it

Change applicability and checklist for your task. Document environments, dependencies and verification for any script; import does not automatically install tools or execute code.

This example makes the review stage read-only. If the user already authorized implementation afterward, finish the review and continue within that authorization without duplicate approval. Skill text cannot expand user authorization or system capabilities.