recap
Quick summary of the last session — commands run, files changed, and what to do next.
pinned to #00f9115updated 2 weeks ago
Ask your AI client: “install skills/recap”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/recapmetahub onboarded this repo on the author's behalf.
If you own github.com/sharpdeveye/maestro on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
402
Last commit
2 weeks ago
Latest release
published
- #agent-orchestration
- #ai
- #ai-agents
- #ai-workflows
- #claude-code
- #codex
- #copilot
- #cursor
- #developer-tools
- #gemini
- #open-source
- #prompt-engineering
- #skills
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.00f9115· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at source/skills/recap/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
329 words · 2,144 chars · 6 sections · 1 code block
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent00f9115warn2 weeks ago
Contents
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Get back up to speed fast. Recap reads the most recent session file and recent decisions to tell you where you left off and what to do next.
Data Sources
.maestro/sessions/— read the most recent session file (by filename date).maestro/decisions.jsonl— read the last 5 decisions
If no session files exist, read the last 10 decisions and summarize those instead.
If no data exists at all, respond: "No session history found. Run /capture at the end of your next session to start tracking."
Output Format
┌─────────────────────────────────────┐
│ LAST SESSION RECAP │
├─────────────────────────────────────┤
│ Date: YYYY-MM-DD │
│ Commands: /diagnose → /fortify (2) │
│ Files: 3 changed, 1 created │
│ Outcome: Completed │
├─────────────────────────────────────┤
│ PICK UP HERE: │
│ 1. Run /guard — rate limiting │
│ 2. Run /evaluate — adversarial tests│
└─────────────────────────────────────┘
Recap Rules
- Be concise — this is a 30-second read, not a report
- Lead with the "PICK UP HERE" section — that's what the user needs
- If the session ended with open issues, highlight them
- Reference specific files and commands, not vague summaries
Recap Checklist
- Most recent session identified
- Commands and outcomes summarized in one line each
- "Pick up here" section has specific, actionable next steps
- Open issues from last session surfaced
Recommended Next Step
After recapping, run the first command listed in "Pick Up Here" to continue where you left off.
NEVER:
- Dump the entire session file — summarize it
- Recap without checking decisions.jsonl for recent activity
- Give vague next steps ("continue working") — be specific
- Assume context from the current conversation — only use persisted data
Reviews
No reviews yet. Be the first.
Related
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
orchestration-patterns
>
migration-patterns
>
mh install skills/recap