Skills and plugins

Skills preserve repeatable working methods. Plugins provide installable capabilities and connections. Decide whether you need a method or a tool before adding one.

Choose a capability

A plugin may contain skills or expose MCP tools. Installing a skill does not connect the accounts it depends on.

Check before installing

Review the source, instructions, dependencies, and access scope. Identify what it reads, whether it creates or sends content, and whether it uses paid services.

Browse the directory or installed list in Extensions, add the capability, and enable it. Complete account sign-in or credential setup where required.

Confirm readiness

1. Open plugin details and inspect its source and status.
2. Configure required accounts or local dependencies.
3. Save, test the connection, and inspect the actual tool list.
4. Try a small read operation before using write tools.

Installed, connected, and able to complete a task are different states. A connected service remains subject to account permissions and the task's authorization.

Create a skill

Start with work you have already performed and can verify repeatedly. Describe purpose, trigger, inputs, steps, output, and acceptance checks. Add templates, references, or scripts when useful.

Try a real small task before refining it. For example: “Create a weekly briefing from project records, organized into progress, risks, and next steps, with source links.”

Follow the current skill-management interface for directories and imports rather than copying another product's personal configuration paths.

Maintain or disable

Disable a capability temporarily, or use its removal control when available. Built-in capabilities may only offer enable and disable.

Removing a local plugin does not delete remote data or revoke service-side authorization. Review the external account's grants when retiring a connection.

Next: MCP servers · Subagents · Using plugins