All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
67 lines
2.7 KiB
Markdown
67 lines
2.7 KiB
Markdown
# Skills
|
|
|
|
Each folder here is a way this agent does its job, in the Agent Skills format
|
|
(agentskills.io/specification, the open format ADK implements). The model
|
|
reads every skill's name and description, loads the one that fits the request,
|
|
and follows its instructions. Empty is fine: an agent with no skill folders
|
|
works exactly as it did before skills existed.
|
|
|
|
Skills are internal to the agent. They do not change what it accepts or
|
|
returns:
|
|
|
|
- An agent with an input and output schema (`contract:` in agent.yaml,
|
|
`schemas/input.json` and `schemas/output.json`) keeps that one contract
|
|
whichever skill it uses.
|
|
Every skill must produce the agent's output.
|
|
- An agent without schemas takes text and answers in text, whichever skill it
|
|
uses.
|
|
|
|
Callers never choose a skill. Work that needs a different input or output is a
|
|
different agent, not another skill.
|
|
|
|
```
|
|
skills/review-travel-and-meals/
|
|
├── SKILL.md name, description and the instructions (below)
|
|
├── assets/examples.json example requests shown on the agent card (optional)
|
|
└── references/ files the skill may read on demand (optional)
|
|
```
|
|
|
|
```markdown
|
|
---
|
|
name: review-travel-and-meals # lowercase letters, digits and single hyphens; same as the folder
|
|
description: Review a claim for travel, meals or lodging ... Use for any claim whose category is ...
|
|
metadata: # string values only, as the specification requires
|
|
agent.tools: lookup_policy_rule convert_currency # the agent's tools, space-separated
|
|
agent.tags: expenses travel
|
|
---
|
|
The instructions: how to do the job this way, step by step. They are loaded
|
|
only when the model picks this skill.
|
|
```
|
|
|
|
The description is how the model chooses, so say what the skill is for and
|
|
when to use it. The folder is a standard Agent Skill:
|
|
`agentskills validate skills/review-travel-and-meals` accepts it.
|
|
|
|
Then list the folder in `agent.yaml`:
|
|
|
|
```yaml
|
|
skills:
|
|
- review-travel-and-meals
|
|
```
|
|
|
|
What you get:
|
|
|
|
- The agent card lists each skill (name, description, tags, examples).
|
|
- The model loads a skill's instructions only when it needs them, and reads
|
|
its references on demand.
|
|
- A skill's tools can only be used once that skill is loaded. Tools no skill
|
|
names are always available.
|
|
- Every choice is logged as `skill_selected`, with the skill, the model's
|
|
reason and the run's id.
|
|
|
|
Put the functions a skill uses in `app/tools.py` and list them under
|
|
`functions:` in agent.yaml (`app.tools:<name>`); an MCP tool the agent declares
|
|
under `mcp:` can be named too. A skill that names a tool the agent does not
|
|
have stops the agent at startup, with a message naming it.
|
|
`scripts/` inside a skill is not supported yet.
|