Menu

Individual skill

agent-deck-playbooks

Use when a task matches a bound-deck playbook trigger, or when the user corrects output produced from a playbook. Fetch playbooks; propose patches from corrections.

plugins/not-so-fat/agent-deck/skills/agent-deck-playbooks/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Agent Deck playbooks

1. On task match: check `triggers` on `get_bound_deck`, then `get_playbook` before improvising. Playbook bodies live on the deck — do not mirror them into local skills.


**When the user corrects your output** (the write trigger — no need to have called `get_playbook` earlier in the session):

**Update case** (a playbook covered this task): fix the output, then `get_playbook` and read `openPatches`. If an open proposal addresses the **same** lesson, pass its `id`(s) in `supersedes` and fold into one better `propose_playbook_patch` (do not file a sibling). If open patches are different problems, omit `supersedes`. Prefer one `add_item` to Gotchas/Checklist; include `evidence.user_feedback_excerpt` as a short verbatim quote of the correction.

**Genesis case** (no playbook covered the task): before ending, `propose_playbook_patch { kind: "create", new_playbook: { title, triggers, body with one gotcha } }` — a few lines is the right size.

**Defer when unsure** (`kind: "signal_only"`): if the correction is plausible but not yet clearly generalizable (edge case, one-off, or needs sibling corrections before the lesson is clear), call `propose_playbook_patch { kind: "signal_only", evidence, rationale }` — logs the signal with no patch proposal. Prefer immediate `update`/`create` when the lesson is clear.

**Curate from a pasted dashboard prompt:** when the user pastes a curation prompt from the Feedback table (`/feedback-signals` → Copy for agent; Markdown + YAML list, each row leads with `id`), group the signals, then `propose_playbook_patch` with consolidated ops and `signal_ids` of every consumed id. That links rows (still open) until the patch is accepted. Do not invent a list-feedback MCP tool — browse/discard is dashboard-only.