handoff-pack

Generate compact handoff packs for agent-to-agent communication.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/marcusglee11/LifeOS --skill handoff-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-pack
Source: https://github.com/marcusglee11/LifeOS/tree/main/.claude/skills/handoff-pack
Command: npx skills add https://github.com/marcusglee11/LifeOS --skill handoff-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of concise, structured handoff packages for inter-agent communication, ensuring clarity and reducing token usage.

Core Features & Use Cases

  • Deterministic Handoffs: Generates compact, structured data packs for seamless agent transitions.
  • Mode Flexibility: Supports both outbound (to Codex) and inbound (from Codex) handoff scenarios.
  • Use Case: When passing a complex coding task to a specialized coding agent, use this Skill to generate a clear summary of the task, current progress, and necessary context.

Quick Start

Use the handoff-pack skill to prepare an outbound handoff to Codex for the current task.

Frequently Asked Questions about handoff-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured context handoff for agent-to-agent communication?

Agent handoff packs standardize context transfer by packaging branch, commits, test results, and task status into compact, deterministic data structures. This minimizes token usage and ensures clear information transfer between agents.

What is the best way to pass complex coding tasks to Codex?

Passing tasks to Codex requires a structured outbound handoff pack containing branch state, commits, test results, and task status. This provides the specialized coding agent with deterministic, minimal-token context for seamless task transitions.

How does context management work for inbound task transitions from Codex?

Inbound task transitions process structured handoff packs from Codex, extracting standardized task status, commits, and progress data. This inbound workflow ensures the receiving agent accurately absorbs completed work and remaining context with minimal token overhead.

Why use a deterministic handoff pack instead of raw text for agent communication?

Deterministic handoff packs replace raw text to optimize token usage and enforce clear information transfer. They standardize essential context like branch, commits, and test results, preventing ambiguity and reducing overhead during complex agent task transitions.

Can I use this handoff skill for both outbound and inbound agent workflows?

Yes, this skill supports both outbound and inbound agent workflows through mode flexibility. It generates packs for sending tasks to Codex and processes packs received from Codex, ensuring seamless bidirectional task transitions and standardized context management.