CtrlK
BlogDocsLog inGet started
Tessl Logo

tessleng/agent-insight-experiment

Scan a repository to surface actionable findings about agent performance. Analyzes source code, git history, GitHub data, agent logs, and agent context, then synthesizes cross-referenced findings with targeted actions informed by Tessl product awareness. Supports incremental multi-developer contributions and produces a self-contained HTML report.

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

README.md

Agent Insights

Scan a repository to surface actionable findings about coding agent performance, each with a targeted action recommendation.

What It Does

This plugin analyzes five data sources in parallel — source code, git history, GitHub PRs/CI, agent conversation logs, and agent configuration files — then cross-references and synthesizes the results into:

  • Overall Score: A one-word assessment of the repo's agent-readiness — blocked, constrained, or productive
  • Executive Summary: A short markdown paragraph giving a quick read on the state of the report before drilling into findings
  • Findings: Specific, evidence-backed issues affecting agent performance, categorized by the APEX taxonomy
  • Actions: Each finding carries an inline action — a targeted fix with rock-sized effort estimates (pebble/stone/rock/boulder) and Tessl product awareness (recommending plugins when appropriate)
  • HTML Report: A self-contained, shareable report with filtering, search, and evidence provenance trails

Quick Start

run-insight-scan

This orchestrates all five analyzers and the synthesis step, producing output in .tessl-insights-poc/ at the repo root.

Prerequisites

  • A git checkout of the target repository
  • gh CLI installed and authenticated (for GitHub data analysis)
  • Agent conversation logs on the machine (optional but recommended — from Cursor, Claude Code, etc.)

Multi-Developer Workflow

The scan results are designed to be committed to git so the whole team can contribute and benefit.

Initial scan (first developer)

  1. Run run-insight-scan to analyze the repo
  2. Review .tessl-insights-poc/report.html
  3. Commit .tessl-insights-poc/ to git

Additional contributions (other developers)

  1. Pull the latest .tessl-insights-poc/ from git
  2. Run contribute-agent-logs — this analyzes your local agent logs and re-runs synthesis
  3. Commit the updated .tessl-insights-poc/

Each developer's agent logs are saved separately (by username and date), so contributions are additive and don't overwrite each other. The synthesis step merges all available data on every run.

Output Structure

.tessl-insights-poc/
├── findings.json              # Synthesized findings with inline actions
├── report.html                # Self-contained HTML report
└── reports/                   # Raw analyzer outputs
    ├── source-code.json
    ├── git-history.json
    ├── github-data.json
    ├── agent-context.json
    └── agent-logs/
        ├── joe-20260408.json
        └── alice-20260410.json

Skills

SkillPurpose
run-insight-scanMain orchestrator — runs all analyzers and synthesis
analyze-source-codeExamines code patterns, internal libraries, build config
analyze-git-historyExamines file churn, co-changes, contributor concentration
analyze-github-dataExamines PRs, review comments, CI failures, issues
analyze-agent-logsExamines agent conversation histories for failure patterns
analyze-agent-contextExamines agent config files for quality, conflicts, gaps
synthesize-insightsCross-references reports, deduplicates findings, delegates action generation, generates HTML
generate-actionsGenerates targeted actions for each finding with Tessl product awareness
contribute-agent-logsAdds a developer's agent logs and re-runs synthesis
regenerate-reportRe-renders HTML report from existing findings.json without re-running analyzers

README.md

tile.json