How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

skill-chain-prompts - Skill

Name: skill-chain-prompts
Author: 4444j99

Imported from 4444j99/a-i--skills (skills/tools/skill-chain-prompts/SKILL.md). Install upstream with npx skills add 4444j99/a-i--skills --skill skill-chain-prompts. Copyright stays with the author (MIT).

Skill Chain Prompts

Orchestrate complex workflows by chaining multiple skills together. Define sequences, track progress, and use pre-built chains for common development patterns.

Concept

A chain is a sequence of skills that work together to accomplish a larger goal. Each step invokes a skill, passes context forward, and tracks completion. Chains work through Claude's sequential processing—no external engine required.

Quick Reference

Chain Format

chain:
  name: "my-workflow"
  description: "What this chain accomplishes"

steps:
  - id: first
    skill: skill-name
    description: "What this step does"
    outputs: [artifact1, artifact2]

  - id: second
    skill: another-skill
    depends_on: [first]
    checkpoint: true  # Pause for review

  - id: third
    skill: final-skill
    depends_on: [second]
    optional: true  # Can be skipped

Commands

Command	Purpose
`/skill-chain-prompts run <chain>`	Execute a named chain
`/skill-chain-prompts list`	Show available chains
`/skill-chain-prompts status`	Display current progress
`/skill-chain-prompts resume`	Continue from checkpoint
`/skill-chain-prompts skip`	Skip current optional step

Pre-Built Chains

Development Workflows

api-development — Full API from design to deployment

api-design-patterns → tdd-workflow → backend-implementation-patterns → verification-loop → deployment-cicd

fullstack-feature — Complete feature implementation

product-requirements-designer → api-design-patterns → backend-implementation-patterns → frontend-design-systems → testing-patterns → verification-loop

mcp-development — MCP server creation

mcp-builder → testing-patterns → verification-loop → mcp-server-orchestrator

Professional Workflows

career-preparation — Job search readiness

cv-resume-builder → portfolio-presentation → interview-preparation → networking-outreach

documentation — Project documentation

doc-coauthoring → github-repository-standards → github-profile-architect

Usage Examples

Run a Pre-Built Chain

User: /skill-chain-prompts run api-development

Claude: Starting chain: api-development
        "Full API development from design to deployment"

        Step 1/5: design (api-design-patterns)
        Invoking /api-design-patterns...

Check Progress

User: /skill-chain-prompts status

Claude: ## Chain Progress: api-development

        | Step | Skill | Status | Notes |
        |------|-------|--------|-------|
        | design | api-design-patterns | ● Done | OpenAPI spec created |
        | test-first | tdd-workflow | ◐ Active | Writing endpoint tests |
        | implement | backend-implementation-patterns | ○ Pending | |
        | verify | verification-loop | ○ Pending | |
        | deploy | deployment-cicd | ⊖ Optional | |

        **Progress**: 2/5 steps (40%)
        **Current**: test-first

Create Custom Chain

User: I need a chain for building a CLI tool

Claude: Creating custom chain...

        chain:
          name: "cli-tool"
          description: "Build a CLI application"

        steps:
          - id: design
            skill: api-design-patterns
            description: "Design CLI interface and commands"

          - id: implement
            skill: backend-implementation-patterns
            depends_on: [design]

          - id: test
            skill: testing-patterns
            depends_on: [implement]

          - id: docs
            skill: doc-coauthoring
            depends_on: [implement]
            optional: true

        Ready to execute?

State Tracking

Progress is tracked in the conversation using markdown tables:

## Chain Progress: fullstack-feature

| Step | Skill | Status | Notes |
|------|-------|--------|-------|
| requirements | product-requirements-designer | ● Done | PRD complete |
| api | api-design-patterns | ● Done | 12 endpoints |
| backend | backend-implementation-patterns | ◐ Active | 8/12 endpoints |
| frontend | frontend-design-systems | ○ Pending | |
| testing | testing-patterns | ○ Pending | |
| verify | verification-loop | ○ Pending | |

**Progress**: 2.5/6 steps (42%)
**Checkpoint**: After verify

Status Icons

Icon	Meaning
○	Pending
◐	In Progress
●	Complete
⊖	Optional/Skipped
✕	Failed

Checkpoints

Checkpoints pause the chain for review:

- id: verify
  skill: verification-loop
  depends_on: [implement]
  checkpoint: true  # Chain pauses here

At a checkpoint:

Chain pauses and shows summary
User reviews artifacts and progress
/skill-chain-prompts resume continues
Or user can modify, redo, or abort

Best Practices

Start with pre-built chains — Customize as needed
Use checkpoints — Add after critical steps for review
Mark optional steps — Deployment, documentation often optional
Keep chains focused — 3-7 steps is ideal
Pass context forward — Reference outputs from prior steps

References

references/chain-format.md — Complete YAML specification
references/execution-model.md — How chains are processed
references/state-tracking.md — Progress visualization formats
references/built-in-chains.md — All pre-built chains documented

Chain Templates

Pre-built chain files in assets/chains/:

api-development.yaml
fullstack-feature.yaml
career-preparation.yaml
mcp-development.yaml
custom-chain.yaml — Blank template

Install skill-chain-prompts and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "4444j99-a-i-skills-skill-chain-prompts", "kind": "skill", "name": "skill-chain-prompts", "description": "Orchestrate multi-skill workflows with prompt-based skill chaining. Define sequential or parallel skill invocations using YAML chain definitions, track progress through chains, and use pre-built chains for development, documentation, and career workflows. Use when coordinating multiple skills for complex tasks.", "publisher": "4444j99", "version": "1.0.0", "capabilities": { "domains": [ "coding", "hr" ], "tags": [ "skill-md", "orchestration", "workflow", "chaining", "multi-skill", "automation", "meta", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Orchestrate multi-skill workflows with prompt-based skill chaining. Define sequential or parallel skill invocations using YAML chain definitions, track progress through chains, and use pre-built chains for development, documentation, and career workflows. Use when coordinating multiple skills for complex tasks." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/4444j99/a-i--skills", "path": "skills/tools/skill-chain-prompts/SKILL.md", "ref": "HEAD", "url": "https://github.com/4444j99/a-i--skills/blob/HEAD/skills/tools/skill-chain-prompts/SKILL.md", "key": "4444j99/a-i--skills/skills/tools/skill-chain-prompts/SKILL.md" }, "license": "MIT" }, "instructions": "# Skill Chain Prompts\n\nOrchestrate complex workflows by chaining multiple skills together. Define sequences, track progress, and use pre-built chains for common development patterns.\n\n## Concept\n\nA **chain** is a sequence of skills that work together to accomplish a larger goal. Each step invokes a skill, passes context forward, and tracks completion. Chains work through Claude's sequential processing—no external engine required.\n\n## Quick Reference\n\n### Chain Format\n\n```yaml\nchain:\n name: \"my-workflow\"\n description: \"What this chain accomplishes\"\n\nsteps:\n - id: first\n skill: skill-name\n", "cost": { "context_tokens": 1396 } }

skill-chain-prompts

About