Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

3.11.1 How to author SKILL.md

SKILL.md has two parts: frontmatter and body instructions. Frontmatter tells Moss what the skill is called, when to use it, and how risky it is; the body explains how to execute it.

Full template

---
name: my-skill
description: One-line explanation of purpose
version: 1.0.0
trigger: keyword1,keyword2,keyword3
risk: low
permissions: device_exec
delegate_preference: board
requires_board: true
approval_level: none
cooldown_seconds: 0
scheduler_template: none
category: Custom
---

# Skill title

## When to use
(Scenarios where this skill applies)

## Execution flow
(Step 1 → step 2 → ...)

## Tool mapping
(Which Studio tools or board commands to use)

## FAQ / pitfalls
(Known issues and workarounds)

The YAML block bounded by --- is frontmatter—you only need to fill it in using the template.

Key fields

FieldRequiredMeaning
nameYesUnique skill name; prefer short English or romanized identifiers
descriptionYesOne sentence—the strongest signal Moss uses to choose the skill
versionNoSemantic version (for example 1.0.0)
triggerYesComma-separated keywords; boosts priority when matched
riskYeslow / medium / high
permissionsYesTools the skill expects to call
delegate_preferenceNolocal (PC), board, or hybrid
approval_levelNoWhether user confirmation runs before execution
requires_boardNoMust a board-attached session exist
categoryOptionalGroups skills in UI

How risk changes behavior

ValueMoss behavior
lowLightweight tasks—fewer confirmation prompts
mediumCall out planned actions before running
highRequires an explicit Allow click before continuing

Prefer conservative labeling. Board tuning, deletes, restarts deserve medium or high.

Markdown bodies are flexible, but structuring helps Moss parse reliably:

SectionContent
When to useComplements description with timing cues
Execution flowNumbered procedural steps
Tool mappingStudio tools and shell snippets
FAQ / pitfallsErrors, remediation, escapes

Avoid long prose blobs—numbered steps parse more reliably.