skill-recipes

Compose reusable skill workflows with frontmatter metadata, telemetry, and versioning.

1|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/GodSpeedAI/SEA --skill skill-recipes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-recipes
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/skill-recipes
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill skill-recipes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to compose, orchestrate, and govern complex skill workflows by packaging reusable recipes that connect skills, capture telemetry, and manage evolution.

Core Features & Use Cases

  • Skill Chaining: connect multiple skills into end-to-end pipelines.
  • Skill Telemetry: instrument executions and observe behaviors.
  • Visual Catalog: map relationships and dependencies between skills.
  • Skill Versioning: track changes and evolution over time across deployments.

Quick Start

Create a sample recipe that chains skill-creator with pm-agent-orchestration, enables basic telemetry, and generates a visual catalog for the workflow.

Frequently Asked Questions about skill-recipes

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

FAQPage Schema
How do I compose complex skill workflows into reusable pipelines?

To instrument skill telemetry, you apply the recipe's telemetry patterns to observe skill executions and behaviors within your orchestrated pipelines. This allows teams to monitor multi-skill workflows and track operational metrics across deployments.

What is the best way to track skill versioning across evolving deployments?

Skill versioning is tracked by defining frontmatter-based metadata within your recipes to manage changes and evolution over time. This approach governs skill deployments and ensures consistent version tracking across environments.

Can I visualize skill relationships and dependencies for orchestrated pipelines?

You can visualize skill relationships by generating a visual catalog that maps dependencies between connected skills. This provides a clear overview of your multi-skill pipelines and helps teams understand complex workflow architectures.

Do I need specific components to build multi-skill pipelines with recipes?

Building multi-skill pipelines requires no specific dependencies, as recipes support optional components like scripts, references, and assets. You define frontmatter-based metadata to chain skills and govern the workflow without rigid component requirements.

When should I not use recipes for skill orchestration?

You should avoid recipes for skill orchestration when managing isolated, single-skill tasks that do not require chaining, telemetry, or versioning. The recipe overhead is unnecessary for simple deployments lacking complex multi-skill pipeline dependencies.