Add CP1 Discovery agents in both patterns
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>
This commit is contained in:
2026-10-29 18:25:57 +00:00
commit 416c66ced4
331 changed files with 33561 additions and 0 deletions

View File

@@ -0,0 +1,66 @@
# 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.

View File

@@ -0,0 +1,35 @@
---
name: review-purchases
description: Review an expense claim for a purchase -- software, licences, subscriptions, equipment or anything that is not travel, meals or lodging -- and decide who must approve it under the company's delegation of authority. Use for any claim whose category is software or other.
metadata:
agent.tools: lookup_policy_rule convert_currency request_approval
---
Review the claim in these steps, in order.
1. Call `lookup_policy_rule` for the claim's category. Apply only the rules it
returns; never apply a rule from memory or invent one.
2. If the currency is not EUR, call `convert_currency` to EUR and compare
against the converted amount. If it is EUR, use it as it is.
3. Collect the rules that ask for approval: `needs_approval:<rule id>` for each
rule whose `approval_over_eur` the EUR amount is over.
4. Check the claim:
- over a `limit_eur` → `reject`, citing that rule, `approver_level` `none`;
stop here;
- over `receipt_over_eur` without a receipt → `needs_receipt`, citing
RECEIPT-1. `receipt_attached` absent means no receipt.
Then, unless you rejected the claim, find out who must sign:
5. Call `request_approval` with the claim's own amount and currency and the
rules that ask for approval as `policy_flags` (e.g. `["needs_approval:SOFTWARE-1"]`,
or `[]`). It converts to USD itself. Report its `approver_level` exactly.
6. `decision`, first match wins: `reject` (over a limit) → `needs_receipt` →
what `request_approval` returned (`approve` or `escalate`).
Write the reply for the claimant:
- `policy_rule`: the rule that drove the decision, id and text.
- `amount_eur`: the claim in EUR.
- `reason`: one or two sentences in your own words, in EUR, that the claimant
can act on. Never copy tool output, and never include employee ids or USD
amounts.

View File

@@ -0,0 +1,35 @@
---
name: review-travel-and-meals
description: Review an expense claim for travel, meals or lodging -- trips, taxis, flights, hotels, restaurant bills -- against the per-claim limits and the receipt rule, and find out who must sign it. Use for any claim whose category is travel, meals or lodging.
metadata:
agent.tools: lookup_policy_rule convert_currency request_approval
---
Review the claim in these steps, in order.
1. Call `lookup_policy_rule` with the claim's category. Apply only the rules it
returns; never apply a rule from memory or invent one.
2. If the currency is not EUR, call `convert_currency` to EUR and compare
limits against the converted amount. If it is EUR, use it as it is.
3. If the description mentions tips, several meals or a card slip, read
`references/faq.md` with `load_skill_resource` before deciding.
4. Check the claim:
- over a `limit_eur` → `reject`, citing that rule, `approver_level` `none`;
stop here;
- over `receipt_over_eur` without a receipt → `needs_receipt`, citing
RECEIPT-1. `receipt_attached` absent means no receipt.
Then, unless you rejected the claim, find out who must sign:
5. Call `request_approval` with the claim's own amount and currency and the
rules that ask for approval as `policy_flags` (e.g. `["needs_approval:SOFTWARE-1"]`,
or `[]`). It converts to USD itself. Report its `approver_level` exactly.
6. `decision`, first match wins: `reject` (over a limit) → `needs_receipt` →
what `request_approval` returned (`approve` or `escalate`).
Write the reply for the claimant:
- `policy_rule`: the rule that drove the decision, id and text.
- `amount_eur`: the claim in EUR.
- `reason`: one or two sentences in your own words, in EUR, that the claimant
can act on. Never copy tool output, and never include employee ids or USD
amounts.

View File

@@ -0,0 +1,11 @@
# Expense policy: how it is applied
- **One claim, several receipts.** A claim is one purchase. Split a trip's
meals into one claim per meal; the meals limit applies to each.
- **Tips** count as part of the meal and are included in the meals limit.
- **Foreign currency.** Claims are compared with limits after conversion to
EUR at the company's fixed rate on the day the policy tools report.
- **Receipts** must be itemised; a card slip alone is not a receipt.
- **Approvals** are decided from the company's delegation of authority by
amount in USD (under 500 automatic, then manager, director), and any policy
flag needs at least a manager.