plugins/meta/skills/discover-workflows/SKILL.md
Research and catalog workflows from external Claude Code repositories
npx skillsauth add coalesce-labs/catalyst discover-workflowsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are tasked with researching external Claude Code repositories to discover, analyze, and catalog their agents, commands, and workflow patterns.
This command helps you learn from the Claude Code community by analyzing workflow repositories and extracting reusable patterns.
Default repositories to research:
catlog22/Claude-Code-Workflow - Multi-agent automationautomazeio/ccpm - Project management systemwshobson/commands - Production slash commandswshobson/agents - Production subagentsqdhenry/Claude-Command-Suite - 148+ commands, 54 agentsVoltAgent/awesome-claude-code-subagents - 100+ subagentshesreallyhim/awesome-claude-code - Curated commands/agentsfeiskyer/claude-code-settings - Workflow improvementsOneRedOak/claude-code-workflows - Code review workflowsanthropics/claude-code - Official Claude Code repowinfunc/opcode - GUI toolkit for agents/commandsWhen invoked:
I'll research Claude Code workflows from external repositories.
Which repository would you like to explore?
1. wshobson/commands - Production slash commands
2. wshobson/agents - Production subagents
3. qdhenry/Claude-Command-Suite - 148+ commands
4. VoltAgent/awesome-claude-code-subagents - 100+ subagents
5. Custom repository (provide org/repo)
Or type 'all' to catalog all supported repos (this may take a while).
Get user selection or use provided parameter.
IMPORTANT: Spawn 3 parallel research tasks for efficiency and context isolation.
Use TodoWrite to track the 3 parallel research tasks.
Task 1 - Workflow Discovery:
Use external-research agent:
"Research {repo-name}. What commands and agents are available? List all workflows with brief descriptions of what each does."
Tools: mcp__deepwiki__read_wiki_structure, mcp__deepwiki__ask_question
Return: Complete list of all workflows found
Task 2 - Frontmatter Analysis:
Use external-research agent:
"Research {repo-name}. What frontmatter format is used for agents and commands? Provide specific examples showing all frontmatter fields used."
Tools: mcp__deepwiki__ask_question
Return: Frontmatter patterns with concrete examples
Task 3 - Implementation Patterns:
Use external-research agent:
"Research {repo-name}. What are the common implementation patterns, structures, and conventions used across workflows? Include naming conventions, file organization, and any templates."
Tools: mcp__deepwiki__ask_question
Return: Patterns, templates, conventions observed
WAIT for all 3 tasks to complete before proceeding.
Why parallel:
Combine findings from the 3 parallel research tasks:
Mark all 3 tasks complete in TodoWrite.
From the aggregated results, extract:
Available Workflows
Frontmatter Patterns
Implementation Patterns
Unique Features
Save research to thoughts/shared/workflows/{repo-name}/analysis.md:
# Workflow Analysis: {Repo Name}
**Repository**: {org/repo} **Analyzed**: {date} **Focus**: {agents/commands/both}
## Summary
[1-2 sentence overview of what this repo offers]
## Available Workflows
### Commands
1. **{command-name}**
- **Purpose**: [what it does]
- **Use when**: [scenario]
- **Frontmatter**:
```yaml
[actual frontmatter from repo]
```
2. **{command-name}** [...]
### Agents
1. **{agent-name}**
- **Purpose**: [what it does]
- **Tools**: [tools it uses]
- **Frontmatter**:
```yaml
[actual frontmatter from repo]
```
## Frontmatter Patterns
### Standard Fields
- name: [how they define it]
- description: [format they use]
- tools: [how specified]
- [other fields observed]
### Naming Conventions
- [pattern 1]
- [pattern 2]
## Implementation Patterns
### Common Structures
[Patterns you notice across workflows]
### Reusable Templates
[Templates that could be adapted]
## Unique Features
[Novel or interesting approaches]
## Integration Notes
[How these could integrate with your workspace]
## Recommendations
### High-Value Imports
1. **{workflow-name}** - [why it's valuable]
2. **{workflow-name}** - [why it's valuable]
### Patterns to Adopt
- [Pattern 1]: [how to use it]
- [Pattern 2]: [how to use it]
## References
- DeepWiki searches: [links]
- Repository: {URL}
- Analyzed on: {date}
Update thoughts/shared/workflows/catalog.md:
# Workflow Catalog
Discovered workflows from the Claude Code community.
## Repositories Analyzed
### wshobson/commands
- **Analyzed**: 2025-01-08
- **Workflows**: 15 commands
- **Focus**: Production-ready automation
- **Details**: [See analysis](wshobson-commands/analysis.md)
- **Top Picks**:
- code-review: Automated code review workflow
- refactor: Safe refactoring patterns
[... more repos]
## By Category
### Code Review
- wshobson/commands: code-review
- OneRedOak/claude-code-workflows: review-pr
### Documentation
- qdhenry/Claude-Command-Suite: doc-generator
- hesreallyhim/awesome-claude-code: readme-generator
[... more categories]
## By Use Case
### "I want to automate code reviews"
1. wshobson/commands/code-review
2. OneRedOak/claude-code-workflows/review-pr
3. [Details in respective analyses]
### "I need project management workflows"
1. automazeio/ccpm - Full PM system
2. [...]
Show user what was found:
# Discovery Results: {Repo Name}
## Summary
Discovered {N} workflows ({X} commands, {Y} agents)
## Highlights
### Top Workflows
1. **{name}** - {brief description}
2. **{name}** - {brief description}
3. **{name}** - {brief description}
### Interesting Patterns
- {Pattern 1}
- {Pattern 2}
### Recommended for Import
- **{workflow-name}**: {why}
## Next Steps
1. **Review the analysis**: `thoughts/shared/workflows/{repo}/analysis.md`
2. **Import a workflow**: `/catalyst-meta:import-workflow {repo} {workflow-name}`
3. **Discover another repo**: `/catalyst-meta:discover-workflows`
Catalog updated at: `thoughts/shared/workflows/catalog.md`
/catalyst-meta:discover-workflows all
This will:
Performance: ~10-15x faster than sequential research
Context efficiency: Each agent loads only its research area
/catalyst-meta:discover-workflows org/repo
Works with any public GitHub repo with Claude Code workflows.
/catalyst-meta:discover-workflows wshobson/agents --focus agents
Only analyzes agents, skips commands.
/catalyst-meta:import-workflow to actually import/catalyst-meta:discover-workflows (this command)/catalyst-meta:import-workflow (imports discovered workflows)/catalyst-meta:create-workflow (creates new using discovered patterns)/catalyst-meta:validate-frontmatter (ensures consistency)This command is the first step in workflow discovery and reuse!
testing
Phase-agent that fixes a failing verify verdict so the pipeline self-heals instead of stalling to needs-human (CTL-653). Reads `${ORCH_DIR}/workers/<ticket>/verify.json`, fixes the `findings[]` (every severity:"high" plus the regression_risk drivers) directly via Edit/Write, commits the remediation, and emits `phase.remediate.complete.<ticket>`. The scheduler's router then re-dispatches `verify` to re-check (the verify⇄remediate cycle, cap 3). Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.
tools
--- name: phase-triage description: Phase agent that triages a Linear ticket — expands acronyms, classifies (feature/bug/docs/refactor/chore), identifies genuine blockers (a semantic second-pass over the backlog — NOT a prose scrape; CTL-838), estimates scope, writes triage.json, and posts a triage analysis comment to Linear. Triage completion is signaled by that comment plus the local triage.json — there is no `triaged` label. Emits phase.triage.complete.<TICKET> on success and phase.triage.fai
tools
Phase agent for the research step of the 9-phase orchestrator pipeline (CTL-450). Wraps /catalyst-dev:research-codebase and produces thoughts/shared/research/<date>-<ticket>.md, then emits phase.research.complete.<ticket>. Reads triage.json from the worker dir as its prior-phase artifact. Spawned via plugins/dev/scripts/phase-agent-dispatch, which invokes it via slash command — hence `user-invocable: true`.
development
Phase-agent wrapper that opens the pull request after implementation completes (CTL-449 Initiative 1 Phase 3). Delegates to `/catalyst-dev:create-pr` (which already auto-runs `describe-pr` and transitions Linear to `inReview`), then writes the PR number + URL into the phase signal file so the downstream `phase-monitor-merge` agent can read it without re-querying GitHub. Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.