Files
cp1-agents/docs/source-material/agent-shapes/agent-pattern/agent.yaml
Jonathan Boniface 416c66ced4
All checks were successful
check agents / check (push) Successful in 10s
Add CP1 Discovery agents in both patterns
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>
2026-10-29 18:25:57 +00:00

89 lines
3.5 KiB
YAML

# Who this agent is and what it offers.
#
# This file is the agent: the runtime reads it at startup and builds the agent
# from it -- its instructions, contract, tools, skills and hooks. There is no
# app/agent.py. The agent card, the agent catalog and the logs all show what it
# says. Nothing here is read from environment variables. Edit it, redeploy, and
# refresh the agent in the catalog.
# The agent's unique identity. Changing it renames the agent in the
# catalog when it is refreshed at the same URL.
name: "expense-policy-agent"
# How the agent is shown in the catalog. Optional: without it, the name is
# shown. Generated from the name; change it freely -- it is not an identity.
display_name: "Expense Policy Agent"
# Shown in the catalog and the workflow palette. Write it for someone
# deciding whether this agent does what they need.
description: "Reviews an expense claim against the travel and expense policy and decides it, naming the rule applied and who must approve."
# Bump it when you ship a change callers should notice; it is how two builds of
# one agent are told apart in the catalog. The agent pipeline tags the image
# with it and will not release a version twice, or one without its entry in
# RELEASE_NOTES.md.
version: "1.0.0"
# The framework the agent runs on, set by the template it came from. It must
# match the runtime image the Dockerfile builds on (agent-runtime-adk).
framework: adk
# What the agent is about, for searching and filtering the catalog.
tags:
- expenses
- finance
- policy
- skills
# A2A capabilities.
# streaming replies arrive as they are generated
# push_notifications the agent can call the client back when a task finishes
capabilities:
streaming: true
push_notifications: false
# What the agent can do. Two forms, and they can be mixed:
#
# - review-claim a skill folder, skills/review-claim/SKILL.md: the
# instructions and tools for one way of doing the
# agent's job. The model loads it when it fits the
# request. See skills/README.md.
# - id: ... name: ... an advertised skill: listed on the agent card and in
# the catalog, and nothing more.
#
# Skills never change what the agent accepts or returns: its contract (below),
# or free text when it has none, holds whichever skill is used. The first skill carries them on
# the agent card.
#
# An advertised skill has:
# id stable identifier, lower case with underscores
# name short human title
# description what the skill does, for someone choosing it
# tags what it is about
# examples example requests, e.g. a JSON payload matching the input schema
skills:
- review-travel-and-meals
- review-purchases
# The instructions, relative to this file.
prompt: prompt.md
# What the agent accepts and returns, checked on every request: JSON Schemas in
# schemas/. A reply that breaks the output schema is sent back to the model
# once, then refused. Without a contract the agent takes and returns free text.
contract:
input: schemas/input.json
output: schemas/output.json
# The agent's own functions the model may call, each `module:function`. Write
# them in app/tools.py.
functions:
- app.tools:lookup_policy_rule
- app.tools:convert_currency
- app.tools:request_approval
- app.tools:get_policy_rule
# The agent's own code around each request and each model call: pre_process,
# post_process, before_model and after_model in app/business_logic.py.
hooks: app.business_logic