workflow-skill-creator

from adaptationio/skrillz

No description

1 stars0 forksUpdated Jan 16, 2026
npx skills add https://github.com/adaptationio/skrillz --skill workflow-skill-creator

SKILL.md

Workflow Skill Creator

Overview

workflow-skill-creator provides a systematic workflow for composing multiple existing skills into integrated workflows. It enables creating higher-level skills that orchestrate sequences of other skills, manage dependencies, and automate complex multi-step processes.

Purpose: Build workflow skills that compose and orchestrate existing skills

Pattern: Workflow-based (5-step process)

Key Benefit: Transform multiple standalone skills into cohesive, automated workflows

When to Use

Use workflow-skill-creator when:

  • Building complex multi-step processes
  • Orchestrating multiple existing skills
  • Creating end-to-end automation workflows
  • Standardizing common skill sequences
  • Building domain-specific workflow skills
  • Automating repetitive multi-skill tasks

Prerequisites

Before creating workflow skills:

  • Existing skills: Have 2+ skills to compose
  • Clear goal: Know the workflow objective
  • Dependencies understood: Know skill execution order
  • Integration points: Understand skill inputs/outputs

Workflow Composition Process

Step 1: Identify Component Skills

Determine which existing skills will be composed into the workflow.

What to Identify:

  1. Workflow Objective:

    • What does the workflow accomplish end-to-end?
    • What problem does it solve?
    • Who will use it?
    • What's the expected outcome?
  2. Required Capabilities:

    • What actions are needed?
    • What expertise is required?
    • What tools must be used?
    • What validations are needed?
  3. Candidate Skills:

    • Which existing skills provide needed capabilities?
    • Are all required skills available?
    • Are some skills missing (need to build)?
    • Are some skills optional (nice-to-have)?
  4. Skill Assessment:

    • Does each skill do exactly what's needed?
    • Are skills well-documented?
    • Are skills tested and reliable?
    • Are there alternative skills?

Assessment Template:

# Workflow: [Name]

## Objective:
[What the workflow accomplishes]

## Required Capabilities:
1. [Capability 1]: [What's needed]
2. [Capability 2]: [What's needed]
3. [Capability 3]: [What's needed]

## Component Skills:

### Skill 1: [Name]
- **Provides**: [Capability]
- **Status**: Available/Needs Building
- **Quality**: Tested/Untested
- **Alternative**: [Other options if any]

### Skill 2: [Name]
[Same structure]

## Gaps:
- [Missing capability 1]
- [Missing capability 2]

## Next Steps:
1. [Build missing skill X]
2. [Validate skill Y]

Example:

# Workflow: Skill Development

## Objective:
Complete end-to-end skill development from research to validated, production-ready skill.

## Required Capabilities:
1. Research: Gather patterns, best practices, examples
2. Planning: Design skill structure, define scope
3. Task Breakdown: Create detailed task list with estimates
4. Progress Tracking: Monitor completion, identify blockers
5. Prompt Building: Create high-quality prompts for operations

## Component Skills:

### Skill 1: skill-researcher
- **Provides**: Research capability (web, GitHub, MCP, docs)
- **Status**: Available
- **Quality**: Tested, production-ready
- **Alternative**: Manual research (slower)

### Skill 2: planning-architect
- **Provides**: Skill planning and architecture design
- **Status**: Available
- **Quality**: Tested, production-ready
- **Alternative**: Manual planning (less structured)

### Skill 3: task-development
- **Provides**: Task breakdown with estimates and dependencies
- **Status**: Available
- **Quality**: Tested, production-ready
- **Alternative**: Manual task listing

### Skill 4: todo-management
- **Provides**: Progress tracking and momentum
- **Status**: Available
- **Quality**: Tested, production-ready
- **Alternative**: Manual tracking (less systematic)

### Skill 5: prompt-builder
- **Provides**: High-quality prompt creation
- **Status**: Available
- **Quality**: Tested, production-ready
- **Alternative**: Ad-hoc prompts (lower quality)

## Gaps:
- None (all required skills available)

## Next Steps:
1. Map dependencies between skills
2. Design workflow structure

Questions to Answer:

  • What skills are essential vs. optional?
  • Are all required skills available and working?
  • What needs to be built before composing?
  • Are there alternative skill choices?

Validation:

  • Workflow objective clearly defined
  • All required capabilities identified
  • Component skills listed with status
  • Gaps identified
  • Assessment complete

→ Output: Component skill list with assessment

→ Next: Map how skills flow and depend on each other

Step 2: Map Dependencies & Flow

Define the execution order and dependencies between component skills.

What to Map:

  1. Execution Sequence:

    • What order should skills execute?
    • Which skills depend on others?
    • What can run in parallel?
    • What must be sequential?
  2. Data Flow:

    • What does each

...

Read full content

Repository Stats

Stars1
Forks0