ava-guide

Explains the ava CLI for operating clusters, agents, MCP servers, packages, presets, and schedules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating an Ava deployment requires knowing which CLI command family handles which job, and the mental model behind clusters, units, machines, agents, and channels. This Skill maps the entire ava CLI so an agent can operate the deployment itself without guessing at commands or misusing development workflows. ## Core Features & Use Cases - CLI command map: Routes operational tasks to the right sub-skill covering ops, MCP servers, packages, agents, presets, models, workspace cleanup, and onboarding. - Operations vs development split: Distinguishes running the cluster (ava-guide) from modifying its code (ava-modification-layers and ava-self-development), preventing dangerous shortcuts like editing the production checkout. - Design intent guidance: Explains why capabilities live as skills and CLI commands rather than SDK functions, so operators work with the grain of the system. - Use Case: An agent asked to add an MCP server, switch the update channel, or spawn a worker on a specific model loads this skill to find the correct sub-skill and command family before acting. ## Quick Start Load the ava-guide skill and follow its sub-skill table to find the right operational guide for your task.

Frequently Asked Questions about ava-guide

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

FAQPage Schema
How do I operate an Ava cluster with the ava CLI?▼

Run ava commands through the shell, using ava --help for the full command list and ava <cmd> --help for details. The ava-guide skill maps each operational task, such as cluster lifecycle, MCP servers, or packages, to the sub-skill that covers it.

What is the difference between operating Ava and modifying Ava?▼

Operating Ava means running the deployment through the ava CLI: starting clusters, installing packages, managing agents. Modifying Ava means changing its code, which follows the ava-modification-layers and ava-self-development skills through a PR, CI, merge, and cluster update flow.

How do I add an MCP server to Ava?▼

Use ava mcp add with a JSON spec or command flags, then call its tools as ava.mcps.<server>.<tool>. Configuration is machine-level, and a newly added server connects the next time one of its tools is called without a restart.

Can I edit Ava production source code directly and reload it?▼

No. Directly editing the production checkout or switching its branch with git checkout breaks new agent startup and is explicitly forbidden. Code changes must go through PR, CI, merge, and ava cluster update.

How do I choose a model when spawning an Ava agent?▼

Pass config_overlay with llm_model at spawn time, choosing from the live roster returned by GET /api/models or the registry. The current policy defaults to deepseek-v4-flash for all workers unless the user explicitly requests another registered model.