Skip to content
AtoiDocumentation
Use Atoi

Skills

Teach Atoi how you want a kind of work done, and keep a skill separate from the connections it uses.

Open in Atoi
A skill holds instructions and tool access, the connection it uses is a separate grant, and the receipt names what ranA skill holdsinstructions and triggersexamples it learns fromthe tools it may usea step limitIts owner sets the rulesbuilt in, yours, imported, or a pluginAConnectiona separate grantBApprovalfor a consequential writeReceiptnames what ran and changedturning one on never creates the otherread an imported skill before you enable it
A skill is instructions. A connection is authorization. One never creates the other.

A skill is a set of instructions for a repeatable kind of work. A connection is an authorization to use a service. Turning one on never creates the other.

#What a skill holds

A name, a description, instructions, triggers, examples, the tools it may use, a step limit, and any references or templates. Built-in, custom, imported, and plugin-managed skills have different owners and editing rules.

#Review before you enable

Open Settings → Skills to review your own and synced skills. Use Import to add a skill, then read its instructions, triggers, tool access, and source before enabling it. A plugin-managed skill updates with its plugin. It is not a local copy you edit.

From the terminal:

bash
atoi skill list --json
atoi skill view <skill-id> --json
atoi skill disable <skill-id> --json

Removal needs --confirm.

#Skills use connections

A skill can ask for GitHub or Linear work, but the matching connection has to be healthy and in scope. A healthy connection still shows an approval for consequential writes. The receipt names which capability ran and what it changed.

Read Tools next for how Atoi chooses among the skills and tools it has.

Was this useful?