managing-cargo-dependencies

Cargo.toml dependency management patterns for HASH workspace. Use when adding, updating, or removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, or managing public dependencies.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Well-organized, executable reference skill with excellent progressive disclosure and concrete TOML examples. The main gap is the absence of an explicit verification step after the dependency-addition workflow.

Suggestions

Add an explicit verification step to 'Quick Add Process' (e.g., '5. Run `cargo check` / `cargo build` to confirm the workspace resolves and compiles') to satisfy the batch/destructive validation requirement.

Trim the restated intro line 'Guidance for adding and managing dependencies in Cargo.toml files within the HASH repository's workspace structure.' since it duplicates the title and description.

Consider a brief note on what to do when `cargo` reports a dependency resolution failure (a feedback loop) to lift workflow_clarity above 3.

Dimension	Reasoning	Score
Conciseness	Lean, dense reference material (DO/DON'T bullets, tight TOML blocks) that assumes Cargo/TOML knowledge; only the restated intro sentence is trimmable, placing it just above the efficient-midpoint anchor.	4 / 5
Actionability	Provides copy-paste-ready, fully executable TOML examples covering the 4-section pattern, public dependencies, and optional-dependency/feature configuration, matching the top anchor.	5 / 5
Workflow Clarity	The 'Quick Add Process' gives a clear 4-step sequence, but there is no explicit validation/verification step (e.g. cargo check/build) for these batch Cargo.toml edits, which caps this dimension per the rubric's destructive/batch guidance.	3 / 5
Progressive Disclosure	Clear overview in SKILL.md with well-signaled, one-level-deep references to three real bundle files, each annotated with a 'Use when' clause and listed in a References section, matching the top anchor.	5 / 5
	Total	17 / 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.

A specific, well-scoped description that clearly states the domain, lists concrete actions, and provides an explicit 'Use when' trigger clause. Minor room to add synonyms/file extensions but otherwise excellent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (adding/updating/removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, managing public dependencies), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (Cargo.toml dependency management patterns for HASH workspace) and 'when' (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural terms users would say (dependencies, Cargo.toml, version pinning, default features, public dependencies), but missing some synonyms and file-extension variations, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (HASH workspace Cargo.toml dependency management) with distinct triggers and minimal overlap with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 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
relative_links	Relative link issues: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: hashintel/hash
Path: .claude/skills/managing-cargo-dependencies/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.