presets

Creates and manages reusable Ava agent config presets via REST API and CLI.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill presets-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: presets
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/skills/ava-guide/presets
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill presets-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes references (resource) components.

What problem does it solve? Spawning agents with the same model, skill, and behavior settings repeatedly means re-writing config every time. This Skill lets you store those settings as named, reusable presets that seed an agent's config at spawn time. ## Core Features & Use Cases - Preset CRUD: Create, list, view, update, and delete named config templates through the REST API (/api/presets) or the ava presets CLI. - Config design guidance: Explains per-agent config fields like llm_model, skills_to_expand_at_start, and skills_to_inject_into_system_prompt, including fork rules and override semantics with config_overlay. - Role card authoring: A reference guide explains how to build a role (e.g., product manager) as a be-a-<role> skill and wire it into a preset. - Use Case: You need a reusable "reviewer" agent type. Create a preset naming the model and preloaded skills, then spawn agents with preset="reviewer" instead of passing full config each time. ## Quick Start Ask the agent to create a new preset named my-preset with a chosen model and preloaded skills, then verify it with ava presets ls.

Frequently Asked Questions about presets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a reusable agent config preset?▼

Create a preset by POSTing to /api/presets with a name, label, description, and config object, or run ava presets create with the same fields. The config holds per-agent fields like llm_model and skills_to_expand_at_start.

What is the difference between a preset and config_overlay?▼

A preset is the named base config stored in the cluster, while config_overlay fields passed at spawn are precise per-key overrides. The preset itself travels inside the overlay as config_overlay={"preset": "name", ...}.

How do I create a new agent role like a product manager?▼

Author the role as a skill named be-a-<role> under $AVA_HOME/skills, register it with ava skill register, then create a preset whose config lists it in skills_to_expand_at_start. The preset only names the card; the role text lives in the skill.

Can a preset restrict which skills an agent can use?▼

No. The cluster default indexes every loaded skill, so skills_to_inject_into_system_prompt in a preset can only narrow the listing, not block access. Any skill still loads by name via ava.help, so it buys attention, not a capability boundary.

Why does my preset fail with an invalid model error?▼

The llm_model value must be an id on the current model registry, not a name copied from old docs. List valid ids with GET /api/models or check shared/lm/registry.py before setting the field.

When should I use a preset versus a one-off config_overlay?▼

Use a preset only when the config combination will be reused across multiple spawns. For a one-off agent, pass config_overlay directly at spawn time instead of creating a named template.