Agent skill
acm-handoff
Use when resuming work from a previous session that reached context threshold, or when a handoff summary exists. Reads handoff state and markdown to restore context, todos, and continue seamlessly.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/acm-handoff
SKILL.md
Context Handoff
This skill loads handoff content from a previous session that reached the context threshold.
Instructions
When this skill is invoked:
- Check for structured state at
.claude/claudikins-acm/handoff-state.json - Read the handoff markdown at
.claude/claudikins-acm/handoff.md - Present both to understand what was being worked on
- Restore todos if active todos exist in the state
- Continue the work from where it was left off
File Locations
| File | Purpose |
|---|---|
.claude/claudikins-acm/handoff-state.json |
Structured state (preferred) |
.claude/claudikins-acm/handoff.md |
Human-readable summary |
Reading the State
The structured state JSON contains:
context.current_objective- What was being worked oncontext.active_todos- Pending/in-progress todos to restorecontext.key_files_modified- Recently changed filesgit.branch- Git branch at handoff timegit.modified_files- Uncommitted changes
After Reading
- Restore todos using TodoWrite if
active_todoshas entries - Summarise the previous session's state for the user
- Ask if they want to continue from where they left off
- Clean up the handoff files after successful restoration
Cleanup
After successfully restoring context, offer to clean up:
rm -f .claude/claudikins-acm/handoff-state.json
rm -f .claude/claudikins-acm/handoff.md
If No Handoff Exists
If neither file exists, inform the user:
- No handoff is currently active
- A handoff is created when context usage hits the threshold (default 60%)
- They can configure the threshold via /acm:config
Claudikins Automatic Context Manager To configure settings, use: /acm:config
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?