Agent skill

Workflow Skill Designer

by catlog22 in catlog22/Claude-Code-Workflow

Meta-skill for designing orchestrator+phases structured workflow skills.

MITAuto-check: notesDevelopment

Install Workflow Skill Designer

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill workflow-skill-designer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow workflow-skill-designer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/workflow-skill-designer .claude/skills/workflow-skill-designer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-skill-designer
GitHub stars
2.1k
Token cost
~4.4k tokens
SKILL.md length
1,007 words
Files
5
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Meta-skill for designing orchestrator+phases structured workflow skills.

  • Design workflow skill
  • SKILL.md covers Architecture Overview, Target Output Structure, Core Design Patterns and Execution Flow, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Create workflow skill

What it does

Workflow Skill Designer is an agent skill from catlog22/Claude-Code-Workflow. Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on "design workflow skill", "create workflow skill", "workflow skill designer".

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `phases/01-requirements-analysis.md`, `phases/02-orchestrator-design.md` and `phases/03-phase-design.md`).

It sits in Development. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Design workflow skill
  • Create workflow skill
  • Workflow skill designer

Example prompts

  • “design workflow skill”
  • “create workflow skill”
  • “workflow skill designer”
  • “/workflow-skill-designer”

Requirements

  • Pre-approved tools (allowed-tools): Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Agent
    • AskUserQuestion
    • TodoWrite
    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Skill Designer loads about 4.4k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 1,007 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 1,007 words, ~4,427 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-skill-designer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
workflow-skill-designer
description
Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on "design workflow skill", "create workflow skill", "workflow skill designer".
allowed-tools
Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep

Workflow Skill Designer

Meta-skill for creating structured workflow skills following the orchestrator + phases pattern. Generates complete skill packages with SKILL.md as coordinator and phases/ folder for execution details.

Architecture Overview

┌─────────────────────────────────────────────────────────────────┐
│  Workflow Skill Designer                                         │
│  → Analyze requirements → Design orchestrator → Generate phases  │
└───────────────┬─────────────────────────────────────────────────┘
                │
    ┌───────────┼───────────┬───────────┐
    ↓           ↓           ↓           ↓
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ Phase 1 │ │ Phase 2 │ │ Phase 3 │ │ Phase 4 │
│ Require │ │  Orch   │ │ Phases  │ │ Valid   │
│ Analysis│ │ Design  │ │ Design  │ │ & Integ │
└─────────┘ └─────────┘ └─────────┘ └─────────┘
     ↓           ↓           ↓           ↓
  workflow    SKILL.md    phases/     Complete
  config     generated   0N-*.md     skill pkg

Target Output Structure

The skill this meta-skill produces follows this structure:

.claude/skills/{skill-name}/
├── SKILL.md                    # Orchestrator: coordination, data flow, TodoWrite
├── phases/
│   ├── 01-{phase-name}.md      # Phase execution detail (full content)
│   ├── 02-{phase-name}.md
│   ├── ...
│   └── 0N-{phase-name}.md
├── specs/                      # [Optional] Domain specifications
└── templates/                  # [Optional] Reusable templates

Core Design Patterns

Patterns extracted from successful workflow skill implementations (workflow-plan, project-analyze, etc.):

Pattern 1: Orchestrator + Progressive Loading

SKILL.md = Pure coordinator. Contains:

  • Architecture diagram (ASCII)
  • Execution flow with Ref: phases/0N-xxx.md markers
  • Phase Reference Documents table (read on-demand)
  • Data flow between phases
  • Core rules and error handling

Phase files = Full execution detail. Contains:

  • Complete agent prompts, bash commands, code implementations
  • Validation checklists, error handling
  • Input/Output specification
  • Next Phase link

Key Rule: SKILL.md references phase docs via Ref: markers. Phase docs are read only when that phase executes, not all at once.

Pattern 2: TodoWrite Attachment/Collapse
Phase starts:
  → Sub-tasks ATTACHED to TodoWrite (in_progress + pending)
  → Orchestrator executes sub-tasks sequentially

Phase ends:
  → Sub-tasks COLLAPSED back to high-level summary (completed)
  → Next phase begins
Pattern 3: Inter-Phase Data Flow
Phase N output → stored in memory/variable → Phase N+1 input
                  └─ or written to session file for persistence

Each phase receives outputs from prior phases via:

  • In-memory variables (sessionId, contextPath, etc.)
  • Session directory files (.workflow/active/{sessionId}/...)
  • Planning notes (accumulated constraints document)
