diagnose-agent

Analyze agent performance from git logs and learnings files to generate a struggle profile.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill diagnose-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-agent
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/diagnose-agent
Command: npx skills add https://github.com/tyevans/tackline --skill diagnose-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes an agent's historical performance and learning patterns to identify its strengths, weaknesses, and knowledge gaps, providing a clear profile for targeted improvement.

Core Features & Use Cases

  • Performance Profiling: Assesses an agent's historical learnings and commit activity to pinpoint areas of consistent success and recurring struggles.
  • Struggle Identification: Detects patterns like high churn in learnings or frequent fixes after feature implementation, indicating areas where the agent needs support.
  • Use Case: Before generating new training challenges for an agent, use this Skill to understand precisely where it excels and where it falters, ensuring training efforts are focused and effective.

Quick Start

Use the diagnose-agent skill to profile the agent named 'code-reviewer'.

Frequently Asked Questions about diagnose-agent

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

FAQPage Schema
How do I analyze agent performance using git history and learnings files?

To analyze agent performance, you examine historical learnings evolution and commit history to generate a struggle profile, identifying agent strengths, weaknesses, and knowledge gaps based on evidence from git logs and learnings files.

What is an agent struggle profile and how does it detect weaknesses?

An agent struggle profile detects weaknesses by examining historical learnings evolution and commit activity, pinpointing patterns like high churn in learnings or frequent fixes after feature implementation.

Do I need a team.yaml file to profile agent strengths and weaknesses?

Yes, profiling agent strengths and weaknesses requires the agent to be listed in team.yaml with ownership patterns and a populated learnings file with git history to provide evidence.

When should I diagnose an agent's historical performance before training?

You should diagnose an agent's historical performance before generating new training challenges to understand precisely where it excels and falters, ensuring training efforts are focused and effective.

Can I detect knowledge gaps from commit logs and learnings evolution?

Yes, you can detect knowledge gaps from commit logs and learnings evolution by analyzing historical performance data to identify recurring struggles and areas where the agent needs support.