Agentic Hub Docs
Portal & WorkflowsWorkflows

Usage Analysis

Workflow Usage Analysis

CE8 flywheel: Track → Analyze → Optimize → Track better.

Data Source

e:\Agentic\clara\workflow-usage.jsonl — one line per invocation.

Analysis Script

# Read and parse
$data = Get-Content "e:\Agentic\clara\workflow-usage.jsonl" | ForEach-Object { $_ | ConvertFrom-Json }

# Summary: count by workflow
$data | Group-Object wf | Sort-Object Count -Descending |
  Select-Object Count, Name | Format-Table

# Summary: count by workflow+mode
$data | Group-Object {"{0}/{1}" -f $_.wf, $_.mode} | Sort-Object Count -Descending |
  Select-Object Count, Name | Format-Table

# Daily distribution
$data | Group-Object { $_.ts.Substring(0,10) } | Sort-Object Name |
  Select-Object Name, Count | Format-Table

# Per-agent session activity
$data | Group-Object agent | Sort-Object Count -Descending |
  Select-Object Count, Name | Format-Table

# Unused workflows (compare against known list)
$known = @("task","commit","log","ongoing","qm","session","wrapup","akira","kb",
           "clara","vision","clarity","align","status","logarchive","skill","audy","handoff")
$used = $data | Select-Object -ExpandProperty wf -Unique
$unused = $known | Where-Object { $_ -notin $used }
Write-Host "`nUnused workflows:" ($unused -join ", ")

When to Analyze

TriggerScopeWho
/hub-auditFull analysis, flag unused/overusedAudy
/hub-evolveQuick counts, check for new patternsAkira
Weekly /clara alignWhich workflows supported the week's work?Clara
Monthly /vision alignWorkflow patterns vs life goals alignmentAgent

What to Look For

PatternSignalAction
Workflow never usedDead weight or undiscoveredRemove or promote
One mode dominatesOther modes may be unnecessaryConsider merging
High usage + high friction (from session quality)Optimization targetImprove the hot path
Workflow always paired with anotherComposition candidateMerge or create compound
Agent-specific usage patternsDifferent agents use different workflowsStandardize or specialize

Portal Integration (Future)

When ready to graduate from local JSONL to portal:

  1. New D1 table: workflow_usage (id, ts, workflow, mode, agent, session_id)
  2. API endpoint: POST /api/workflow-usage with batch insert
  3. Portal UI: New "Workflows" tab showing:
    • Usage heatmap (workflow × day)
    • Top workflows bar chart
    • Unused workflow alerts
    • Mode distribution per workflow
  4. Sync: /wrapup or daily cron pushes local JSONL → D1, then clears local

ETC: ~2-3 hours for D1+API+UI. Not urgent — local JSONL is sufficient until we have enough data to make it worthwhile.

On this page