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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- agent-deck-playbooks
- description
- 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.
03 SKILL.md 正文
Agent Deck playbooks
- On task match: check
triggersonget_bound_deck, thenget_playbookbefore 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.
-
Explicit user-directed playbook edits ("fix the playbook to say X"): direct
update_playbookis dashboard-only — usepropose_playbook_patchwithrewrite_bodyunless they will apply the edit in the dashboard themselves. -
Tell the user in one line that a proposal was filed (or a signal was logged for later dashboard curation); review happens in the dashboard.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.