Capture

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 4e163a7a8095 · 19 Oct 2026Report an issue or request a re-scan

• Publishersharpdeveye GitHub userOwner of the repository this skill is read from
• Source foldersharpdeveye/maestro/source/skills/captureThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict4e163a7a8095A new audit runs when the source changes
• Repository statusNot archivedLast push 173 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Capture a session summary — what was done, what decisions were made, and what to do next.

---
name: capture
description: "Capture a session summary — what was done, what decisions were made, and what to do next."
argument-hint: "[session topic]"
category: utility
version: 2.0.0
user-invocable: true
---

## 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.

---

Capture the current session's work into a persistent summary. This creates a record that survives session boundaries — future commands can reference what happened here.

### What to Capture

Read the conversation history and identify:

1. **Commands run** — which Maestro commands were invoked and in what order
2. **Decisions made** — architectural choices, trade-offs accepted, patterns adopted
3. **Files changed** — what was created, modified, or deleted
4. **Issues found** — bugs, gaps, or risks identified
5. **Next steps** — what should happen next (be specific)

### Output Format

Generate a session summary file at `.maestro/sessions/{date}_{topic}.md`:

```markdown
# Session: {topic}
Date: {YYYY-MM-DD}

## Commands Run
- /diagnose → Score: 18/25
- /fortify → Added retry logic to API handlers
- /evaluate → Verified with 3 test scenarios

## Decisions
- Chose retry-with-backoff over circuit breaker (simpler, sufficient for current load)
- Kept synchronous error handling (async not justified yet)

## Files Changed
- `src/api/handler.ts` — added retry wrapper
- `src/middleware/auth.ts` — added input validation
- `tests/api.test.ts` — new test file

## Open Issues
- Rate limiting not yet implemented (deferred to next session)

## Next Steps
1. Run `/guard` to add rate limiting
2. Run `/evaluate` with adversarial test cases
```

Also append a decision entry to `.maestro/decisions.jsonl` recording this capture.

### Session Capture Checklist

- [ ] All commands from this session listed
- [ ] Key decisions documented with rationale
- [ ] Files changed listed with brief descriptions
- [ ] Open issues captured (nothing lost)
- [ ] Next steps are specific and actionable
- [ ] Summary saved to `.maestro/sessions/`

### Recommended Next Step

After capturing, your next session should start with `/recap` to restore context, then proceed with the next steps listed above.

**NEVER**:

- Store raw prompts or full LLM outputs in the session file
- Overwrite an existing session file — create a new one
- Skip the "Next Steps" section — this is what makes capture valuable
- Capture without reading the conversation history first
- Auto-capture without the user invoking this command

Excerpt, first 2,672 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/sharpdeveye/maestro
git -C maestro checkout 4e163a7a8095

Works in

1. 2026-10-19
   ✓SAFE B 89 / 100

   first audit · source 4e163a7a8095

Questions about Capture

• github.com/sharpdeveye/maestro/tree/main/source/skills/capture — the audited source at commit 4e163a7a8095 and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology