Streamline

This is your complexity pruning tool for when an agentic workflow has gotten too heavy. It walks you through a systematic analysis of every pipeline step, tool, and config parameter to find what's adding weight without adding value. The approach is surgical: merge overlapping tools, remove validation that duplicates downstream checks, and consolidate sequential steps that could be a single prompt. What I appreciate is the explicit complexity scoring table and the hard rules about never removing error handling or safety guardrails in the name of simplicity. It requires you to justify each component with concrete value and verify your golden test set still passes after each change. Best used when you've been iterating fast and accumulated cruft, or when you suspect you're paying latency costs for components that aren't pulling their weight.

skills.sh installs: 342
GitHub stars: 602
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add sharpdeveye/maestro --skill streamline --agent claude-code

Installs into .claude/skills of the current project.

Files

MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Consult the agent-architecture reference in the agent-workflow skill for complexity assessment and topology simplification.

Reduce complexity without reducing capability. Every component should earn its place.

Streamlining Analysis

For each component, ask:

Does this add measurable value? If you can't name the specific value, remove it.
Can this be combined with another component? Merge overlapping responsibilities.
Is this solving a real problem or an imagined one? Remove speculative complexity.
Would a simpler alternative work? Prefer simplicity over elegance.