SKILL.md file. Register skills once under Settings → Skills, then attach them by name when you create an agent.
Registering a skill
Open Settings → Skills, pick a starter skill from the catalog, or add your own GitHub/GitLab repository (URL, optional path, and ref). Pin a tag or commit SHA for production stability.What a skill contains
SKILL.md has YAML frontmatter (name, description) and a markdown body of instructions. The description is what the agent sees upfront; the full body and supporting files load only when the agent picks the skill (progressive disclosure).
Runtime requirements
Skills require the agent’s sandbox to be enabled. The skill repository is cloned into the sandbox, and the
agent reads
SKILL.md (and can run bundled scripts) there. Two skills cannot share the same name on one agent.- The harness exposes each attached skill’s name and description.
- When the model decides a skill is relevant, the repo is materialized under
/opt/tfy/skills/{name}. - The agent follows
SKILL.mdand uses supporting files as needed.
Skills + MCP tools
- Skills define how to handle a task (procedure, decision logic, formatting).
- MCP tools provide the actions and data to execute it.
Authoring tips
- Keep the
descriptionsharp — it is the only thing the model sees before loading the skill. - Write
SKILL.mdlike instructions to a competent teammate. - Put heavy reference material in supporting files the skill links to.
- Prefer several focused skills over one sprawling pack.