alonso-skills/joi
Use when building joi schemas, validating input data, defining custom types, conditional validation with .when(), cross-field references, custom error messages, or writing joi extensions. Standalone package that integrates with the @hapi ecosystem.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 skill description that clearly identifies its niche (joi validation library), lists specific concrete capabilities including advanced features like .when() and extensions, and opens with an explicit 'Use when' clause. The description is concise, uses third person voice appropriately, and provides enough detail to distinguish it from general validation or other schema library skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building joi schemas, validating input data, defining custom types, conditional validation with .when(), cross-field references, custom error messages, and writing joi extensions. | 3 / 3 |
Completeness | Explicitly starts with 'Use when...' providing clear trigger guidance for when Claude should select this skill, and the listed items serve double duty as both 'what it does' and 'when to use it'. Also includes ecosystem context (hapijs). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'joi schemas', 'validating input data', 'custom types', '.when()', 'cross-field references', 'custom error messages', 'joi extensions', 'hapijs'. These cover both common and advanced use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to the joi validation library specifically, with distinct triggers like 'joi schemas', '.when()', 'joi extensions', and 'hapijs ecosystem' that are unlikely to conflict with other validation or schema skills. | 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 a well-crafted skill that exemplifies good content design. It provides a concise quick start with executable code, clear critical rules, a logical workflow, practical common patterns, and a comprehensive reference table for deeper exploration. The content respects Claude's intelligence while providing exactly the domain-specific knowledge needed for Joi schema building.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what Joi is or how validation libraries work. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples for the quick start, conditional validation with .when(), and cross-field references with Joi.ref(). The code is copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (choose type → add constraints → compose → add conditionals → customize errors). For a schema-building skill, this is a non-destructive operation where validation checkpoints aren't critical, and the single-direction workflow is unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to 9 separate reference files. The Key Patterns table provides clear navigation to detailed materials without inlining excessive content. | 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.
Reviewed
Table of Contents