completion-summary-contract

Solid

Require clear user-facing summaries after completed agent batches.

AI & Automation 58 stars 15 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
59
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
35
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Context Use after any completed agent/task batch or significant direct coordinator action. ## Patterns The final user-facing summary includes these labels, in this order: 1. `Asked:` concise restatement of the request. 2. `Completed:` compact, specific outcomes. 3. `Open issues:` blockers, failing checks, unresolved follow-ups, pending reviews, or `None`. ## Examples Asked: Upgrade the Squad. Completed: Added roster, routing, charters, skills, and validation gates. Open issues: No app build was needed because changes were Squad metadata only. ## Anti-Patterns - Do not hide blockers only in Scribe logs. - Do not claim completion if validation found inconsistencies.

Details

Author
DanWahlin
Repository
DanWahlin/ai-agent-board
Created
6 months ago
Last Updated
2 weeks ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

auditing-completion-claims

当任何一方声称"完成了/做好了/通过了/环境好了/已发布/已经改了"时使用——AI 或工具的汇报、你转述别人的结论、或会话自己即将宣布完成。按层级和证据等级审计:能查机器事实的先查(坐标+新鲜度),查不到的追问四件事(完成了什么/怎么证明/还缺什么/谁接下一步),把假完成拦在验收前。/ Use whenever a completion claim must be accepted or issued — an agent, tool, or teammate reports done/passed/ready, the user relays such a claim, or the session itself is about to report completion. Audits by layer, evidence grade, and residual gaps so "it says done" never silently becomes "it is done."

0 Updated 3 weeks ago
zhaiby-web
AI & Automation Listed

false-completion-gate

Fires when a state-mutating task is about to be declared Done (success summary or completion verdict) — to catch silent success, the highest-frequency invisible agent failure where confident 'done' language hides work that never landed. Decomposes the completion into receipt-checkable assertions, then dispatches a reconciliation auditor that cross-references each claim against the session's tool-call LEDGER (did the producing action fire?) and a fresh postcondition READ-BACK of the named artifact (does the file/test/commit exist and match?), gating the Done behind a BACKED/UNBACKED/UNVERIFIABLE verdict plus a bounded repair loop. Distinct from shadow-verify, which RE-DERIVES an investigation finding's correctness — this reconciles a COMPLETION against execution receipts, never re-deriving the claim. Use before any Done/success in implementation, fix, refactor, migration, or multi-file write work. Skip text-terminal sessions (explanation, Q&A) and work that already failed loudly.

54 Updated today
griffinwork40
AI & Automation Listed

regrounding-summary

Make Claude Fable 5's final report readable to someone who saw none of the work. Use for long agentic sessions, overnight runs, and multi-tool tasks — whenever summaries come back as arrow-chain shorthand, invented abbreviations, or references to reasoning the reader never saw. Pair with grounded-progress for status content; this skill governs the prose.

17 Updated 1 weeks ago
kpab