Agent skill

Capture

by sharpdeveye in sharpdeveye/maestro

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

MITAuto-check passedAgent Workflows

Install Capture

skills CLI
$ npx skills add sharpdeveye/maestro --skill capture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sharpdeveye/maestro capture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/skills/capture .claude/skills/capture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
capture
GitHub stars
592
Token cost
~669 tokens
SKILL.md length
233 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Commands run — which Maestro commands… → Decisions made — architectural choices,… → Files changed — what was created,… → …
  • Tasks that involve Session handoff
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Capture is an agent skill from sharpdeveye/maestro. Capture a session summary — what was done, what decisions were made, and what to do next.

Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and… The licence is MIT.

When your agent uses it

  • Tasks that involve Session handoff

Example prompts

  • “/capture”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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)

What it can do on your machine

Read from SKILL.md and the folder at commit 00f9115. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Capture loads about 669 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 233 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~669

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sharpdeveye/maestro at commit 00f9115, republished under its MIT licence (© sharpdeveye). 233 words, ~669 tokens.

Download SKILL.mdSave it as .claude/skills/capture/SKILL.md (or your agent's skills folder).
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/

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

© sharpdeveye, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in source/skills/capture of sharpdeveye/maestro.

Open the folder on GitHubat commit 00f9115

Compare with similar skills

Capture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Capture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Capture this skillsharpdeveye/maestro592—~669Automated safety check: PassMIT
Session Managementjosstei/maestro-orchestrate465—~3.5kAutomated safety check: PassApache-2.0
Executejosstei/maestro-orchestrate465—~409Automated safety check: NotesApache-2.0
Orchestratejosstei/maestro-orchestrate465—~388Automated safety check: NotesApache-2.0
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Coding Agent Session Findercode-yeongyu/oh-my-openagent70k1 repos~2.8kAutomated safety check: PassCustom licence

Similar skills

  • Session Management

    josstei/maestro-orchestrate

    Manages orchestration session state, tracking, and resumption

    465 GitHub stars~3.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Execute

    josstei/maestro-orchestrate

    Execute an approved Maestro implementation plan using the shared session-state contract

    465 GitHub stars~409 tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Orchestrate

    josstei/maestro-orchestrate

    Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved implementation plan, and then execution with shared session state

    465 GitHub stars~388 tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub starsUsed in 1 repo~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from sharpdeveye/maestro

All 25 skills in this repo
  • Accelerate

    sharpdeveye/maestro

    A skill your agent uses when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

    592 GitHub stars~745 tokensUpdated 5 mo ago
    Auto-check passed
  • Chain

    sharpdeveye/maestro

    A skill your agent uses when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.

    592 GitHub stars~607 tokensUpdated 5 mo ago
    Auto-check passed
  • Compose

    sharpdeveye/maestro

    A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

    592 GitHub stars~720 tokensUpdated 5 mo ago
    Auto-check passed
  • Diagnose

    sharpdeveye/maestro

    A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.

    592 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed
  • Extract Pattern

    sharpdeveye/maestro

    A skill your agent uses when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

    592 GitHub stars~664 tokensUpdated 5 mo ago
    Auto-check passed
  • Fortify

    sharpdeveye/maestro

    A skill your agent uses when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

    592 GitHub stars~688 tokensUpdated 5 mo ago
    Auto-check passed

Questions about Capture

What does Capture do?

Capture a session summary — what was done, what decisions were made, and what to do next. Capture is an agent skill from sharpdeveye/maestro. Capture a session summary — what was done, what decisions were made, and what to do next.

When should I use Capture?

Capture fits situations like: tasks that involve Session handoff.

How do I install Capture in Claude Code?

Run `npx skills add sharpdeveye/maestro --skill capture -a claude-code`. Or copy the skill folder (source/skills/capture in sharpdeveye/maestro) into .claude/skills/capture in your project. Claude Code loads it when a task matches its description.

How do I install Capture in Codex?

Run `npx skills add sharpdeveye/maestro --skill capture -a codex`. Or copy the skill folder (source/skills/capture in sharpdeveye/maestro) into .agents/skills/capture in your project. Codex loads it when a task matches its description.

Can I use Capture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sharpdeveye/maestro --skill capture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/capture, .gemini/skills/capture, .github/skills/capture and .opencode/skills/capture in your project.

What does Capture need to run?

SKILL.md names no scripts, command-line tools or credentials: Capture is instructions for the agent only.

Does Capture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Capture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Capture use?

Capture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Capture use?

About 669 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Capture?

Skills that share tags, products or a category with Capture: Session Management (josstei/maestro-orchestrate, 465 stars), Execute (josstei/maestro-orchestrate, 465 stars), Orchestrate (josstei/maestro-orchestrate, 465 stars) and Orca CLI (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Capture?

sharpdeveye (a GitHub user) maintains it in sharpdeveye/maestro, which has 592 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on April 29, 2026.

Source: sharpdeveye/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.