---
id: "concept-skill-composability"
type: "concept"
source_timestamps: ["16:30:00", "16:40:00", "17:00:00"]
tags: ["workflow-automation", "system-design"]
related: ["concept-skills-as-contracts", "concept-orchestrator-pattern", "action-define-output-contracts"]
definition: "The requirement to design skills not as isolated solutions, but as modular components whose outputs feed directly into the inputs of the next skill in a chain."
sources: ["s43-file-format-agreement"]
sourceVaultSlug: "s43-file-format-agreement"
originDay: 43
---
# Skill Composability and Handoffs

## Definition

Skills must be designed not as isolated solutions but as **modular components** whose outputs feed directly into the inputs of the next skill in a chain.

## The Failure Mode

A critical failure mode in skill design is treating a skill as a standalone solution to a single problem. In an agent-first world, skills must be composable.

The **output of Skill A must be explicitly designed to serve as the perfect input for Skill B**. If a business process requires multiple steps (e.g., processing a ticket through triage → enrichment → routing → response), the agent needs to be able to hand off the work from one specialized skill to another.

If the output of the first skill is not formatted correctly to be handed down the chain, the entire workflow breaks.

## The Design Question

When designing a skill, the creator must constantly ask:

> *"Is the output generated by this skill correct and formatted to hand to the next agent or process?"*

Thinking **end-to-end** rather than in isolation is essential for preventing handoff failures.

## Related

- [[concept-skills-as-contracts]] — the contract is the substrate of composability
- [[concept-orchestrator-pattern]] — orchestrators are useless without composable sub-skills
- [[action-define-output-contracts]] — concrete enabling practice