/createskills
GuideAI builders

SKILL.md template

A practical SKILL.md template for agent workflows

Start with a focused trigger, a short workflow, and references that the agent can inspect only when the task calls for them.

Direct answer

A good SKILL.md template names the skill, describes when to use it, lists the workflow, defines output expectations, and points to references without dumping everything into one prompt.

Last updated May 4, 2026
Reviewed by createskills editorial

Start with a narrow trigger

The description is the most important part of the file. It should say exactly when the skill helps and when it should stay out of the way.

Keep instructions operational

Write the body as steps the agent can follow. Avoid vague goals like "be strategic." Name the inputs, decision points, output format, and verification checklist.

Reference files deliberately

Use references/ for source material, examples, templates, or long notes. SKILL.md should point to those files and tell the agent when to open them.

Test the skill against real prompts

A skill is only useful if it activates for the right requests. Test it with specific prompts, vague prompts, and unrelated prompts, then tighten the description.

Workflow

Template workflow

  1. 1Name one repeatable job the skill should perform.
  2. 2Write a trigger description with the most important keywords first.
  3. 3List the workflow as numbered steps.
  4. 4Add references and examples only where they reduce ambiguity.
  5. 5Run a real task and edit the skill based on the result.
Starter SKILL.md
---
name: landing-page-review
description: Use when reviewing a SaaS landing page for positioning, clarity, proof, and conversion issues.
---

## Workflow
1. Read the page copy and identify the intended buyer.
2. Compare claims against references/customer-research.md.
3. List the top conversion risks before suggesting rewrites.

## Output
Return findings first, then a concise rewrite plan.

FAQ

Questions people ask

What belongs in the description?

Put the trigger use case first, then the boundaries. The description helps the agent decide whether to load the skill.

How long should SKILL.md be?

Keep it as short as possible while still specifying workflow and output. Put long source material in references/.

Where do references go?

Use references/ for supporting documents, examples, source captures, transcripts, PDFs, and longer notes.

How do I test a skill?

Run a real task that should use it, then run one that should not. Tighten the description and workflow based on behavior.

Keep exploring

Related workflows

Try it with your own sources

Turn the next useful web page into reusable AI context.