Skills, MCP and API

Skills plugin

Save a procedure once and let Chetty load the right instructions when a later task matches.

The optional skills plugin adds the skill picker in chat, the skill manager under Settings → Plugins → Skills, and the ListSkills, SkillLoad, CreateSkill and DeleteSkill tools. See Skills for the file format and how to write a good one.

Find and load a skill

In web or terminal chat, type / and choose a skill by name and description, or open the picker with /skills. Typing /<skill-name> loads the same instructions, and any text after it travels with the request.

If a skill's name collides with another command or is longer than 32 characters, use /skills or /skill:name. Load a skill in chat covers paging through a long skill and asking for input.

Create, edit or delete a skill

Open Settings → Plugins → Skills to add, edit or delete reusable instructions. A saved skill applies from the next message, without restarting Chetty, and an already-running turn is not rewritten.

Names, scopes, supporting files and the editor are described in Create and edit a skill.

Who can use a skill

A personal skill belongs to one account and appears only in that account's conversations. An instance skill is shared across the installation. Bundled skills are read-only.

The plugin is grant-gated: an account without a linked identity sees no skills from it, and skills contributed by other enabled plugins appear in the same catalog. A contributed skill is available only when its plugin is enabled and, if that plugin is user-grantable, granted to the account.

A skill describes a procedure; it never gives the account new permissions, and slash aliases and loading still honor plugin grants and tool policy. Changes to plugin grants, plugin availability or skill ownership appear in the catalog on a later turn. Administrators manage instance-wide skills and, where appropriate, other accounts' custom skills; everyone else manages their own personal skills.

Install and grant the Skills plugin

Install skills from Settings → Available plugins. The marketplace checks the minimum core version declared by the installed release.
Open Users, select the account and choose Manage under Granted plugins.
Select skills and save.

Note: There is no administrator bypass, so an administrator needs the same grant too. Account tool policy can still deny SkillLoad on its own.

Automatic learning from completed work needs a matching core release, so upgrade Chetty and Skills together. Enabling, disabling, installing or changing a plugin restarts Chetty; saving a skill does not. The plugin has no configuration fields.

Skills the assistant proposes

Chetty can learn from long tasks and offer a new skill afterwards. Switch it on under Account → Memory, and turn it off there at any time.

A new skill is an ordinary personal skill, marked as created by the agent.
There is no approval step: it is offered exactly like a skill you saved yourself.
An existing agent-created skill is improved only when it was loaded in that exchange and has not changed since.

What counts as a task worth reviewing, the administrative limits and the cost model are in Skills from completed work.