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

94%

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

88%

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

The body is lean, highly actionable, and well-structured with a quick-reference table and concrete executable examples, backed by real one-level reference files. The only gap is the absence of explicit validation/checkpoint guidance around the destructive --bless flow.

Suggestions

Add a short validation checkpoint around --bless: e.g., run the suite first, review the diff before blessing, and re-run without --bless to confirm, since --bless silently overwrites expected outputs.

Clarify the insta review/accept workflow with an explicit feedback loop (run → cargo insta review → accept only the intended snapshots) to prevent accidentally blessing unintended changes.

Note when to prefer the fluent builder reference over the body! macro reference so the two MIR references are clearly distinguished rather than both listed as 'for advanced cases'.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: a quick-reference table, terse command blocks, and minimal prose; it avoids explaining what compiletest/insta is and assumes competence, with every token earning its place.	3 / 3
Actionability	Provides fully executable cargo commands, copy-paste-ready test file examples (jsonc with //@ and //~ annotations), real Rust unit-test snippets, and concrete insta settings code — all specific and runnable.	3 / 3
Workflow Clarity	The Quick Reference table gives a clear scenario-to-test-type mapping, but there are no explicit validation/checkpoint steps for the risky --bless operation (which mutates expected outputs) beyond a bare command, capping it per the 'missing validation in destructive/batch operations' rule.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview with four well-signaled one-level-deep references (compiletest-guide, testing-strategies, mir-builder-guide, mir-fluent-builder), all verified to exist as real files, with clear per-section navigation links.	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.

The description is specific, action-oriented, and includes a strong explicit 'Use when' trigger clause with natural domain keywords. It clearly communicates both what the skill does and when to use it within a distinct HashQL niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'compiletest (UI tests), unit tests, and snapshot tests' and the trigger clause enumerates 'writing tests... using //~ annotations, running --bless, debugging test failures, or choosing the right testing approach', matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (the three testing strategies) and when via a clear 'Use when writing tests for HashQL code, using //~ annotations, running --bless, debugging test failures, or choosing the right testing approach' clause, matching the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered ('compiletest', 'ui test', 'snapshot test', 'insta test', '//~ annotation', '--bless'), which are exactly what a HashQL developer would say; not generic jargon.	3 / 3
Distinctiveness Conflict Risk	The HashQL-specific domain (compiletest, //~ annotations, --bless, MIR/HIR) carves a clear niche unlikely to conflict with other skills; not a score below because it is neither generic nor overlapping.	3 / 3
	Total	12 / 12 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: 4f2d2ce

Reviewed: about 5 hours 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.