Skip to main content

Create and add a skill

Start with a small task: turn meeting notes into an action list. The input is the meeting record; the output contains actions, owners, deadlines, and supporting text. Mark missing information as unconfirmed.

Create SKILL.md

Use stable, descriptive folder and skill names.
---
name: meeting-actions
description: Use when asked to extract actions, owners, and deadlines from meeting notes.
---

# Extract meeting actions

1. Read the supplied notes. Request the original record if missing.
2. Extract explicit follow-up actions and preserve their supporting text.
3. Record owners and deadlines; mark unspecified values as unconfirmed.
4. Merge duplicate actions and retain conflicts for confirmation.
5. Return a table with action, owner, deadline, and evidence.

Add resources

Put required output templates in assets/ and reference their paths in the instructions. Place longer rules in references/ and load them only when relevant. Add scripts only when needed.

Load and validate

Open Extensions → Skills → Add skill and follow the client's available import method. Run a task that matches the description. Check that the skill is used, resources are readable, output fields are complete, and every action has evidence. Test locally before submitting to the marketplace. Next: check the specification, prepare a self-test report, then publish the skill.