CtrlK
BlogDocsLog inGet started
Tessl Logo

alonso-skills/hapi

Creates, configures, and debugs `@hapi/hapi` servers — implements routes, plugins, auth schemes, validation, caching, and request lifecycle hooks. Use when building HTTP APIs, setting up stale-while-revalidate caching, registering server methods, configuring views, managing startup sequences, or troubleshooting response marshalling.

76

Quality

95%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

87%

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 efficiently covers the Hapi framework's key concepts with executable code examples and excellent progressive disclosure through a comprehensive reference table. The main weakness is the workflow section, which could benefit from more explicit validation/error recovery steps. Overall, it's a strong skill that respects token budget while providing actionable, well-organized guidance.

Suggestions

Add a brief feedback loop to the workflow (e.g., 'If server.inject() returns unexpected auth errors, check scheme → strategy → default chain before proceeding')

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude knows what Hapi, Joi, and related concepts are. Every section provides only what's needed — code patterns, critical rules, and references. No unnecessary explanations of basic concepts.

3 / 3

Actionability

Provides executable code examples for the quick start, auth three-layer pattern, scheme authenticate return, and route validation. These are copy-paste ready patterns covering the most critical operations.

3 / 3

Workflow Clarity

The workflow section provides a clear 6-step sequence for building a Hapi server, and step 4 includes a verification checkpoint (test auth with server.inject before defining protected routes). However, there are no explicit feedback loops for error recovery, and validation checkpoints beyond auth testing are missing.

2 / 3

Progressive Disclosure

Excellent progressive disclosure structure: a concise overview with quick start and critical patterns inline, then a comprehensive reference table with well-organized one-level-deep links to detailed reference files. Navigation is clear and topics are logically grouped.

3 / 3

Total

11

/

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 an excellent skill description that clearly identifies the specific framework (@hapi/hapi), lists concrete capabilities, and provides an explicit 'Use when' clause with diverse trigger scenarios. It uses proper third-person voice throughout and balances framework-specific terminology with general concepts like 'HTTP APIs' to ensure discoverability. The description is concise yet comprehensive, making it easy for Claude to select this skill precisely when needed.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: creates/configures/debugs servers, implements routes, plugins, auth schemes, validation, caching, and request lifecycle hooks. Very detailed and actionable.

3 / 3

Completeness

Clearly answers both 'what' (creates, configures, debugs hapi servers with routes, plugins, auth, validation, caching, lifecycle hooks) and 'when' (explicit 'Use when' clause listing building HTTP APIs, setting up caching, registering server methods, configuring views, managing startup, troubleshooting).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: '@hapi/hapi', 'HTTP APIs', 'routes', 'plugins', 'auth schemes', 'validation', 'caching', 'stale-while-revalidate', 'server methods', 'views', 'startup sequences', 'response marshalling'. Good coverage of both framework-specific and general terms.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific framework reference '@hapi/hapi' and framework-specific terminology like 'request lifecycle hooks', 'server methods', 'response marshalling', and 'stale-while-revalidate caching'. Unlikely to conflict with generic HTTP or Express 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