Skills

Skills are reusable instruction packages that teach Anyy how to perform a specific workflow. A Skill can include a SKILL.md, supporting files, and a command that appears in compatible chat surfaces.

Skill sources

Dashboard groups Skills by origin:

Source	Meaning
System	Bundled with Anyy; visible but not user-toggleable or removable
User Installed	Installed into the selected Profile's managed Skills root
Agent Created	A managed provenance label shown when an existing Skill record was created by an agent-capable workflow

Skills are Profile-scoped. Another Profile has its own catalog and enabled state.

You can install a Skill from Dashboard or ask Anyy to install a specified source in a conversation. When skill_manage is available to that conversation, it writes the selected Profile's managed library. Dashboard and CLI use that same library.

Install through a conversation

Give Anyy the path to a trusted local .zip package accessible on its host, and ask it to install the Skill. After installation, refresh Dashboard → Skills and inspect its source, enabled state and contents.

The reverse path also works: install from Dashboard, then ask Anyy to use that Skill in the same Profile. The next prompt can discover the reloaded catalog and read the installed SKILL.md; an already running prompt keeps its admitted context. A success message alone is insufficient if the Skill is missing from the page or cannot be read in the conversation.

Inspect a Skill

Open Dashboard → Skills, then select a Skill to review:

• ID, name, description, and scope;
• source category and managed state;
• enabled or disabled state;
• rendered SKILL.md content;
• file path; and
• linked supporting files.

Read the instructions before enabling or installing a third-party Skill. A Skill can influence what Anyy is asked to run and which tools it selects.

Enable or disable

Use the toggle on a non-system Skill. Disabling removes it from normal resolution without deleting its files. Re-enable it when you want it available again.

Reload the catalog after out-of-band file changes. The next prompt uses the updated catalog; an already admitted prompt keeps its instructions. Check the enabled state separately: replacing a disabled Skill does not imply enabling it.

Install from Dashboard

Select Install Skill and upload a local .zip containing exactly one Skill: either a top-level SKILL.md with its supporting files, or a single Skill directory.

The complete upload request, including multipart overhead, must fit within 10 MiB. The ZIP and its extracted content also have a 10 MiB limit. Validation rejects path traversal, symlinks, special files and entries outside the staging root. The SKILL.md name must be at most 64 lowercase letters/digits joined by single hyphens, such as release-notes; it cannot be a path. Use that name for the enclosing directory when present. Installation replaces an existing managed Skill with the same name.

The resident Skills service checks the upload ID, SHA-256 and expiry in the selected Profile, applies the package, and reloads the catalog. Installation accepts local ZIP packages only. GitHub sources, remote URLs, local directories and collection installation are unsupported; historical source metadata on existing Skills remains available.

Treat Skills as code-level trust

Review the package instructions, requested commands, external downloads, and referenced files before installing. Archive validation checks package structure; you remain responsible for deciding whether to trust its instructions.

Remove a Skill

Select Remove Skill on the detail page to remove a managed Skill from the selected Profile and reload its catalog. System Skills cannot be removed from Dashboard.

CLI management

The CLI installs a local ZIP file accessible to the Anyy host. It uses the same managed library and archive validation as Dashboard.

anyy skills list
anyy skills view weather
anyy skills install ./weather.zip
anyy skills uninstall weather
anyy skills rollback weather
anyy skills reload

Useful options:

• --force replaces an existing managed Skill;
• --now requests a Gateway reload after an offline mutation; resident RPC mutations already reload the catalog;
• --revision ID rolls back to a specific immutable revision; and
• --json returns machine-readable output.

Without --revision, rollback selects the previous managed revision. Offline mutation is allowed only when the Profile is not owned by a resident Anyy runtime; without a running Gateway the files are discovered on its next startup. Conversation mutations normally reload too; if skill_manage uses reload:false or reports reload_error, run a reload before relying on the next catalog.

Use a Skill

Type /skills in the TUI or / in Dashboard Chat to browse the live catalog. Installed Skills can add canonical commands. The exact list depends on the selected Profile, surface, platform, and enabled state.

Troubleshooting

Problem	Fix
Install fails	Check the source or upload error and confirm the selected Profile
Skill does not appear in chat	Confirm the same Profile and enabled state, inspect reload errors, then submit a new prompt with an available read or bash reader
ZIP is rejected	Check the Skill name and one-Skill layout, remove symlinks/path escapes, and leave room for multipart overhead within 10 MiB
Uninstall or rollback is blocked	Use the resident workflow, or stop Anyy before an offline mutation
System Skill cannot be toggled	System Skills are managed by the Anyy release

Keep capability configuration on Tools; a Skill does not grant tools or permissions by itself.