Use when you want to see how a skill is structured. Example content — replace with your own team's conventions (API handlers, migrations, review rules, deploy steps…).
Installs into .claude/skills of the current project.
Are you the author of Example Skill?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/plantik-example-skill)
---
name: example-skill
description: Use when you want to see how a skill is structured. Example content — replace with your own team's conventions (API handlers, migrations, review rules, deploy steps…).
---
# Example Skill
A skill is a focused set of instructions an agent loads **on demand** via
`get_skill`. The `description` in the frontmatter is what the agent sees in
`list_skills`, so write it as a trigger: *"Use when …"*.
## When to Activate
- The agent is about to do the kind of work this skill covers
- A project page or task file points at this skill by name
## Rules
1. Keep rules concrete and checkable — "handlers return JSON errors as
`{ "error": "<message>" }`", not "handle errors well".
2. Show one good code example per pattern.
3. Put long or rarely-needed material in `references/` so the main skill stays short.
## Example Pattern
```ts
export default defineEventHandler(async (event) => {
const body = await readBody(event)
if (!body?.title) {
throw createError({ statusCode: 400, message: 'title is required' })
}
return createTodo(body.title)
})
```
## References
- `anti-patterns` — things to avoid (load with `get_skill_reference`)
