Ltm:compact
Review the current session and extract undocumented decisions into the project memory
Install
$ agentstack add skill-laserphaser-claude-ltm-ltm-compact ✓ 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-laserphaser-claude-ltm-ltm-compact) 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
Compact — Extract Decisions to Memory
Perform a compact pass: review everything that happened in this session and capture any significant decisions that aren't yet in .memory/DECISIONS.md.
What to do
- Read
.memory/DECISIONS.mdto understand what's already recorded.
- Review this session's work. Look for:
- Architecture or design choices that were made
- Technology or library selections
- Approaches that were tried and rejected
- Business logic decisions or constraints discovered
- Changes to previously recorded decisions
- Current project status (focus, blockers, open questions)
- For each unrecorded decision:
- "Significant" = something a teammate joining next week would need to know.
- Add a
### headingwith today's date and up to ~10 lines of context. - If the decision is truly complex (>10 lines needed), create a detail file
in .memory/details/YYYY-MM-DD-.md and link to it.
- If a prior decision was superseded, update it in-place with what changed
and why. Add a Changelog entry.
- Check for duplicates — update existing entries rather than adding new ones.
- Update the
## Statussection with current focus, blockers, and open questions.
- Update the
> Auto-maintained by claude-ltm. Last updated:date.
- Report to the user what was captured (or that nothing new was found).
Detail file format
When creating a detail file in .memory/details/, use this structure:
---
decision:
date: YYYY-MM-DD
status: ACTIVE
---
## Context
[Why this decision was needed — 2-3 sentences]
## Decision
[What was chosen and why — concise]
## Alternatives Considered
- Option B: [why rejected]
## Impact
- [Key consequence 1]Guidelines
- Keep entries concise. This is a decision log, not documentation.
- Routine code changes are NOT decisions. Choosing a database IS.
- When in doubt about significance, record it — pruning is easier than recreating.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: LaserPhaser
- Source: LaserPhaser/claude-ltm
- License: MIT
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.