Creating a skill

A skill takes five minutes: a folder, a SKILL.md file with a YAML header, and clear instructions. No build step is required.

Anatomy of SKILL.md

---
name: meeting-followup
description: Parse meeting notes into decisions, open questions,
  and tasks with owners and deadlines.
version: 1.0.0
tags: [meetings, tasks, followup]
triggers_i18n:
  ru: ["разбери встречу", "итоги встречи", "задачи из встречи"]
  en: ["follow up on the meeting", "parse the notes"]
apply: on_demand
---

# Meeting follow-up

After a meeting, turn notes or a transcript into a structure,
create tasks, and optionally draft an email to participants.

## When to use

- The user asks to follow up on a meeting or create tasks from it.

## Steps

1. Get the meeting and linked notes.
2. Extract decisions, open questions, and actions.
3. Propose a task for each action with an owner and deadline.

Frontmatter fields

name and slug are the identifier; the folder name must match the slug.
description and when_to_use help the agent decide when the skill is relevant.
triggers_i18n contains activation phrases per language: { ru: [...], en: [...] }.
allowed_tools optionally restricts which tools the agent may call inside the skill.
apply: always | on_demand keeps the skill in context or loads it on demand.

Tips

Write clear numbered steps: the agent follows them in order.
List data sources and tools explicitly.
Add an example of a good result — it beats any adjectives.