CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-hashql-diagnostics

HashQL diagnostic writing patterns using hashql-diagnostics crate. Use when creating error messages, warnings, Labels, Messages, Severity levels, Patches, Suggestions, or improving diagnostic quality in HashQL code.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is exemplary for a patterns skill: tight, actionable, well-organized, and properly offloading depth to a single real bundle file. There is little to improve beyond optional polish.

DimensionReasoningScore

Conciseness

The body is lean: it jumps straight into DO/DON'T rules, code, and a severity table without explaining what diagnostics are or how Rust works, so every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready Rust examples (Diagnostic::new, Label::new, add_message, Suggestions::patch, Patch::new) plus good/bad message pairs and a when-to-use severity table — concrete and executable.

3 / 3

Workflow Clarity

This is a single-purpose patterns skill where the create-then-annotate-diagnostic flow is unambiguous across the examples; no destructive or batch operation requires a validation checkpoint.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with a clearly signaled one-level-deep reference to references/guidelines.md (verified to exist), each annotated with its contents, keeping navigation shallow and discoverable.

3 / 3

Total

12

/

12

Passed

Description

85%

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

A strong description: it states concrete capabilities, gives an explicit 'Use when' trigger, and carves out a distinct HashQL-diagnostic niche. It would score higher on trigger terms by leading with natural phrasing instead of capitalized crate types.

Suggestions

Lead the trigger clause with natural user phrasing (e.g. 'Use when writing or improving HashQL diagnostics, error messages, or warnings') before naming the crate types.

Soften capitalized API names (Label, Message, Severity, Patch, Suggestions) in the description so they read as tasks rather than type identifiers.

DimensionReasoningScore

Specificity

Lists multiple concrete items a user works with — 'error messages, warnings, Labels, Messages, Severity levels, Patches, Suggestions' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

States what it does ('HashQL diagnostic writing patterns using hashql-diagnostics crate') and explicitly when to use it via an explicit 'Use when ...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

It includes natural terms ('error messages', 'warnings', 'improving diagnostic quality') but leans heavily on capitalized crate type names (Label, Message, Severity, Patch) that read as API jargon rather than words users naturally say.

2 / 3

Distinctiveness Conflict Risk

The HashQL-specific crate niche and diagnostic-only scope give it a clear, distinct trigger set unlikely to overlap with other skills.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository
hashintel/hash
Reviewed

Table of Contents

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.