Skills

A skill is a written procedure that clients and agents read and follow: how your team writes a weekly report, how to file a bug in your tracker, what to check before a release. A tool server gives a client new tools; a skill tells it how to do something well.

What a skill is made of

• A folder with a file SKILL.md. Its frontmatter has a name and a description (up to 1024 characters): the description says when the skill applies, and clients read it to decide whether to open the skill.
• Further files beside it, if it needs them: up to 100 files of up to 256 KiB each.
• A name of 2 to 48 characters.

A tool server can bring skills of its own (at most 10, shown as <server>-<name>) and link up to 20 skills from the library.

Write one

1. In Studio, open More to make and choose New skill.
2. Say under What it is for what the skill should teach.
3. Click Write it in a chat. Your assistant drafts it with you.

The next steps show on the skill’s page: Read the draft, then Publish version 1; until it is accepted it says Waits for your OK.

From a client with Authoring on, the same goes with studio__create_skill, then studio__write_file, then studio__propose. A skill needs no build. The skill skill-authoring tells the client how.

Using skills

• A skill reaches a client through its profile: add it under Skills on the profile page, or find it under Browse and use Add to profile. See Profiles.
• In the chat, type / to use one.
• Clients read the skills of their profile with skills__list and skills__get.
• Your organisation can give skills to people through Servers & skills policies, as recommended or required.

Publishing and versions

Like a tool server, a skill has versions, and its editors publish them. Who may find it beyond you needs an approval; who approves is set by your organisation’s Approvals policies.