Import a skill into Avery
2 min · 5 steps
Pick the skill folder, preview the translation, confirm. The new agent lands in /agents.
The Import skill… button on the Agents page opens a wizard. Step one picks the skill folder (anything with a SKILL.md at its root). Step two lets you rename the resulting agent + opt into a cloud translation (recommended — produces higher-quality DSL). Step three shows the parsed manifest + a list of warnings / skipped files; you click Import as agent to commit.
Steps
- Open the Agents page.
Sidebar → Agents. Click 'Import skill…' in the header (next to the existing 'Import' agent-export button).
- Pick the skill folder.
Avery opens a folder picker. Select the directory containing SKILL.md. Common locations: ~/.claude/skills/<name>/ (personal Claude Code skill) or any `git clone`'d skill repo.
- Confirm the agent settings.
The 'Agent name' field seeds from the manifest's `name`. Leave Use a cloud model for the one-time translation checked unless you have a specific reason — local-model translation tends to drop nuance from the SKILL body.
- Review the preview.
Avery shows the parsed manifest, any warnings (skill name too long, missing description, etc.) and any files we skipped (Python scripts, shell scripts, binary bundles — V1 doesn't run those at agent runtime).
- Click 'Import as agent'.
Avery commits the import + drops you into the new agent's Builder tab. From here it's a regular Avery agent — edit nodes, change the trigger, run it.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.