Skills: procedures Starko loads only when they apply

A skill is a procedure for Starko's agents, written like an article and kept in the Knowledge Hub. Starko loads a skill only when it applies to what you asked, so you can give it dozens of detailed procedures without slowing every conversation down. Skills work in Ask Starko (⌘L), in Slack, in MCP-connected tools and in coding sessions.

skills list

The Skills page

Open Knowledge Hub → Skills. Each row shows the skill's name and slug, when to use it, which surfaces it is available in, its published version and when it last changed. New skill starts a blank one; Import from GitHub pulls skills from a repository in the common skills//SKILL.md layout.

Anatomy of a skill

Name and slug. The slug is how you call it with / in chat or $slug in a project's agent instructions.

When to use. One or two sentences Starko reads to decide whether the skill applies. Be specific about the situation, not the steps.

Instructions. The body: steps, rules, examples, templates. Markdown with headings, lists, code blocks and tables.

Files. Scripts, templates and reference documents bundled with the skill. Coding sessions get them on disk; chat can run bundled scripts with your approval.

Available in. ⌘L chat, Slack, Coding sessions and MCP, each switchable.

Projects. Limit a coding skill to the projects it belongs to.

Drafts and publishing

Editing a skill changes its draft. Agents only ever read the published version, so nothing you type takes effect until you press Publish. Each publish creates a numbered version you can compare and roll back to.

skill new

Using a skill

In chat, type / and pick the skill, or just ask; Starko picks matching skills itself.

In a project's Agent instructions, write $slug to attach the skill to every coding session in that project.

In Slack, $slug in a message does the same.

Team rules live in skills

When an owner or admin tells Starko a standing rule ("always answer customers in their language"), Starko offers to save it as a team rule inside the skill it belongs to. Rules are published immediately and apply to everyone. See Team rules and personal memory.

Turning an article into a skill

Open an unpublished article and choose Turn into skill from its menu. The article body becomes the instructions; add the "when to use" line and publish.

Good skills

One situation per skill. "Refund requests" and "Chargebacks" are two skills.

Start the instructions with the outcome, then the steps.

Put examples of good and bad output at the end.

Keep the body under a few thousand words; move reference material into bundled files.

Did this answer your question?