Pattern 4: Conditional Phase Execution
Phase N output contains condition flag
  ├─ condition met → Execute Phase N+1
  └─ condition not met → Skip to Phase N+2
Pattern 5: Input Structuring

User input (free text) → Structured format before Phase 1:

GOAL: [objective]
SCOPE: [boundaries]
CONTEXT: [background/constraints]
Pattern 6: Interactive Preference Collection (SKILL.md Responsibility)

Workflow preferences (auto mode, force explore, etc.) MUST be collected via AskUserQuestion in SKILL.md before dispatching to phases. Phases reference these as workflowPreferences.{key} context variables.

Anti-Pattern: Command-line flags (--yes, -e, --explore) parsed within phase files via $ARGUMENTS.includes(...).

javascript
// CORRECT: In SKILL.md (before phase dispatch)
const prefResponse = AskUserQuestion({
  questions: [
    { question: "是否跳过确认?", header: "Auto Mode", options: [
      { label: "Interactive (Recommended)", description: "交互模式" },
      { label: "Auto", description: "跳过所有确认" }
    ]}
  ]
})
workflowPreferences = { autoYes: prefResponse.autoMode === 'Auto' }

// CORRECT: In phase files (reference only)
const autoYes = workflowPreferences.autoYes

// WRONG: In phase files (flag parsing)
const autoYes = $ARGUMENTS.includes('--yes') || $ARGUMENTS.includes('-y')
Pattern 7: Direct Phase Handoff

When one phase needs to invoke another phase within the same skill, read and execute the phase document directly. Do NOT use Skill() routing back through SKILL.md.

javascript
// CORRECT: Direct handoff (executionContext already set)
Read("phases/02-lite-execute.md")
// Execute with executionContext (Mode 1)

// WRONG: Skill routing (unnecessary round-trip)
Skill(skill="workflow-lite-plan", args="--in-memory")
Pattern 8: Phase File Hygiene

Phase files are internal execution documents. They MUST NOT contain:

ProhibitedReasonCorrect Location
Flag parsing ($ARGUMENTS.includes(...))Preferences collected in SKILL.mdSKILL.md via AskUserQuestion
Invocation syntax (/skill-name "...")Not user-facing docsRemoved or SKILL.md only
Conversion provenance (Source: Converted from...)Implementation detailRemoved
Skill routing for inter-phase (Skill(skill="..."))Use direct phase readDirect Read("phases/...")
Pattern 9: Compact Recovery (Phase Persistence)

Multi-phase workflows span long conversations. Context compression (compact) will naturally summarize earlier phase documents. The strategy uses 双重保险: TodoWrite 跟踪 active phase 保护其不被压缩,sentinel 作为兜底在压缩发生时触发恢复。

Design principle: TodoWrite in_progress = active phase → protect from compact | Sentinel = re-read fallback if protection fails.

Double insurance mechanism:

LayerRoleMechanism
1. Active Phase Protection预防TodoWrite in_progress 标记当前 phase → compact 时保留该 phase 完整内容,不压缩
2. Sentinel Re-read恢复Phase 文件嵌入标识符 → 若仍被压缩,检测到 sentinel-only 状态时立即 re-read

When to apply: 任何通过 direct handoff (Pattern 7) 跨 phase 执行的场景,尤其是后续 phase 包含复杂执行协议(多 Step、agent 调度、CLI 编排)时。


Layer 1: Active Phase Protection (TodoWrite 联动)

TodoWrite 已经跟踪每个 phase 的执行状态。利用此信息驱动 compact 策略:

TodoWrite status → Compact behavior:
  ┌─ completed  → ✅ 可压缩(已完成,不再需要完整内容)
  ├─ in_progress → 🛡️ 禁止压缩(正在执行,必须保留完整协议)
  └─ pending    → ✅ 可压缩(尚未加载,无内容)

SKILL.md Execution Flow 中标注 compact 联动:

markdown
## Execution Flow

> **⚠️ COMPACT DIRECTIVE**: Context compression MUST check TodoWrite phase status.
> The phase currently marked `in_progress` is the active execution phase — preserve its FULL content.
> Only compress phases marked `completed` or `pending`.

Phase 1: Requirements Analysis    ← TodoWrite tracks status
   └─ Ref: phases/01-xxx.md
Phase 2: Execution Engine         ← TodoWrite tracks status
   └─ Ref: phases/02-xxx.md
...

TodoWrite 状态转换 时自动更新 compact 保护范围:

