yao-agent

Name: yao-agent
Author: YaoApp

DevOps Community

Repo stars 7,542
Author updated Live
Author repo yao

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: DevOps
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @YaoApp · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

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

---
name: yao-agent
description: Agent management expert. ALWAYS invoke this skill when you need to list available agents, downlo…
category: devops
runtime: no special runtime
---

# yao-agent output preview

## PART A: Task fit
- Use case: Agent management expert. ALWAYS invoke this skill when you need to list available agents, download or reference agent source code, deploy agent code to the host, or query the LLM connector matrix. Do not guess agent structures — use this skill first..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “agentlist / agentdownload / agentreference” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent management expert. ALWAYS invoke this skill when you need to list available agents, download or reference agent source code, deploy agent code to the host, or query the LLM connector matrix. Do not guess agent structures — use this skill first.”.
- **02** When the source has headings, the agent prioritizes “agentlist / agentdownload / agentreference” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: yao-agent
description: Agent management expert. ALWAYS invoke this skill when you need to list available agents, downlo…
category: devops
source: YaoApp/yao
---

# yao-agent

## When to use
- Agent management expert. ALWAYS invoke this skill when you need to list available agents, download or reference agent…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “agentlist / agentdownload / agentreference” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "yao-agent" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> agentlist / agentdownload / agentreference
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

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 / write; 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

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add YaoApp/yao/tools/skills/yao-agent -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
YaoApp/yao
中文

Category & tags

Category DevOps