Create a skill
for one useful job.

Choose a task you can describe clearly.

Good skills solve a specific, repeatable problem: review a pull request, prepare a release, turn notes into a brief, or check a page for accessibility. Avoid starting with “make the agent better.” Name the input, the work, and the expected output.

Keep the first version small.

Put the canonical instructions in a directory named after the skill. For a public repository you want Skilly to discover, use skills/<skill-name>/SKILL.md. Only add supporting files when they make the workflow easier to repeat.

your-repo/
└── skills/
    └── accessibility-review/
        ├── SKILL.md
        └── README.md

Give the agent a reliable path through the work.

Use YAML frontmatter at the top. Give the skill a recognizable lowercase, hyphenated name and a description that says what it does and when to use it. Then organize the instructions around decisions and actions. Prefer concrete steps, examples, and expected outputs over general advice.

---
name: accessibility-review
description: Review a web interface for keyboard access, semantics, focus states, and readable contrast.
---

# Accessibility review

## Use this skill when
The user asks for an accessibility review of a web page or component.

## Workflow
1. Inspect the relevant files and identify the page boundaries.
2. Check semantics, keyboard access, focus states, and contrast.
3. Report findings with a concrete fix and a way to verify it.

## Output
Return findings grouped by severity, followed by verification steps.

Use an agent to draft the first version.

Give the agent enough context to make a scoped, reviewable change. This prompt asks it to clarify the job, create the files, test the result, and explain its decisions.

Create a skill named [skill-name] for [agent harness].

The skill should help an agent [specific outcome]. Use it when [trigger or request].

Before writing files:
1. Ask any questions needed to define the scope.
2. Propose the folder structure and explain the tools or permissions required.
3. Keep the skill focused on one repeatable job.

Then create the files in [target directory]. Write SKILL.md with valid YAML frontmatter,
clear step-by-step instructions, examples, expected output, and explicit safety boundaries.
Add a README with install and usage notes. Test the skill against [sample task], show the
result, and list anything that should be reviewed before publishing.

Review it like a small piece of software.

Run the skill against a real but bounded task. Check the agent’s work and revise ambiguous instructions before sharing the repository.

• The trigger is specific enough that an agent can recognize it.
• The workflow has a clear start, finish, and expected output.
• Tool use, permissions, network access, and destructive actions are explicit.
• A sample task produces useful results without hidden context.
• The repository contains no secrets or private data.

Publish your repository, then check the listing.

Skilly indexes public skill repositories into its directory; there is no separate submission form. A public repository with a discoverable skill file can be imported during the next successful catalog refresh.