debugging-workflows
Debug workflow execution issues including syntax errors, agent failures, variable problems, and execution errors. Use when workflows fail, produce unexpected results, or user asks for debugging help.
What this skill does
# Debugging Orchestration Workflows
I help diagnose and fix workflow execution issues using systematic debugging techniques.
## When I Activate
I activate when you:
- Experience workflow failures
- Get syntax errors
- Have agent execution issues
- Variables not working as expected
- Ask "why isn't this working?"
## Common Issues
### Syntax Errors
**Problem**: Workflow won't parse
**Symptoms**:
- "Unexpected token" errors
- "Invalid syntax" messages
- Workflow won't start
**Solutions**:
1. Check operator syntax: `->`, `||`, `~>` (not `=>` or `&&`)
2. Verify bracket matching: `[...]`
3. Check quote matching: `"instruction"`
4. Validate agent names (no typos)
### Agent Not Found
**Problem**: Agent reference doesn't resolve
**Symptoms**:
- "Agent 'X' not found"
- Execution stops at agent invocation
**Solutions**:
1. Check spelling of agent name
2. Verify temp agent file exists: `temp-agents/agent-name.md`
3. Check defined agent in registry: `agents/registry.json`
4. Ensure built-in agent name is correct
### Variable Issues
**Problem**: Variables not passing correctly
**Symptoms**:
- `{variable}` shows as literal text
- "Variable not found" errors
- Empty variable values
**Solutions**:
1. Verify capture syntax: `agent:"task":variable_name`
2. Check interpolation: `"Use {variable_name}"`
3. Ensure variable set before use
4. Check variable name spelling
### Parallel Execution Failures
**Problem**: Parallel tasks failing or hanging
**Symptoms**:
- Only some parallel tasks complete
- Workflow hangs at parallel section
- Inconsistent results
**Solutions**:
1. Ensure tasks are independent (no shared state)
2. Check syntax: `[task1 || task2 || task3]`
3. Verify each task can run standalone
4. Check for race conditions
### Checkpoint Issues
**Problem**: Checkpoints not triggering
**Symptoms**:
- Checkpoints skipped
- No user prompt shown
- Workflow continues without pause
**Solutions**:
1. Check checkpoint syntax: `@checkpoint-name`
2. Verify not in auto-mode
3. Ensure checkpoint is reachable in flow
## Debugging Process
### 1. Reproduce
Run workflow with minimal changes to reproduce issue.
### 2. Isolate
Simplify workflow to find problematic section:
```flow
# If this fails:
step1 -> step2 -> step3 -> step4
# Try:
step1 -> step2 # Works?
step3 -> step4 # Works?
```
### 3. Inspect
Check execution logs for error details.
### 4. Fix
Apply targeted fix based on findings.
### 5. Verify
Run full workflow to ensure fix works.
## Error Messages Guide
| Error | Meaning | Fix |
|-------|---------|-----|
| "Unexpected token" | Syntax error | Check syntax around error location |
| "Agent not found" | Missing agent | Verify agent exists and spelling |
| "Variable not found" | Variable undefined | Check variable was captured |
| "Condition failed" | Condition not met | Check condition logic |
| "Execution timeout" | Task took too long | Add timeout handling or simplify task |
## Best Practices
✅ **DO**:
- Start with simple workflow, add complexity gradually
- Test each section independently
- Use meaningful variable names
- Add error handling paths
- Capture outputs for debugging
❌ **DON'T**:
- Create overly complex workflows initially
- Skip testing individual steps
- Use cryptic variable names
- Ignore error messages
- Remove error handling
## Diagnostic Commands
```bash
# Check temp agents exist
ls temp-agents/
# Verify agent registry
cat agents/registry.json
# Check workflow syntax file
cat examples/workflow-name.flow
```
## Related Skills
- **creating-workflows**: Create well-structured workflows
- **executing-workflows**: Execute with better error visibility
- **managing-agents**: Debug agent-related issues
---
**Workflow not working? Show me the error and I'll help debug!**
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.