skills.rest
douglasjarquin
douglasjarquinCOMMUNITY
Explore all skills by this author →
Website𝕏@douglasjarquinGitHub

recap

Summarizes session history from saved inbox, task, and verification files.

Updated Sep 5, 2026
Search Tags:#multi-agent#inbox#task status#audit trail#coordinator#session recap#history summary
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill recap-douglasjarquin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recap
Source: https://github.com/douglasjarquin/sum/tree/main/grok-bots/sum/skills/recap
Command: npx skills add https://github.com/douglasjarquin/sum --skill recap-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you return to a multi-agent coordination session, it is hard to reconstruct what already happened without polling workers or guessing at live state. This Skill produces a recap built strictly from saved files, so every claim is grounded in recorded history rather than speculation. ## Core Features & Use Cases - History-only recap: Reads /workspace/sum/inbox.md, task briefs, questions, reports, and verification files to summarize what already occurred. - No live state invention: Explicitly refuses to poll workers or GitHub, and reports missing files instead of guessing. - No accidental work dispatch: A recap never counts as approval to start new work. - Use Case: After stepping away from a coordinator session, ask for a recap to see which questions were answered, which tasks reported results, and what verification was recorded. ## Quick Start Ask the coordinator to recap this session from the saved history files.

Frequently Asked Questions about recap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a recap of what happened in my agent session?▼

Ask the coordinator for a session recap. The recap skill reads the saved inbox, task briefs, questions, reports, and verification files under /workspace/sum/ and summarizes only what those files record.

Does the session recap show live worker status?▼

No, the recap is history-only. It never polls workers or GitHub and does not invent live fleet state; every claim must point at a saved file on disk.

What happens if a task file is missing during a recap?▼

The recap states that the file is missing instead of guessing. It will not speculate about what a worker is currently doing when no saved record exists.

Can a recap trigger new work or task dispatch?▼

No. A recap is never treated as approval to start work. New work begins only from an explicit user instruction or an already-approved task.

What files does the session recap read?▼

It reads inbox.md plus open task briefs, question files, reports, and verification files saved under /workspace/sum/. It uses only these saved records as sources.

Related Skills

Explore More Software Engineering Skills→
riethmayerriethmayer
2

team

Coordinate agent workers on a shared task list via tmux orchestration.

Community
Advanced
cobusgreylingcobusgreyling
10.8k

pr-review-triage

Triages open pull requests for CI status, review state, and merge readiness.

Community
Intermediate
phyter1phyter1

fleet-status

Monitor fleet machine and service health via network checks and model status.

Community
Basic
davila7davila7
30.5k

excalidraw

Delegates Excalidraw diagram file operations to subagents to preserve main agent context.

Community
Intermediate