yao-agent

DevOps Community

Repo stars 7,542
Author repo yao

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Agent management expert. ALWAYS invoke this skill when you need to list available agents, download or reference agent source cod…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “agentlist”, “agentdownload”, “agentreference”, “agentdeploy”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name yao-agent directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “agentlist / agentdownload / agentreference” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Agent Tools

Five tools for managing agents on the host, called via bash.

agent_list

List available agents. Returns ID, name, description, and capabilities for each agent.

tai tool agent_list '{}'
tai tool agent_list '{"namespace": "smith"}'

Parameter	Type	Required	Description
`namespace`	string	no	Filter by namespace (e.g. `yao`, `smith`). Omit for all.

agent_download

Download a smith-namespace agent into the development directory for editing. Restricted to smith namespace only — for other agents, use agent_reference.

tai tool agent_download '{"id": "smith.weather"}'

Parameter	Type	Required	Description
`id`	string	yes	Agent ID in dot notation. Must be `smith.*`.

Downloaded code lands in agent-smith-dev/assistants/smith/<name>/.

agent_reference

Download agent source code from the host into .references/ for read-only study. Any agent across all namespaces can be referenced.

tai tool agent_reference '{"id": "yao.slides"}'
tai tool agent_reference '{"id": "yao.keeper"}'

Parameter	Type	Required	Description
`id`	string	yes	Agent ID in dot notation (e.g. `yao.slides`)

Referenced code lands in agent-smith-dev/.references/<namespace>/<name>/.

agent_deploy

Deploy agent source code from the sandbox development directory to the host. Restricted to the smith namespace only — attempts to deploy to other namespaces will be rejected.

tai tool agent_deploy '{"id": "smith.weather"}'
tai tool agent_deploy '{"id": "smith.weather", "message": "add SUI page"}'

Parameter	Type	Required	Description
`id`	string	yes	Agent ID in dot notation. Must use `smith` namespace.
`message`	string	no	Optional deploy message for logging.

agent_connectors

Get the current user's LLM connector matrix. Returns metadata for each role (default, heavy, light, vision, etc.) without API keys. Use this to understand which models are available and their capabilities.

tai tool agent_connectors '{}'

No parameters required.

Guidelines

Use agent_list to discover agents before downloading or referencing
agent_download is for editing smith agents — code lands in agent-smith-dev/assistants/smith/<name>/
agent_reference is for studying any agent — code lands in agent-smith-dev/.references/<namespace>/<name>/
Deploy is restricted to the smith namespace for safety
Connector data never includes API keys, secrets, or tokens
All output is JSON

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: DevOps
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @YaoApp · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview yao-agent.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Agent Tools

Five tools for managing agents on the host, called via bash.

## agent_list

List available agents. Returns ID, name, description, and capabilities for each agent.

```bash
tai tool agent_list '{}'
tai tool agent_list '{"namespace": "smith"}'
```

| Parameter   | Type   | Required | Description                                              |
|-------------|--------|----------|----------------------------------------------------------|
| `namespace` | string | no       | Filter by namespace (e.g. `yao`, `smith`). Omit for all. |

## agent_download

Download a **smith-namespace** agent into the development directory for editing. **Restricted to `smith` namespace only** — for other agents, use `agent_reference`.

```bash
tai tool agent_download '{"id": "smith.weather"}'
```

| Parameter | Type   | Required | Description                                              |
|-----------|--------|----------|----------------------------------------------------------|
| `id`      | string | yes      | Agent ID in dot notation. Must be `smith.*`.             |

Downloaded code lands in `agent-smith-dev/assistants/smith/<name>/`.

## agent_reference

Download agent source code from the host into `.references/` for **read-only study**. Any agent across all namespaces can be referenced.

```bash
tai tool agent_reference '{"id": "yao.slides"}'
tai tool agent_reference '{"id": "yao.keeper"}'
```

| Parameter | Type   | Required | Description                                        |
|-----------|--------|----------|----------------------------------------------------|
| `id`      | string | yes      | Agent ID in dot notation (e.g. `yao.slides`)       |

Referenced code lands in `agent-smith-dev/.references/<namespace>/<name>/`.

## agent_deploy

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> agentlist → agentdownload → agentreference → agentdeploy → agentconnectors → Guidelines
terms    -> smith-namespace · Restricted to smith namespace only · read-only study · Restricted to the smith namespace only · without API keys
files/cmd -> namespace · yao · smith · agentreference · smith. · agent-smith-dev/assistants/smith/<name>/ · .references/ · yao.slides
body sha256 -> 71c7c5f6a6b5