paker-it/aie26-skill-judge
Evaluates SKILL.md submissions for the AI Engineer London 2026 Skills Contest across 11 dimensions (8 official Tessl rubric + 3 bonus). Use when you say 'judge my AIE26 contest skill', 'score this SKILL.md for the contest', 'review my skill submission', or 'how would this score on the leaderboard'. Accepts GitHub repo URLs, file paths, or raw pastes.
82
94%
Does it follow best practices?
Impact
65%
1.80xAverage score across 5 eval scenarios
Risky
Do not use without reviewing
example-evaluation.mdreferences/
Example Evaluation: devcon-hack-coach
This is a worked example of a completed evaluation. Use it to calibrate your expectations for the output format and scoring depth.
Scorecard: devcon-hack-coach
Core Score: 100/100
| Dimension | Score | Reasoning |
|---|---|---|
| Specificity | 3/3 | Names exact deliverables: one-page spec, 4-checkpoint plan, 3-sentence pitch |
| Trigger Terms | 3/3 | Six natural phrases including "coach me through a DevCon hack", "scope my 24h hack" |
| Completeness | 3/3 | Purpose (hackathon coaching) and activation context (DevCon 2026 prep) both crystal clear |
| Distinctiveness | 3/3 | Scoped to a single event + format; zero conflict risk with general coaching skills |
| Conciseness | 3/3 | Every section earns its place. Anti-patterns list is tight. No filler. |
| Actionability | 3/3 | Exact questions to ask, exact exit gates, example dialogue for each phase |
| Workflow Clarity | 3/3 | 4 named phases with explicit exit gates and loop-back conditions ("loop inside the phase") |
| Progressive Disclosure | 3/3 | 5 reference files loaded only when their phase starts; main file stays lean |
Bonus Score: +8/9
| Dimension | Score | Reasoning |
|---|---|---|
| Innovation | 3/3 | Opinionated "no code before spec" stance is a novel coaching angle for hackathons |
| Style | 3/3 | Pushy coach voice with specific example dialogue — distinctive and consistent |
| Vibes | 2/3 | Compelling hook and real utility, but narrow event window limits install appeal |
Verdict
Competition-ready. The 4-phase workflow with strict exit gates is the strongest element — it turns vague coaching into a repeatable process. The only soft spot is vibes: the skill is tied to a single event (DevCon June 2026), which limits its shelf life. A contestant might generalize the concept to "hackathon coach" for broader appeal, but for this contest the event specificity is actually a strength for distinctiveness.
docs
superpowers
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
references