devcon-hack-coach
Coaches you through scoping, shipping, and pitching a 24-hour hackathon project at AI Native DevCon (Tessl, London, 1–2 June 2026). Spec-first, track-aware, demo-obsessed. Use when you say "coach me through a DevCon hack", "pressure-test my hackathon idea", "what should I build at AI Native DevCon", "scope my 24h hack", "will I finish this in time", or "draft my demo pitch". Refuses to let you write code before a one-page spec exists.
98
100%
Does it follow best practices?
Impact
96%
1.62xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly defines a narrow niche (hackathon coaching for a specific event), lists concrete actions, and provides explicit trigger phrases. The only minor issue is the use of second person ('Coaches you', 'Refuses to let you'), which per the rubric guidelines should be penalized, but the overall quality of specificity, triggers, and completeness is excellent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: scoping, shipping, pitching a hackathon project, pressure-testing ideas, drafting demo pitches, enforcing spec-first workflow. The phrase 'Refuses to let you write code before a one-page spec exists' is a distinctive behavioral detail. | 3 / 3 |
Completeness | Clearly answers both 'what' (coaches through scoping, shipping, pitching a 24-hour hackathon project) and 'when' (explicit 'Use when...' clause with six specific trigger phrases). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger phrases users would actually say: 'coach me through a DevCon hack', 'pressure-test my hackathon idea', 'scope my 24h hack', 'will I finish this in time', 'draft my demo pitch'. These cover multiple natural variations of how someone would invoke this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche: specific to a named event (AI Native DevCon, Tessl, London, 1–2 June 2026), a specific format (24-hour hackathon), and a specific methodology (spec-first, track-aware, demo-obsessed). Very unlikely to conflict with any other skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill. It combines a clear 4-phase workflow with strict exit gates, concrete pushback language that defines the coaching voice, and disciplined progressive disclosure of reference materials. The anti-patterns section is particularly strong — it preemptively blocks common failure modes with specific, actionable refusals rather than vague warnings.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The voice examples double as behavioral constraints, the anti-patterns list is tight and specific, and there's no explanation of concepts Claude already knows. The skill is ~150 lines but dense with actionable content — nothing could be cut without losing information. | 3 / 3 |
Actionability | Extremely concrete throughout: specific questions to ask in order, exact checkpoint hours with named deliverables, word-count constraints on pitch sentences, explicit stage-direction format for demo moments, and verbatim pushback phrases. Every instruction tells Claude exactly what to do or say. | 3 / 3 |
Workflow Clarity | Four phases are clearly sequenced with explicit exit gates that prevent skipping ahead. Each phase has a named goal, concrete steps, and a loop-back condition if the gate isn't met (e.g., 'go back to Phase 2 and cut'). The checkpoint table in Phase 3 adds a validation layer, and the anti-patterns section acts as a guardrail checklist. | 3 / 3 |
Progressive Disclosure | Explicitly instructs to load references only when their phase starts. References are one level deep, clearly mapped to phases, and include both templates and worked examples. The main file is a complete overview that stands alone while pointing to five supporting files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mertpaker/devcon-hack-coach
- Commit
0bd801f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.