Phase 1: in_progress 🛡️  →  completed ✅   (compact 可压缩 Phase 1)
Phase 2: pending ✅       →  in_progress 🛡️ (compact 保护 Phase 2)

Layer 2: Sentinel Re-read (兜底恢复)

即使有 Layer 1 保护,compact 仍可能在极端场景(超长上下文、多轮 agent 调度)下压缩 active phase。Sentinel 确保恢复能力:

Phase 文件顶部嵌入 sentinel:

markdown
> **📌 COMPACT SENTINEL [Phase N: {phase-name}]**
> This phase contains {M} execution steps (Step N.1 — N.{M}).
> If you can read this sentinel but cannot find the full Step protocol below, context has been compressed.
> Recovery: `Read("phases/0N-xxx.md")`

Sentinel 设计特点:

  • 结构化、醒目 → compact 会将其作为关键信息保留在摘要中
  • 包含 step 数量 → 提供自检依据("应该看到 M 个 Step,但只有摘要")
  • 包含 re-read 路径 → 无需查表即可恢复

Phase Reference Table (整合双重保险)
markdown
| Phase | Document | Purpose | Compact |
|-------|----------|---------|---------|
| 1 | phases/01-xxx.md | Planning | TodoWrite 驱动 |
| 2 | phases/02-xxx.md | Execution | TodoWrite 驱动 + 🔄 sentinel |

**Compact Rules**:
1. **TodoWrite `in_progress`** → 保留完整内容,禁止压缩
2. **TodoWrite `completed`** → 可压缩为摘要
3. **🔄 sentinel fallback** → 带此标记的 phase 包含 compact sentinel;若 compact 后仅存 sentinel 而无完整 Step 协议,**必须立即 `Read("phases/0N-xxx.md")` 恢复后再继续**

Checkpoint (执行步骤前双重验证)
markdown
> **⚠️ CHECKPOINT**: Before proceeding, verify:
> 1. This phase is TodoWrite `in_progress` (active phase protection)
> 2. Full protocol (Step N.X — N.{M}) is in active memory, not just sentinel
> If only sentinel remains → `Read("phases/0N-xxx.md")` now.
Handoff 注释
javascript
// Phase N is tracked by TodoWrite — active phase protection applies.
// Sentinel fallback: if compressed despite protection, re-read triggers automatically.
Read("phases/0N-xxx.md")

Execution Flow

Phase 1: Requirements Analysis
   └─ Ref: phases/01-requirements-analysis.md
      ├─ Input source: commands, descriptions, user interaction
      └─ Output: workflowConfig (phases, data flow, agents, conditions)

Phase 2: Orchestrator Design (SKILL.md)
   └─ Ref: phases/02-orchestrator-design.md
      ├─ Input: workflowConfig
      └─ Output: .claude/skills/{name}/SKILL.md

Phase 3: Phase Files Design
   └─ Ref: phases/03-phase-design.md
      ├─ Input: workflowConfig + source content
      └─ Output: .claude/skills/{name}/phases/0N-*.md

Phase 4: Validation & Integration
   └─ Ref: phases/04-validation.md
      └─ Output: Validated skill package

Phase Reference Documents (read on-demand):

PhaseDocumentPurpose
1phases/01-requirements-analysis.mdAnalyze workflow requirements from various sources
2phases/02-orchestrator-design.mdGenerate SKILL.md with orchestration patterns
3phases/03-phase-design.mdGenerate phase files preserving full execution detail
4phases/04-validation.mdValidate structure, references, and integration

Input Sources

This meta-skill accepts workflow definitions from multiple sources:

