roster-skill-health

Cluster friction log entries by theme and affected skill.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-skill-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster-skill-health
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-skill-health
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-skill-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated AI agent pipelines accumulate small, repeated friction points over time that are easy to miss individually but create significant systemic inefficiency. This Skill eliminates the guesswork from improving your pipeline by turning unstructured friction logs into prioritized, data-backed improvement proposals.

Core Features & Use Cases

  • Friction Log Analysis: Parses JSONL friction logs from pipeline runs to identify recurring issues, workarounds, and gaps in your agent workflow.
  • Thematic Clustering: Groups friction entries by shared theme, affected skill, and estimated effort to surface high-impact, actionable improvement opportunities.
  • Structured Proposals: Generates categorized, prioritized proposals for new skills, deterministic tools, skill adaptations, hooks, or dedicated agents, filtered to only include signals strong enough to act on.
  • Use Case: Run this Skill every 5-10 pipeline cycles to maintain a continuous improvement loop for your agent team, ensuring small friction points are addressed before they compound into major workflow blockers.

Quick Start

Ask the AI to run the roster-skill-health skill to analyze your project's friction log and generate a prioritized report of actionable pipeline improvement proposals.

Frequently Asked Questions about roster-skill-health

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

FAQPage Schema
How do I analyze agent pipeline friction logs to identify recurring workflow inefficiencies?

To analyze agent pipeline friction logs, you can parse accumulated JSONL entries from pipeline runs to cluster recurring issues by theme, affected skill, and estimated effort. This process surfaces systemic inefficiencies and generates prioritized, data-backed improvement proposals for your coordinated agent development teams.

What is a data-driven improvement metabolism for AI agent teams?

A data-driven improvement metabolism is a structured process that turns unstructured friction logs into prioritized proposals for new skills, deterministic tools, or dedicated agents. It ensures workflow improvements are only proposed when sufficient signal strength from logged friction data supports the action.

How do I prioritize AI agent workflow improvements from logged friction data?

You prioritize AI agent workflow improvements by clustering friction entries by shared theme, affected skill, and estimated effort. This thematic grouping filters signals to surface high-impact, actionable improvement opportunities, ensuring only proposals with sufficient signal strength are recommended.

Can I generate structured proposals for new agent skills from JSONL friction logs?

Yes, you can generate structured proposals for new agent skills by analyzing JSONL friction logs. The process categorizes and prioritizes proposals for new skills, deterministic tools, skill adaptations, hooks, or dedicated agents, filtered to only include signals strong enough to act on.

How often should I run a pipeline health check for my AI agent teams?

You should run a pipeline health check every 5-10 pipeline cycles to maintain a continuous improvement loop for your AI agent teams. This periodic friction analysis ensures small workflow issues are addressed before they compound into major systemic blockers.

What are the limitations of using friction log analysis for agent workflow optimization?

The limitation of friction log analysis is that it only generates proposals for new skills, tools, or agents when supported by sufficient signal strength from accumulated JSONL friction data. It requires continuous, periodic pipeline runs every 5-10 cycles to capture enough data to identify recurring systemic inefficiencies.