claude/skills/transfer-context/SKILL.md
Prepare context for a new chat session when this one is degraded or hitting token limits. Use when context is above 70% or conversation needs to continue in a fresh session.
npx skillsauth add mkitt/dotfiles transfer-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Prepare context for a new chat session when this one is degraded or hitting limits.
## Context Transfer
### Summary
[What was accomplished in this session]
### Key Decisions
- [Decision 1 and why]
- [Decision 2 and why]
### Important Context
- [Gotchas discovered]
- [Patterns to follow]
- [Things that didn't work]
### Relevant Files
- path/to/file.ts - [what it does, why it matters]
- path/to/other.ts - [description]
### Current State
[What's working, what's broken, what's next]
### Prompt for New Chat
[Ready-to-paste prompt with all necessary context to continue]
The prompt should give the new session everything it needs to continue without re-explaining.
testing
Post-merge branch cleanup. Switches to the default branch, pulls latest, and deletes the stale local branch. Use after a PR merges.
testing
Daily situation report. Gathers activity from connected sources (GitHub, Slack, Linear, Calendar, Gmail) to debrief what happened, brief what's ahead, and muster a composed summary. Use when the user wants to review activity, check what's coming up, or prepare a daily update.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------