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

72%

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

A well-organized, actionable skill body with concrete executable TOML examples and a clean one-level-deep reference structure. Its main gaps are a missing verification step in the dependency workflow and some redundant reference/code repetition that could be tightened.

Suggestions

Add an explicit validation step to the Quick Add Process (e.g., a final "Verify: run `cargo check` and confirm the dependency resolves") so the workflow has a real checkpoint.

Remove the standalone References list that duplicates the three files already shown in Detailed Guides, or merge them, to tighten conciseness.

Consolidate overlapping code (e.g., the 4-section Quick Reference example and the "Adding a New External Dependency"/"Making a Dependency Public" snippets) to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no over-explanation of Cargo basics, but the three reference files are listed twice (Detailed Guides and again in a bare References section) and some code examples overlap, so it could be tightened rather than earning the score-3 "every token earns its place" bar.	2 / 3
Actionability	Provides complete, copy-paste-ready TOML snippets (4-section pattern, adding a dependency, making one public, optional deps) plus a concrete Quick Add procedure, matching the score-3 fully-executable anchor rather than the pseudocode of score 2.	3 / 3
Workflow Clarity	The Quick Add Process is a clear 4-step sequence but lacks any validation/verification checkpoint (e.g., run cargo check), and workspace-wide dependency edits carry build-break risk, so per the rubric it caps at score 2 rather than the explicit-feedback-loop level.	2 / 3
Progressive Disclosure	Clear overview with well-signaled one-level-deep references — each guide has a "Use when:" cue and content bullets, all three referenced files verified to exist, with no nested reference chains — matching the score-3 anchor.	3 / 3
	Total	10 / 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.

A strong, well-scoped description that concretely lists capabilities, includes natural trigger terms, and provides an explicit Use-when clause tied to a specific Rust workspace context. No over-claims or fluff, and it uses the accepted "Use when" trigger form rather than first/second person.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "adding, updating, or removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, or managing public dependencies" — matching the score-3 anchor rather than the partial domain-only coverage of score 2.	3 / 3
Completeness	Explicitly states what it does ("Cargo.toml dependency management patterns for HASH workspace") and when to use it via an explicit "Use when..." clause, satisfying both halves required for score 3.	3 / 3
Trigger Term Quality	Includes natural terms a Rust/Cargo user would actually say ("Cargo.toml", "dependency/dependencies", "version pinning", "default features", "public dependencies"), giving good coverage rather than the partial set at score 2.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to "HASH workspace" and "Cargo.toml" dependency management, a clear niche unlikely to trigger for unrelated skills; not the generic overlap seen at score 2.	3 / 3
	Total	12 / 12 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: 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.