Define reusable Atoi instructions and authorize the external services they are allowed to use.
Skills and connectors solve different parts of repeatable work. A skill tells Atoi how to approach a class of request. A connector authorizes Atoi to read or act in a named external service. A skill can depend on connected tools, but enabling a skill does not create an external authorization.
Understand a skill
In Atoi, a skill is a per-user reusable instruction and workflow. Its stored definition can include a name, description, body, triggers, examples, output mode, allowed tools, step limit, category, and supporting resources. Resources can be references, scripts, or templates.
An enabled skill can be matched from its name or triggers during a chat. You can also choose Use in chat to start a conversation with the skill directly. Output remains in the resulting Atoi conversation or artifact mode defined by the skill.
Skills have two origins:
- Built-in or custom skills are managed in Atoi and can be enabled or disabled per user.
- Plugin-managed skills arrive through an installed governed plugin and follow that plugin's lifecycle.
The skills settings surface accepts supported Markdown, ZIP, or folder imports from the host or an upload. Imported definitions preserve source metadata and a content hash. Custom skills can be edited, reimported, disabled, or deleted. Plugin-managed skills are not edited individually; update or disable their plugin instead.
Connect external services
Open the connections settings surface to authorize a provider. The shipped connectors are:
- GitHub, for repositories, branches, issues, pull requests, and Git credentials. It uses either GitHub OAuth or the GitHub App installation path.
- Linear, for teams, projects, issues, comments, and planning operations.
- Slack, for authorized channel history, direct messages, app mentions, and assistant replies used as product context.
- Google Workspace, for Gmail context, calendar events and availability, and Drive files and documents.
Select Connect for the provider and complete its OAuth or installation flow. The browser returns to Atoi with either a connected state or a specific error. The authorization flow uses short-lived state protection and does not ask you to paste a long-lived personal token into a skill.
Connection health is explicit. A provider can be connected, limited, unhealthy, or revoked. Recheck an unhealthy connection before treating missing context as an empty result. Disconnecting removes Atoi's provider authorization; it does not delete data in the external service.
Keep channel delivery separate
The Slack connector described here supplies authorized workspace context and actions to Atoi chats, projects, and tasks. It is distinct from a Slack destination linked under Channels, where delivery is currently outbound-only. Connecting one surface does not expand the behavior of the other.
The same distinction applies to skills. A skill may name GitHub, Linear, Slack, or Google Workspace tools, but those tools are usable only when the corresponding connector is authorized and healthy.
Review before use
Before enabling an imported skill, inspect its instructions, allowed tools, step limit, and resources. Before connecting a provider, review the provider scopes and destination account. Then test the skill in a normal chat and confirm that its output links back to the expected thread or task.