Compress session context using anchored iterative summarization. Use when context is getting long, before ending a session, or when you need to create a resumable checkpoint.
/plugin marketplace add ReinaMacCredy/maestro/plugin install maestro@maestro-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Compress current session context using anchored iterative summarization.
compact/compactsession compactcompress contextcompact → compress + save to history/threads/YYYY-MM-DD-HH-MM-compact.md
compact path/to.md → compress + save to custom path
compact --verbose → show full quality scores
history/threads/YYYY-MM-DD-HH-MM-compact.md)Generate this exact structure:
# Session Compact - YYYY-MM-DD HH:MM
## Intent
[1-2 sentences: What we're trying to accomplish and why]
## Artifacts
### Modified
| File | Change |
|------|--------|
| `path/to/file.ts` | Brief description of changes |
### Read
| File | Reason |
|------|--------|
| `path/to/file.ts` | Why it was examined |
## Decisions
1. **Decision title** - reasoning behind the choice
## State
[Current progress: what works, what's broken, where we are in the task]
## Next
1. [Immediate next action]
2. [Following action]
## Blockers
[Any issues preventing progress, or "None"]
## Quality: X.X/5.0
[Only shown in --verbose mode or when below 3.5 threshold]
Each section must be populated or explicitly marked empty:
| Section | Required Content |
|---|---|
| Intent | Goal + motivation, not just task description |
| Modified | Files changed this session (use git diff if available) |
| Read | Files examined, why they mattered |
| Decisions | Choices made, with reasoning |
| State | What works now, what's broken, current position |
| Next | Actionable steps, specific enough to execute |
| Blockers | What's stopping progress, or explicit "None" |
After generating the summary, evaluate its quality:
Create one question for each probe type based on session content:
| Type | Purpose | Example |
|---|---|---|
| Recall | Test factual retention | "What was the original error message?" |
| Artifact | Test file tracking | "Which files have we modified?" |
| Continuation | Test next-step clarity | "What should we do next?" |
| Decision | Test reasoning preservation | "Why did we choose approach X over Y?" |
⚠️ Low [dimension] (X.X) - [actionable suggestion]
| Dimension | Suggestion |
|---|---|
| Accuracy | "verify file paths and technical details" |
| Context Awareness | "re-read recent messages to capture current state" |
| Artifact Trail | "run git status to find all modified files" |
| Continuity | "check for unresolved TODOs and open questions" |
| Completeness | "review earlier conversation for missed topics" |
| Instruction Following | "ensure all sections are populated" |
Key principles from Factory.ai research:
git diff --name-only to detect modified files when in a git repohistory/threads/ directory exists before savingCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.