Audit existing skills with Tessl scoring, trigger-coverage checks, repo conventions, or quick experiential feedback from a recent task. Use when revising skills, triaging weak activation, or turning observed skill guidance failures into scoped repo edits.
91
90%
Does it follow best practices?
Impact
98%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Tessl run per skill
100%
100%
Score per skill reported
100%
100%
Vague names flagged
62%
87%
Missing boundaries flagged
100%
100%
Third-person descriptions proposed
100%
100%
What and when in descriptions
100%
100%
Overlap boundary in descriptions
100%
100%
Misplaced code review content flagged
100%
100%
Correct handoff skill named
88%
66%
Evidence over taste
100%
87%
Optimizer not invoked
100%
100%
Scope respected
100%
100%
Rubric moved to references
100%
100%
Examples moved to references
100%
100%
Duplicate checklist removed
100%
100%
Frontmatter cleaned
22%
100%
References linked from SKILL.md
100%
100%
Tessl run before edits
100%
100%
Tessl rerun after edits
100%
100%
Before/after scores compared
100%
100%
Change reasons documented
100%
100%
SKILL.md remains workflow-focused
100%
100%
Optimizer not used
100%
100%
Scope respected
100%
100%
Tessl run first
90%
100%
Correct single-skill command
100%
100%
Score reported
100%
100%
Tessl command reported
100%
100%
Strongest parts identified
100%
100%
Findings with file references
100%
100%
Blockers separated from polish
100%
100%
Smallest change set
100%
100%
Rerun status reported
100%
100%
Repo conventions loaded
85%
100%
Optimizer not invoked
100%
100%
Adjacent issues flagged separately
66%
88%