Recap
Quick summary of the last session — commands run, files changed, and what to do next.
Install
$ agentstack add skill-sharpdeveye-maestro-recap ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sharpdeveye-maestro-recap) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sharpdeveye
- Source: sharpdeveye/maestro
- License: MIT
- Homepage: https://maestroskills.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.