session-management
This Claude Code skill manages agent sessions within the Gas Town framework, enabling initialization of new sessions, coordination handoffs between agents, and revival of inactive sessions while preserving agent identity. Use it when setting up agent workflows, transferring work between different agents, recovering from failed sessions, or maintaining persistent identity across ephemeral Polecat agent instances.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/session-management && cp -r /tmp/session-management/library/methodologies/gastown/skills/session-management ~/.claude/skills/session-managementSKILL.md
# Session Management ## Overview Manage agent sessions in Gas Town: initialize new sessions, handle handoffs between agents, revive dead sessions (seance), and maintain persistent identity across ephemeral Polecat sessions. ## When to Use - Initializing new agent sessions - Handing off work between agents - Reviving a dead or stuck agent session - Managing Polecat identity persistence across sessions ## Session Operations 1. **Init**: Start new session with role and hook setup 2. **Attach**: Connect agent to Mayor for coordination 3. **Handoff**: Transfer work between agents with context 4. **Seance**: Revive a dead agent's session state 5. **Resume**: Continue from last checkpoint ## Agent Session Types - **Crew**: Long-lived sessions, full state persistence - **Polecat**: Ephemeral sessions, persistent identity, state via hooks - **Dog**: Infrastructure sessions, minimal state ## Key Commands - `gt mayor attach` - Attach to Mayor coordination - `gt handoff` - Hand off work to another agent - `gt seance` - Revive dead session - `gt prime` - Prime agent with context ## Tool Use Used within agent coordination and patrol monitoring processes.
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement