Tessl • The management layer for AI agent skills

SkillPublic

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

87%

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

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.

The body is a well-structured overview with excellent executable examples and properly implemented one-level-deep progressive disclosure. Its weaknesses are redundant content (duplicated reference listings and examples, a redundant intro line) and the absence of a verification step in the quick-add workflow.

Suggestions

Remove the redundant opening sentence that restates the frontmatter description, and delete (or fold into '## Detailed Guides') the trailing '## References' section that re-lists the same three reference files.

Drop the 'Making a Dependency Public' example, since its serde/tokio lines already appear in the 4-section pattern example, and instead note the public=true rule inline where it is first shown.

Add a final verification step to the 'Quick Add Process' (e.g., run cargo check or cargo metadata to confirm the workspace resolves) so the workflow closes the loop on the earlier steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but has avoidable duplication: the opening line restates the frontmatter description, the trailing '## References' section re-lists the same three files already detailed under '## Detailed Guides', and the 'Making a Dependency Public' example repeats serde/tokio lines already shown in the 4-section pattern — more than the 'minor instances' of a 4.	3 / 5
Actionability	Fully executable, copy-paste-ready TOML for the common cases: the 4-section pattern, the two-step 'Adding a New External Dependency' walkthrough, public dependencies, and optional dependencies with the [features] wiring, matching the top anchor.	5 / 5
Workflow Clarity	The 'Quick Add Process' is a clear 4-step sequence with a pre-check ("Check workspace root - Is dependency already there?"), but there is no verify step after edits (e.g., cargo check), matching 'clear sequence with most checkpoints present; minor validation gaps' rather than a 5.	4 / 5
Progressive Disclosure	All three referenced files (workspace-setup.md, package-dependencies.md, examples-reference.md) exist, are one level deep, and are each introduced with a 'Use when' clause plus a content summary; the body stays a genuine overview with a quick reference, 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 strong description: it names a specific domain, enumerates concrete actions, and provides an explicit 'Use when...' clause with natural trigger phrases. The only shortfall is the absence of a few common synonyms (e.g., 'crates').

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "adding, updating, or removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, or managing public dependencies" — with comprehensive coverage of the skill's scope, matching the top anchor rather than the 'minor gaps' of a 4.	5 / 5
Completeness	"Cargo.toml dependency management patterns for HASH workspace" explicitly answers what the skill does, and "Use when adding, updating, or removing dependencies..." gives concrete trigger phrases for when to use it — both halves are explicit, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural-keyword coverage ("add/update/remove dependencies", "Cargo.toml", "version pinning", "public dependencies") but common synonyms like "crates" are absent, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Cargo.toml dependency management scoped to the HASH workspace) with distinct, specific trigger terms means minimal risk of firing for unrelated skills, matching the top anchor.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: hashintel/hash
Path: .agents/skills/managing-cargo-dependencies/SKILL.md
Revision: ab5d057

Reviewed: 7 days ago

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.

managing-cargo-dependencies

Table of Contents

Is this your skill?