CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

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 balances conciseness with actionability. It provides executable code examples for the most common Joi patterns, establishes clear critical rules, and uses progressive disclosure effectively with a reference table pointing to detailed documentation. The only minor note is that bundle files weren't provided to verify the referenced paths exist, but the structure itself is exemplary.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude knows what Joi is and jumps straight into executable examples and actionable rules. No unnecessary explanations of basic concepts. Every section earns its place.

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 like password confirmation and date range validation.

3 / 3

Workflow Clarity

The workflow section provides a clear 5-step sequence for building Joi schemas. Since Joi schema building is not a destructive or batch operation, explicit validation checkpoints aren't required. The critical rules section adds important guardrails (immutability, validate at boundaries).

3 / 3

Progressive Disclosure

Excellent structure with a concise overview, then well-signaled one-level-deep references to 9 separate reference files organized in a clear table. The main SKILL.md stays focused on quick start and common patterns while pointing to detailed docs for each topic.

3 / 3

Total

12

/

12

Passed

Description

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 the joi validation library domain, lists specific concrete capabilities, and opens with an explicit 'Use when...' clause providing clear trigger guidance. The description is concise, uses third person voice appropriately, and includes both common and advanced use cases that would help Claude distinguish this skill from other validation-related skills.

DimensionReasoningScore

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 answers both what (building joi schemas, validating input, defining custom types, etc.) and when (starts with 'Use when...') with clear trigger conditions. The 'Use when' clause is present and comprehensive.

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 specific use cases a developer would mention.

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 generic validation or other schema library skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents