Install
$ agentstack add skill-s-choung-research-skills-smart-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.
About
Smart Compact
Save session state to file. User then runs /clear to reset. The session-state.md is auto-read on next session start (via CLAUDE.md instruction).
Instructions
When the user runs /smart-compact:
- Write
.claude/session-state.mdin the current working directory - Tell the user it's done so they can
/clear
Speed principle: This should take ~10 seconds, not minutes. Write dense, not verbose.
Template
# Session State
> /smart-compact at [date/time]
## Tone
[One line. e.g. "Korean casual + English tech terms, concise"]
## What We Did
[Numbered list of what happened this session, chronologically. Keep each item to 1-2 lines.
Include: what was requested → what was done → outcome]
## Key Decisions
[Bullet list of decisions + WHY. Quote user's exact words for preferences.]
## Files
| File | What Changed |
|------|-------------|
| path | one-line summary with key function/variable names |
## Current Status
- [x] Done tasks
- [ ] In-progress (note current state)
- [ ] TODO
## Bugs & Fixes
[Only if any. "Problem → cause → fix" format, one line each.]
## Code Notes
[Only for tricky/non-obvious code that would be hard to reconstruct.
Paste ONLY the critical snippets, not whole files. Skip if nothing tricky.]
## Tech Context
[Key paths, model names, config values, env details. Dense bullet list.]
## Next Steps
[Priority-ordered. What to do immediately after recovery.]
Writing Guidelines
- Dense, not verbose — bullet points, not paragraphs
- Skip sections that are empty (except Tone, What We Did, Files, Current Status, Next Steps — always include these 5)
- Include specific names: variables, functions, paths, config values
- Quote user feedback verbatim when it matters
- For bugs: what didn't work is as important as what did
- Write for a new Claude that knows NOTHING about this conversation
Post-Clear Recovery
Project CLAUDE.md auto-reads .claude/session-state.md on session start. No manual action needed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: s-choung
- Source: s-choung/Research-Skills
- 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.