Design, validate, and export SKILL.md

Turn repeatable AI workflows into clean skill files.

Drafts stay in this browser unless you copy, download, import, or export them.

How it works

Workflow, materials, and checks

7/7Readiness checks complete
  • SKILL.md descriptionAdd a one-line description so agents know when the skill applies.
  • Trigger conditionsList at least two situations where this skill should be used.
  • Required inputsName the context an agent should gather before starting.
  • Workflow depthUse at least four ordered steps so execution is repeatable.
  • Expected outputTell the agent what final artifact or answer to return.
  • GuardrailsAdd constraints that prevent overreach, guessing, or unsafe behavior.
  • Reference materialOptional but recommended: include examples, code, or source notes.

Generated result

SKILL.md preview

code-review/SKILL.md
---
name: code-review
description: Review code changes for correctness, risk, and missing tests.
---

# Code Review

## Purpose

Help an agent inspect a pull request or patch and return concise, actionable findings before any summary.

## Audience

Software engineers and agents reviewing application code.

## When To Use

- User asks for a review
- User shares a diff, pull request, or changed file set
- User asks for risk assessment before merge

## Required Inputs

- Changed files or diff
- Relevant tests or build output
- Product requirements or acceptance criteria
- Known risky modules

## Workflow

1. Read the changed files and nearest tests
2. Identify behavior changes and user-visible risk
3. Check edge cases, error handling, and data contracts
4. Verify whether tests cover the changed behavior
5. Return findings first with file and line references

## Reference Materials

Use these notes, examples, or code snippets when they are relevant:

```text
Findings should be ordered by severity.
Use this shape:
- [P1] Title - file:line - why it matters - suggested fix
```

## Output

A prioritized review with findings first, then open questions, then a short change summary.

## Guardrails

- Do not mention unrelated style issues unless they hide a defect.
- Do not approve risky changes without evidence from tests or code.