CtrlK
BlogDocsLog inGet started
Tessl Logo

rust-tracing-practices

HASH tracing and instrumentation practices for Rust. Use when adding spans, events, or #[tracing::instrument] to Rust code.

68

Quality

83%

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

78%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.

A compact, actionable reference covering event recording and instrumentation with concrete code examples and non-obvious error_stack guidance. Minor stubs and the absence of an explicit workflow sequence keep actionability and workflow_clarity just below full marks.

DimensionReasoningScore

Conciseness

Lean bullets and two tight code blocks with mostly earned tokens; the error_stack Display/Debug note is non-obvious domain knowledge, though a couple of explanatory sentences could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready macro calls with specific formatter and field guidance, but the #[tracing::instrument] example is a stub with '// Implementation' rather than a fully runnable function.

4 / 5

Workflow Clarity

Organized into two clear, unambiguous sections (Event Recording, Instrumentation); no destructive or batch workflow exists so the validation cap does not apply, but there is no explicit process sequence.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized section headers, meeting the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A focused, well-structured description that clearly states both capability and explicit trigger conditions for the Rust tracing domain. Minor gaps in action coverage and synonym terms prevent a perfect specificity/trigger score.

DimensionReasoningScore

Specificity

Names the Rust tracing domain and several concrete actions ('spans, events, or #[tracing::instrument]'), but coverage omits related actions like log-level selection and structured fields, keeping it just below comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' ('tracing and instrumentation practices for Rust') and 'when' with concrete trigger phrases ('Use when adding spans, events, or #[tracing::instrument] to Rust code').

5 / 5

Trigger Term Quality

Includes natural terms users would say ('tracing', 'instrument', 'spans', 'events', 'Rust'), but misses common synonyms such as 'logging' or 'log'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Rust tracing/instrumentation) with specific, distinctive triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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
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.