workflow-optimizer

Correlate git history and staffing audits to identify agent retirement candidates.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mihai-chiorean/inc --skill workflow-optimizer-mihai-chiorean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-optimizer
Source: https://github.com/mihai-chiorean/inc/tree/main/skills/workflow-optimizer
Command: npx skills add https://github.com/mihai-chiorean/inc --skill workflow-optimizer-mihai-chiorean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of technical debt and cognitive friction within your AI agent roster by identifying redundant, underutilized, or poorly defined agents.

Core Features & Use Cases

  • Roster Health Analysis: Evaluates agent usage across projects to distinguish between essential tools and dead weight.
  • Friction Identification: Pinpoints recurring handoff issues and prompt-editing bottlenecks that slow down your development cycle.
  • Strategic Recommendations: Provides actionable advice on whether to retire, narrow, split, or merge agents based on empirical usage data and subjective user feedback.

Quick Start

Invoke the workflow optimizer to perform a comprehensive ergonomics review of your current agent roster and generate a health report.

Frequently Asked Questions about workflow-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify underutilized agents in my AI agent roster?

Analyze roster health by correlating git history and project-level staffing audits to identify redundant or poorly defined agents. This friction identification process exposes recurring handoff issues and prompt-editing bottlenecks that slow down your development cycle.

What is the best way to optimize agent scope definitions for peak performance?

Yes, optimizing agent rosters requires access to the staff CLI tool and git history to produce evidence-based recommendations. These dependencies provide the empirical usage data and project-level staffing audit information needed for roster restructuring.

How do I reduce cognitive friction and technical debt in my AI agent workflow?

Roster health analysis evaluates agent usage across projects to distinguish essential tools from dead weight. By correlating git history with project-level staffing audits, it identifies retirement candidates and optimizes agent scope definitions based on actual usage data.

Do I need the staff CLI tool to analyze agent roster ergonomics?

Perform a comprehensive ergonomics review across the entire agent repository to evaluate usage and identify friction. This review uses git history and user-reported friction patterns to generate a health report with actionable advice on retiring, narrowing, splitting, or merging agents.