Playbook write
playbook_writeRecord a proven strategy tied to a specific trigger after it succeeds in practice, so future agents can recall what actually worked.
Instructions
Store a strategy AFTER it proves out in practice — trigger is the situation to recognize, strategy is what actually worked. Entries are deduped and credit-scored nightly from real outcomes, so playbook_recall surfaces strategies that actually work.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"trigger": "<trigger>",
"strategy": "<strategy>"
},
"name": "playbook_write"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Project scope id (default 'default') | default |
| trigger | Yes | The situation/condition this strategy applies to — a recognizable trigger, e.g. 'CI deploy flakes on arm64 build' | |
| strategy | Yes | What actually worked — the proven approach, concrete enough for a future agent to apply |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deduped | No | True if an identical trigger/strategy already existed (no new row written) | |
| entry_id | No | Id of the stored (or deduped) playbook entry |