CtrlK
BlogDocsLog inGet started
Tessl Logo

alonso-skills/hurl

Write and run HTTP API tests in Hurl's plain-text format — requests, assertions, captures, CI reports, and executable API documentation

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 an exceptionally well-crafted skill file. It packs dense, non-obvious domain knowledge (typed predicates, redirect semantics, secret redaction limitations, version-specific breaking changes) into a lean format with executable examples. The constraints section captures critical gotchas that would otherwise cause subtle bugs, the workflow provides a clear incremental development path, and the references are cleanly organized for progressive disclosure.

DimensionReasoningScore

Conciseness

Every section earns its place. The content is dense with non-obvious information (typed predicates, redirect behavior, secret redaction caveats, 8.0 breaking changes) that Claude wouldn't inherently know. No padding or explanation of basic concepts.

3 / 3

Actionability

Provides fully executable Hurl file examples, concrete CLI invocations with flags, and copy-paste-ready patterns for login flows, async polling, CI integration, and curl conversion. Debugging guidance is specific (--very-verbose --to-entry N, --curl).

3 / 3

Workflow Clarity

The workflow section provides a clear 7-step incremental build process (smoke → asserts → chain → async → parameterize → suite → CI) with explicit verification at each step. Debugging/failure recovery is addressed with specific commands. The 'verify as you go' approach and retry-based polling pattern serve as validation checkpoints.

3 / 3

Progressive Disclosure

The SKILL.md serves as a well-structured overview with constraints, workflow, and examples, then cleanly references 6 detailed files (file-format, asserting, captures-and-filters, CLI, testing-workflows, recipes) with clear one-line descriptions. References are one level deep and well-signaled.

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 an excellent skill description that clearly defines the tool (Hurl), lists specific capabilities, and provides comprehensive trigger guidance with both 'Use when' and 'Trigger on' clauses. It uses proper third-person voice, includes natural user terms alongside tool-specific identifiers, and carves out a distinct niche that minimizes conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: writing HTTP API tests, chaining requests with captured values, polling async APIs, converting curl commands, producing executable API documentation. Very detailed and actionable.

3 / 3

Completeness

Clearly answers both 'what' (write and run HTTP API tests in Hurl format) and 'when' with explicit 'Use when...' and 'Trigger on...' clauses covering multiple scenarios and file/tool triggers.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: '.hurl files', 'hurl', 'hurlfmt CLI', 'REST/GraphQL APIs', 'curl commands', 'jsonpath/xpath', 'test an API', 'HTTP endpoints', 'smoke tests', 'integration tests'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — specifically targets Hurl's plain-text format, .hurl files, and the hurl/hurlfmt CLI. Unlikely to conflict with generic API testing or curl skills due to the specific tool focus.

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