SourceDescriptionExample
Existing commandsConvert .claude/commands/ orchestrator + sub-commandsplan.md + session/start.md + tools/*.md
Text descriptionUser describes workflow in natural language"Create a 3-phase code review workflow"
Requirements docStructured requirements filerequirements.md with phases/agents/outputs
Existing skillRefactor/redesign an existing skillRestructure a flat skill into phases

Frontmatter Conversion Rules

When converting from command format to skill format:

Command FieldSkill FieldTransformation
namenamePrefix with group: plan → workflow-plan
descriptiondescriptionAppend trigger phrase: Triggers on "xxx"
argument-hint(removed)Arguments handled in Input Processing section
examples(removed)Examples moved to inline documentation
allowed-toolsallowed-toolsExpand wildcards: Skill(*) → Skill, add commonly needed tools
group(removed)Embedded in name prefix
Show full SKILL.md (378 more words)Show less

Orchestrator Content Mapping

What goes into SKILL.md vs what goes into phase files:

SKILL.md (Coordinator)
SectionContentSource
Frontmattername, description, allowed-toolsCommand frontmatter (converted)
Architecture OverviewASCII diagram of phase flowDerived from execution structure
Key Design PrinciplesCoordination rulesExtracted from command coordinator role
Execution FlowPhase sequence with Ref: markers + Phase Reference tableCommand execution process
Core RulesOrchestration constraintsCommand core rules
Input ProcessingStructured format conversionCommand input processing
Data FlowInter-phase data passingCommand data flow
TodoWrite PatternAttachment/collapse lifecycleCommand TodoWrite sections
Post-Phase UpdatesPlanning notes / state updates between phasesCommand inter-phase update code
Error HandlingFailure recoveryCommand error handling
Coordinator ChecklistPre/post phase actionsCommand coordinator checklist
Related CommandsPrerequisites and follow-upsCommand related commands
Phase Files (Execution Detail)
ContentRule
Full agent promptsPreserve verbatim from source command
Bash command blocksPreserve verbatim
Code implementationsPreserve verbatim
Validation checklistsPreserve verbatim
Error handling detailsPreserve verbatim
Input/Output specAdd if not present in source
Phase headerAdd # Phase N: {Name}
Objective sectionAdd ## Objective with bullet points
Next Phase linkAdd ## Next Phase with link to next

Critical Rule: Phase files must be content-faithful to their source. Do NOT summarize, abbreviate, or simplify. The phase file IS the execution instruction - every bash command, every agent prompt, every validation step must be preserved.

SKILL.md Template

markdown
---
name: {skill-name}
description: {description}. Triggers on "{trigger1}", "{trigger2}".
allowed-tools: {tools}
---

# {Title}

{One-paragraph description of what this skill does and what it produces.}

## Architecture Overview

{ASCII diagram showing phases and data flow}

## Key Design Principles

1. **{Principle}**: {Description}
...

## Interactive Preference Collection

Collect workflow preferences via AskUserQuestion before dispatching to phases:
{AskUserQuestion code with preference derivation → workflowPreferences}

## Auto Mode Defaults

When `workflowPreferences.autoYes === true`: {auto-mode behavior}.

## Execution Flow

{Phase sequence with Ref: markers}

**Phase Reference Documents** (read on-demand when phase executes):

| Phase | Document | Purpose | Compact |
|-------|----------|---------|---------|
| 1 | [phases/01-xxx.md](phases/01-xxx.md) | ... | TodoWrite 驱动 |
| N | [phases/0N-xxx.md](phases/0N-xxx.md) | ... | TodoWrite 驱动 + 🔄 sentinel |
...

**Compact Rules**:
1. **TodoWrite `in_progress`** → 保留完整内容,禁止压缩
2. **TodoWrite `completed`** → 可压缩为摘要
3. **🔄 sentinel fallback** → 带此标记的 phase 包含 compact sentinel;若 compact 后仅存 sentinel 而无完整 Step 协议,必须立即 `Read()` 恢复

## Core Rules

1. {Rule}
...

## Input Processing

{How user input is converted to structured format}

## Data Flow

{Inter-phase data passing diagram}

## TodoWrite Pattern

{Attachment/collapse lifecycle description with examples}

## Post-Phase Updates

{State updates between phases}

## Error Handling

{Failure recovery rules}

## Coordinator Checklist

{Pre/post phase action list}

## Related Commands

{Prerequisites and follow-ups}

Phase File Template

markdown
# Phase N: {Phase Name}

> **📌 COMPACT SENTINEL [Phase N: {phase-name}]**
> This phase contains {M} execution steps (Step N.1 — N.{M}).
> If you can read this sentinel but cannot find the full Step protocol below, context has been compressed.
> Recovery: `Read("phases/0N-xxx.md")`
> _(Include for phases marked 🔄 in SKILL.md Phase Reference table — see Pattern 9)_

{One-sentence description of this phase's goal.}

## Objective

- {Goal 1}
- {Goal 2}

## Execution

### Step N.1: {Step Name}

{Full execution detail: commands, agent prompts, code}

### Step N.2: {Step Name}

> **⚠️ CHECKPOINT**: Before proceeding, verify:
> 1. This phase is TodoWrite `in_progress` (active phase protection)
> 2. Full protocol (Step N.X — N.{M}) is in active memory, not just sentinel
> If only sentinel remains → `Read("phases/0N-xxx.md")` now.
> _(Add checkpoints before critical execution steps: agent dispatch, CLI launch, review — see Pattern 9)_

{Full execution detail}

## Output

- **Variable**: `{variableName}` (e.g., `sessionId`)
- **File**: `{output file path}`
- **TodoWrite**: Mark Phase N completed, Phase N+1 in_progress

## Next Phase

Return to orchestrator, then auto-continue to [Phase N+1: xxx](0N+1-xxx.md).

Design Decision Framework

When designing a new workflow skill, answer these questions:

QuestionImpactExample
How many phases?Directory structure3-7 phases typical
Which phases are conditional?Orchestrator logic"Phase 3 only if conflict_risk >= medium"
What data flows between phases?Data Flow sectionsessionId, contextPath, configFlags
Which phases use agents?Phase file complexityAgent prompts need verbatim preservation
What's the TodoWrite granularity?TodoWrite PatternSome phases have sub-tasks, others are atomic
Is there a planning notes pattern?Post-Phase UpdatesAccumulated state document across phases
What's the error recovery?Error HandlingRetry once then report, vs rollback
Does it need preference collection?Interactive Preference CollectionCollect via AskUserQuestion in SKILL.md, pass as workflowPreferences
Does phase N hand off to phase M?Direct Phase Handoff (Pattern 7)Read phase doc directly, not Skill() routing
Will later phases run after long context?Compact Recovery (Pattern 9)Add sentinel + checkpoints, mark 🔄 in Phase Reference table

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in .claude/skills/workflow-skill-designer of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • phases/01-requirements-analysis.md
  • phases/02-orchestrator-design.md
  • phases/03-phase-design.md
  • phases/04-validation.md

Open the folder on GitHubat commit 07491b0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in catlog22/Claude-Code-Workflow, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Workflow Skill Designer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Skill Designer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Skill Designer this skillcatlog22/Claude-Code-Workflow2.1k—~4.4kAutomated safety check: NotesMIT
Diagram Designcathrynlavery/diagram-design45k1 repos~7.5kAutomated safety check: PassMIT
Excalidraw Canvas Toolkitlingzhi227/agent-research-skills384—~3.8kAutomated safety check: PassNone
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0

Similar skills

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    45k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed
  • Excalidraw Canvas Toolkit

    lingzhi227/agent-research-skills

    Draws and refines Excalidraw diagrams on a live canvas through MCP tools or a REST API, with screenshots, file import and export, snapshots and Mermaid conversion.

    384 GitHub stars~3.8k tokensUpdated 7 mo ago
    DevelopmentAuto-check passed
  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Prompt Generator

    catlog22/Claude-Code-Workflow

    Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.

    2.1k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Team Ultra Analyze

    catlog22/Claude-Code-Workflow

    Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check: notes
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Workflow Skill Designer

What does Workflow Skill Designer do?

Meta-skill for designing orchestrator+phases structured workflow skills. Workflow Skill Designer is an agent skill from catlog22/Claude-Code-Workflow. Meta-skill for designing orchestrator+phases structured workflow skills.

When should I use Workflow Skill Designer?

Workflow Skill Designer fits situations like: design workflow skill; create workflow skill; workflow skill designer.

How do I install Workflow Skill Designer in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-skill-designer -a claude-code`. Or copy the skill folder (.claude/skills/workflow-skill-designer in catlog22/Claude-Code-Workflow) into .claude/skills/workflow-skill-designer in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Skill Designer in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-skill-designer -a codex`. Or copy the skill folder (.claude/skills/workflow-skill-designer in catlog22/Claude-Code-Workflow) into .agents/skills/workflow-skill-designer in your project. Codex loads it when a task matches its description.

Can I use Workflow Skill Designer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-skill-designer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-skill-designer, .gemini/skills/workflow-skill-designer, .github/skills/workflow-skill-designer and .opencode/skills/workflow-skill-designer in your project.

What does Workflow Skill Designer need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Skill Designer is instructions for the agent only. Its frontmatter pre-approves these tools: Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep.

Does Workflow Skill Designer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflow Skill Designer safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Workflow Skill Designer use?

Workflow Skill Designer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Skill Designer use?

About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow Skill Designer?

Skills that share tags, products or a category with Workflow Skill Designer: Diagram Design (cathrynlavery/diagram-design, 45k stars), Excalidraw Canvas Toolkit (lingzhi227/agent-research-skills, 384 stars), Vercel Composition Patterns (supabase/supabase, 111k stars) and Finishing a Development Branch (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Skill Designer?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.