> Analyze workflow patterns using the Agent Monitor's workflow intelligence API — orchestration DAGs, tool flow transitions, subagent effectiveness, model delegation patterns, error propagation by depth, concurrency lanes, compaction impact, and agent co-occurrence. Produces prioritized optimization recommendations with quantified impact.
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill workflow-optimizer
Analyze Claude Code workflows using the Agent Monitor's workflow intelligence engine.
The user provides: $ARGUMENTS
Options: "analyze", a session ID for single-session analysis, or a focus: "tools", "subagents", "cost", "errors".
| Endpoint | Returns |
|----------|---------|
| GET /api/sessions?limit=100 | Session list with metadata |
| GET /api/workflows/{sessionId} | 11 workflow datasets (see below) |
| GET /api/analytics | Tool usage top 20, event types, agent types |
| GET /api/pricing | Model pricing rules for cost comparison |
GET /api/workflows/{sessionId})Returns these 11 datasets per session:
| Dataset | Content |
|---------|---------|
| stats | Aggregate session stats: tool count, agent depth, event count |
| orchestration | DAG: agent nodes with parent/child edges, depths, types |
| toolFlow | Transition matrix: tool A → tool B with counts (common sequences) |
| effectiveness | Subagent success: per-type completion rates, avg duration, task success |
| patterns | Recurring sequences: detected workflow patterns with frequency |
| modelDelegation | Model choices: which models are delegated which tasks |
| errorPropagation | Error flow by depth: where in the agent tree errors originate and propagate |
| concurrency | Concurrency lanes: overlapping agent execution timelines |
| complexity | Complexity score: numerical score based on depth, breadth, tool diversity |
| compaction | Compaction impact: token savings, frequency, context health |
| cooccurrence | Agent pairs: which agents frequently run together |
From toolFlow transition data:
From effectiveness + orchestration:
From modelDelegation:
From errorPropagation:
From concurrency:
From compaction:
Prioritized recommendations table:
| # | Recommendation | Source Data | Impact | Effort | Est. Savings |
|---|---------------|-------------|--------|--------|-------------|
Top 5 recommendations with detailed explanation, supporting data from the workflow API, and implementation steps.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take hoangsonww/workflow-optimizer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.