tessleng/skill-insights
Scan a directory or workspace for SKILL.md files across all agents and repos, capture supporting files (references, scripts, linked docs), dedupe vendored copies, enrich each Tessl tile with registry signals, and emit a canonical JSON inventory validated by JSON Schema. Then run four analytical phases in parallel against the inventory — staleness + git provenance (history, broken refs, contributors), quality (Tessl `skill review`), duplicates (similarity + LLM judgement), registry-search (per-standalone-skill registry suggestions, HTTP only) — and render a self-contained interactive HTML report with a top-of-report health overview, top-issues panel, recently-changed list, and per-tessl.json manifests view.
84
90%
Does it follow best practices?
Impact
97%
1.44xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
duplicate-verdict.schema.jsonreferences/schemas/
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://tessl.io/skill-insights/duplicate-verdict.schema.json",
"title": "Skill Insights — Duplicate Verdict",
"description": "One JSON file written by a duplicate-judge subagent into <verdicts_dir>/<idx>.json. Returned verdict for the pair identified by `pair_id`. Consumed by finalize_duplicates.py.",
"type": "object",
"additionalProperties": false,
"required": ["pair_id", "verdict"],
"properties": {
"pair_id": { "type": "string", "pattern": "^p\\d{3,}$" },
"verdict": {
"type": "string",
"enum": ["duplicate", "overlapping", "independent"]
},
"reason": { "type": "string" },
"dominant": {
"description": "skill_id of the better skill, or null if the pair is genuinely interchangeable. Only meaningful for `verdict: \"duplicate\"`.",
"type": ["string", "null"]
}
}
}