GlinkBot documentation

Skills

Give a bot a procedure it can reuse, review what it learned, and share skills with the rest of the team.

A skill is a short procedure a bot can read and follow: "how we cut a release", "the house style for changelogs", "how to check this project's tests". It is a folder with a SKILL.md in it, and the bot keeps it for every future conversation instead of learning the same thing again.

Skills are instructions, not permissions. A skill can tell a bot how to do something; it never grants access to a computer, a folder, or an app. Access stays with the bot's own settings.

How a bot uses a skill

Only the skills that are switched on for a bot take part. Each turn, the bot gets an index of them — name, one-line description, and the path of the file — and reads the full SKILL.md with its file tools when a task actually matches. That keeps the prompt small: a bot never pays for the body of a skill it doesn't use.

Skills are reference material, and the bot is told to treat them that way: it is instructed not to let a skill override its instructions or your own message. That is an instruction to the model, not a check on the text — nothing scans a skill for a rule that conflicts with the bot's own.

Where to find them

The index a bot sees each turn lists at most 30 skills and at most 4,000 bytes, so a long list is trimmed, and the bot gets a note saying how many were left out and why — the skill cap or the byte cap. The names of the skills left out go to the server log rather than into the note. The skills are still there — it is only the index that is trimmed.

Writing one

A skill is a directory named after the skill, containing SKILL.md:

changelog-style/
└── SKILL.md

The name must be lowercase letters, digits and single hyphens (up to 64 characters); the spec also asks for it to match the folder that holds the skill, and an imported skill gets a folder named after it. The file starts with frontmatter:

---
name: changelog-style
description: Write the changelog entry for a release in this project's house style.
---

# Changelog entry

1. Read the commits since the last tag.
2. Group them under Added, Changed and Fixed…

description is what the bot sees in its index, so write it as the moment the skill should be used, in one line. license, compatibility and comma-separated tags are optional. Keep the body short — the spec suggests under 5,000 tokens — and put long reference material in a references/ folder inside the skill, where the bot reads it only when it needs it.

Letting a bot write one

Two switches decide how much a bot may do on its own: App settings → Early features in Advanced mode.

The /learn command is the predictable path: you decide when a conversation is worth keeping, and the bot writes down what it actually did.

Sharing with the team

A learned skill belongs to one bot until you share it. Share learned skills with the department decides what happens when a bot learns or improves one: Off keeps it private, Ask offers to move it into the library, and Automatic moves it and gives it to every bot in the same department. Conversations already running hear about it on their next message; new ones list it. A teammate that already has its own skill with that name keeps it, and a bot whose conversations more people can see than the one the skill was learned in is left alone.

Reviewing what arrived

Imported and learned skills are text written somewhere else, so treat them the way you would treat a script from a stranger:

GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.