chain-composer

Name: chain-composer
Availability: InStock
Author: notque

Compose type-safe pipeline chains from a Component Manifest into a Pipeline Spec JSON.

415|44|Updated Mar 18, 2026

Search Tags:#automation #validation #composition #pipeline #manifests #type-safety #pipeline-spec

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill chain-composer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chain-composer
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/chain-composer
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill chain-composer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Compose and validate type-safe pipeline chains from a Component Manifest, producing a Pipeline Spec JSON consumable by the pipeline-scaffolder.

Core Features & Use Cases

Start from canonical templates per subdomain task_type and adapt with domain-specific steps
Validate type compatibility deterministically using scripts/artifact-utils.py validate-chain
Output a complete Pipeline Spec JSON and a human-readable summary for handoff
Apply operator-profile gates to tailor chains to personal, work, CI, or production contexts
Respect explicit prerequisites in the domain manifest (references_needed, scripts_needed)

Quick Start

Invoke the chain-composer with a Component Manifest to generate a Pipeline Spec.

Frequently Asked Questions about chain-composer

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

FAQPage Schema

How do I compose type-safe pipeline chains from a domain manifest?▼

To compose type-safe pipeline chains, you apply canonical templates to subdomain task types and validate compatibility deterministically, producing a Pipeline Spec JSON. This process ensures your pipeline chain maintains type safety throughout its execution stages.

How do I validate type compatibility when building a pipeline specification?▼

You validate type compatibility for a pipeline specification by running the artifact-utils validator against your composed chain. This deterministic validation checks whether template-adapted steps align correctly before outputting the final Pipeline Spec JSON.

Can I tailor pipeline chains for CI, production, or personal work contexts?▼

You can tailor pipeline chains for CI, production, personal, or work contexts by applying operator-profile gates during composition. These gates adjust the generated Pipeline Spec JSON to match the specific environmental requirements of each deployment target.

What prerequisites does a domain manifest need before composing a pipeline spec?▼

A domain manifest must explicitly declare prerequisites like references_needed and scripts_needed before pipeline spec composition begins. The chain-composer respects these declared dependencies to ensure all required components are available during type-safe chain generation.

What is the best way to generate a Pipeline Spec JSON for a pipeline scaffolder?▼

The best way to generate a Pipeline Spec JSON for a pipeline scaffolder is to start from canonical templates per subdomain task type, adapt them with domain-specific steps, and validate the chain. This produces a complete spec ready for scaffolding.

Why does my pipeline chain composition fail type compatibility validation?▼

Pipeline chain composition fails type compatibility validation when subdomain task types and adapted domain-specific steps do not align deterministically. The artifact-utils validator rejects mismatches between canonical templates and manifest requirements, preventing an invalid Pipeline Spec from being generated.