handoff

Publish standardized handoff manifests describing produced artifacts for downstream skill coordination.

13|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/OmexIT/claude-skills-pack --skill handoff-omexit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/handoff
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill handoff-omexit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inter-skill artifact protocol. Defines how skills discover and consume prior skill outputs, handle multi-artifact handoffs, track artifact lifecycle, and clean up after consumption. Not a slash command — loaded automatically to enable skill chaining.

Core Features & Use Cases

  • Provides a formal mechanism for artifacts produced by skills to be published via standardized handoff manifests, enabling downstream skills to discover, read, and coordinate consumption.
  • Supports single- and multi-artifact outputs with per-artifact metadata, status, and downstream consumption guidance.
  • Enforces lifecycle policies (consumption, archiving, audit trails) and supports optional design-tool extensions and upstream references.

Quick Start

After producing outputs, emit a handoff manifest using the Section 2 schema to enable downstream skills to locate and use your artifacts.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I coordinate cross-skill artifact handoffs in an automated workflow?

Cross-skill artifact handoffs are coordinated by publishing standardized handoff manifests that describe produced artifacts, enabling downstream skills to discover, read, and consume them reliably within a workflow chain.

What is a handoff manifest and when do I need it for skill chaining?

A handoff manifest is a standardized protocol defining artifact metadata, quality signals, and downstream recommendations. You need it when downstream skills must discover and coordinate the use of prior skill outputs.

How do I handle missing upstream artifacts during a skill workflow?

Missing upstream artifacts are managed through graceful degradation. The handoff protocol supports this fallback behavior while still preserving an audit trail through archiving to maintain workflow reliability.

Can I track multiple artifacts and their lifecycle status in a single workflow?

Yes, multi-artifact outputs are supported with per-artifact metadata, status tracking, and downstream consumption guidance. The protocol enforces lifecycle policies including consumption, archiving, and audit trails.

Do I need to manually invoke a command to start the artifact handoff process?

No, the artifact handoff process is not a slash command. It is loaded automatically to enable skill chaining, requiring you to emit a handoff manifest after producing outputs to enable downstream discovery.

What's the best way to maintain an audit trail for consumed artifacts across skills?

Maintaining an audit trail for consumed artifacts is handled by enforcing lifecycle policies within the handoff manifest. The protocol supports archiving and tracking artifact consumption to preserve reliable audit records.