Skip to main content
skill CX Codex

workflow-optimizer — Claude Code skill: what it does, how to install

Analyzes agent DAGs, tool call transitions, and token expenses via the Agent Monitor API. Identifies retry loops, error flows, and model delegation waste.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill workflow-optimizer -a claude-code
Open on GitHub

What workflow-optimizer does

The skill connects to the Agent Monitor workflow intelligence API to pull telemetry across sessions. By querying GET /api/workflows/{sessionId}, it examines 11 structured datasets. These cover subagent orchestration graphs, tool transition matrices, concurrency lanes, and error propagation across hierarchy levels.

It also cross-references model delegation patterns against the GET /api/pricing endpoint. This highlights misallocated tasks, such as routing lightweight work to Opus instead of Haiku or Sonnet. The output delivers a prioritized table of top 5 recommendations with estimated cost savings and implementation effort.

The skill cannot operate without an active Agent Monitor instance providing the telemetry endpoints.

What it helps with

  • Detect redundant tool call loops and repeated execution failures
  • Trace error propagation through parent and child subagent trees
  • Rebalance model delegation to cut inference costs
  • Pinpoint sessions suffering from frequent context compaction

Example prompts for the agent

  • Run workflow-optimizer analyze on session session_12345 focusing on cost
  • Analyze tool call sequences with workflow-optimizer tools
  • Use workflow-optimizer to inspect subagent completion rates and concurrency bottlenecks

How to install workflow-optimizer

1Skills CLI (Vercel)

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill workflow-optimizer -a claude-code

2Manually: put the files in place

~/.claude/skills/workflow-optimizer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/workflow-optimizer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about workflow-optimizer

How do I install workflow-optimizer in Claude Code?

Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill workflow-optimizer -a claude-code. Alternatively, place the skill file into ~/.claude/skills/workflow-optimizer/SKILL.md.

What data sources does workflow-optimizer require?

It fetches session lists from GET /api/sessions, analytics from GET /api/analytics, pricing rules from GET /api/pricing, and 11 session metrics from GET /api/workflows/{sessionId}.

What does the optimization output contain?

It outputs a prioritized table highlighting the top 5 recommendations, complete with source data citations, implementation effort, and estimated cost savings.

Source text

SKILL.md · MIT
---
name: workflow-optimizer
description: >
  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.
---

# Workflow Optimizer

Analyze Claude Code workflows using the Agent Monitor's workflow intelligence engine.

## Input

The user provides: **$ARGUMENTS**

Options: "analyze", a session ID for single-session analysis, or a focus: "tools", "subagents", "cost", "errors".

## Data Sources

| 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 |

### Workflow Intelligence API (`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 |

## Optimization Analyses

### 1. Tool Flow Optimization
From `toolFlow` transition data:
- Identify the most common tool sequences (e.g., Read → Edit → Bash)
- Find redundant transitions (same tool called repeatedly = retries)
- Detect anti-patterns: high-frequency failure loops
- Recommend tool chain shortcuts

### 2. Subagent Strategy
From `effectiveness` + `orchestration`:
- Which subagent types (task, explore, code-review) have highest completion rates
- Average duration per subagent type — are subagents taking too long?
- Underutilized types: tasks that could benefit from delegation
- Over-spawning: too many subagents for simple tasks

### 3. Model Delegation Analysis
From `modelDelegation`:
- Which models handle which task types
- Cost-per-task comparison across models
- Opportunities to delegate simple tasks to cheaper models (Haiku/Sonnet instead of Opus)
- Calculate estimated savings from model rebalancing

### 4. Error Prevention
From `errorPropagation`:
- Where errors originate (agent depth level)
- How errors cascade to parent agents
- Error types (APIError, tool failure) by frequency
- Defensive strategies: which patterns lead to fewer errors

### 5. Concurrency Optimization
From `concurrency`:
- Which agents run in parallel vs sequential
- Bottlenecks: sequential agents that could be parallelized
- Resource contention: overlapping heavy tasks

### 6. Context Health
From `compaction`:
- How often compaction occurs per session
- Token recovery from compaction baselines
- Sessions that hit context limits — suggest breaking into smaller tasks

## Output

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.

© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set60

regression-alert Compares agent reliability this period against the last one and flags where it got worse. Handy when you need to know if things degraded. CX Codex +1 ★ 1,121repo stars hook-failure-audit Audits hook delivery health using Agent Monitor metrics, tracking unreturned tool calls, unclosed subagents, and stalled ingestion pipelines. CX Codex +1 ★ 1,121repo stars error-scan Scans recent Claude Code sessions for API errors and unfinished tool calls, then ranks failures by tool and model. Useful when you need to see what is breaking. CX Codex +1 ★ 1,121repo stars api-error-report Turns Agent Monitor data into a report on APIError events: how many, in which sessions and models, and what likely caused them. CX Codex +1 ★ 1,121repo stars weekly-report Turns Agent Monitor data into a weekly view of sessions, costs, tokens, tool use, and completion. Use it to review a chosen week or date range. CX Codex +1 ★ 1,121repo stars time-of-day Sorts sessions and events into hour-of-day and day-of-week bins, then marks peak and low-output windows. Useful when you plan a work schedule. CX Codex +1 ★ 1,121repo stars sprint-summary Summarizes Claude Code sprint activity using Agent Monitor data: session costs, model breakdown, project groupings, and velocity metrics. CX Codex +1 ★ 1,121repo stars monthly-review Builds a monthly retrospective from Agent Monitor data, comparing sessions, costs, tokens, and project activity. Use it to review the month and plan the next one. CX Codex +1 ★ 1,121repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor