testing-hashql

HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests. Use when writing tests for HashQL code, using //~ annotations, running --bless, debugging test failures, or choosing the right testing approach.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an actionable, well-structured reference catalog with executable commands, real code examples, and clean progressive disclosure to four verified bundle files. Its main weakness is that debugging workflows lack explicit validation/feedback checkpoints.

Suggestions

Add an explicit validation feedback loop for the debugging-test-failures flow (e.g., run filtered test → read //~ mismatch → fix source → re-run --bless only when intentional) to strengthen workflow clarity.

Tighten transitional prose like 'Three categories exist' and 'Categories vary: reify/, lower/, pass/ssa_repair/' to keep the reference lean.

Dimension	Reasoning	Score
Conciseness	Efficient overview with a scenario→test-type table, terse commands, and minimal prose; assumes Claude knows Rust testing basics without padding. Not a 5 because a few phrases ('Three categories exist', 'Categories vary') could be trimmed.	4 / 5
Actionability	Provides concrete executable commands ('cargo run -p hashql-compiletest run --bless', 'cargo insta accept') and complete copy-paste-ready code examples (peek unit test, body! macro, snapshot Settings) covering the common cases.	5 / 5
Workflow Clarity	The quick-reference table gives a clear scenario→approach→location mapping, but multi-step flows like 'debugging test failures' lack explicit validation checkpoints or feedback loops, so checkpoints remain mostly implicit. Not a 5 due to those gaps; not capped at 3 since this is a reference catalog rather than a destructive/batch workflow.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references (📖 markers and a References section) to four real bundle files — compiletest-guide.md, mir-builder-guide.md, testing-strategies.md, mir-fluent-builder.md — with content appropriately split for easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-targeted, clearly stating both what the skill does and when to use it with concrete trigger phrases tied to HashQL-specific tooling. Its only gap is the absence of the 'insta' synonym that users may also say.

Suggestions

Add 'insta' as a synonym alongside 'snapshot test' in the description so users searching for that crate name trigger the skill.

Consider adding 'cargo nextest' as a natural trigger term since it appears in the body's unit-test commands.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple specific concrete actions — 'compiletest (UI tests), unit tests, and snapshot tests' plus 'writing tests, using //~ annotations, running --bless, debugging test failures, choosing the right testing approach' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (testing strategies across three approaches) and 'when' via the 'Use when writing tests for HashQL code, using //~ annotations, running --bless, debugging test failures...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users say ('compiletest', 'UI test', 'snapshot test', '//~ annotations', '--bless', 'debugging test failures') but missing common synonyms like 'insta' that appear in the body. Not a 5 because a few natural variations are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear HashQL-specific niche with distinct triggers (compiletest, //~ annotations, --bless) unique to this compiler domain, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: hashintel/hash
Path: .claude/skills/testing-hashql/SKILL.md
Commit: 0144f9c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.