Agent skill

Managing Cargo Dependencies

Cargo.toml dependency management patterns for HASH workspace.

AGPL-3.0Auto-check passedDevelopment

Install Managing Cargo Dependencies

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .claude/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .claude/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .agents/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .agents/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .cursor/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .cursor/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hashintel/hash.git --path .agents/skills/managing-cargo-dependencies

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .gemini/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .gemini/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .github/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .github/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashintel/hash --skill managing-cargo-dependencies -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hashintel/hash managing-cargo-dependencies --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/managing-cargo-dependencies .opencode/skills/managing-cargo-dependencies && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "managing-cargo-dependencies" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/managing-cargo-dependencies into .opencode/skills/managing-cargo-dependencies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-cargo-dependencies", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: managing-cargo-dependencies
GitHub stars: 1.7k
Token cost: ~1.2k tokens
SKILL.md length: 309 words
Files: 4 (incl. references)
Skills in repo: 17
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Cargo.toml dependency management patterns for HASH workspace.

Works in 4 steps: Check workspace root - Is dependency… → Add to workspace if needed - With caret… → Determine section - Public… → …
Removing dependencies
SKILL.md covers Core Principles, Quick Reference, Detailed Guides and Common Patterns, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Managing Cargo Dependencies is an agent skill from hashintel/hash. 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/examples-reference.md`, `references/package-dependencies.md` and `references/workspace-setup.md`).

It sits in Development, covering Dependency management. It works with Rust. The repository describes itself as: 🚀 The open-source, multi-tenant platform for self-building knowledge graphs and simulation. The licence is AGPL-3.0.

When your agent uses it

Removing dependencies
Organizing Cargo.toml sections
Configuring version pinning and default features
Managing public dependencies

Example prompts

“/managing-cargo-dependencies”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Check workspace root - Is dependency already there?
Add to workspace if needed - With caret version 1.2.3
Determine section - Public workspace/third-party or private?
Add to package - Use workspace = true (+ public = true if needed)

What it can do on your machine

Read from SKILL.md and the folder at commit 1fa0c7b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are toml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Cargo Dependencies loads about 1.2k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 309 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashintel/hash at commit 1fa0c7b, republished under its AGPL-3.0 licence (© hashintel). 309 words, ~1,211 tokens.

Download SKILL.mdSave it as .claude/skills/managing-cargo-dependencies/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: managing-cargo-dependencies
description: 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.
license: AGPL-3.0

Cargo Dependencies Management

Guidance for adding and managing dependencies in Cargo.toml files within the HASH repository's workspace structure.

Core Principles

HASH uses a strict workspace dependency pattern:

✅ DO:

Add external dependencies to workspace root [workspace.dependencies]
Use caret version specifiers (e.g., version = "1.0.0" = ^1.0.0)
Set default-features = false for all dependencies unless specifically needed
Use workspace = true in package Cargo.toml
Organize dependencies into 4 sections with comment headers
Use public = true for dependencies exposed in public API
Align dependency names using spaces for readability

❌ DON'T:

Add version numbers directly in package Cargo.toml
Use exact versions with = prefix (e.g., =1.0.0) in workspace root
Enable default-features without considering impact
Mix different dependency types without section comments
Forget public = true for dependencies exposed in public API

Quick Reference

The 4-Section Pattern

Every package Cargo.toml must organize dependencies into these sections:

toml

[dependencies]
# Public workspace dependencies
hash-graph-types = { workspace = true, public = true }
hashql-core      = { workspace = true, public = true }

# Public third-party dependencies
serde     = { workspace = true, public = true, features = ["derive"] }
tokio     = { workspace = true, public = true }

# Private workspace dependencies
error-stack = { workspace = true }
hash-codec  = { workspace = true }

# Private third-party dependencies
tracing     = { workspace = true }
regex       = { workspace = true }

Keep all 4 section comments even if a section is empty.

Quick Add Process

Check workspace root - Is dependency already there?
Add to workspace if needed - With caret version 1.2.3
Determine section - Public workspace/third-party or private?
Add to package - Use workspace = true (+ public = true if needed)

Detailed Guides

Choose the guide that matches the task:

workspace-setup.md

Use when: Adding new dependencies to workspace root

How to add external crates to workspace
Version pinning with exact versions
Default features configuration
Workspace member paths

package-dependencies.md

Use when: Adding dependencies to a package Cargo.toml

The 4-section organizational structure
Public vs private dependencies
When to use public = true
Alignment and formatting rules
Feature configuration

examples-reference.md

Use when: Looking for real examples from HASH codebase

Complete examples from @local/codec
Complete examples from @local/hashql/core
Optional dependencies pattern
dev-dependencies structure

Common Patterns

Adding a New External Dependency

toml

# 1. Add to workspace root Cargo.toml
[workspace.dependencies]
my-crate = { version = "1.2.3", default-features = false }

# 2. Add to package Cargo.toml (appropriate section)
[dependencies]
# Private third-party dependencies
my-crate = { workspace = true }

Making a Dependency Public

toml

# Use when the dependency appears in your public API
serde = { workspace = true, public = true, features = ["derive"] }
tokio = { workspace = true, public = true }

Optional Dependencies

toml

[dependencies]
serde = { workspace = true, optional = true, features = ["derive"] }

[features]
serde = ["dep:serde", "other-dep/serde"]

References

workspace-setup.md - Workspace root configuration
package-dependencies.md - Package dependency structure
examples-reference.md - Real codebase examples
Workspace Cargo.toml - Root workspace configuration
hash-codec/Cargo.toml - Reference example
hashql-core/Cargo.toml - Reference example

Files

SKILL.md and 3 other files (references) in .agents/skills/managing-cargo-dependencies of hashintel/hash.

SKILL.md
references/examples-reference.md
references/package-dependencies.md
references/workspace-setup.md

Open the folder on GitHubat commit 1fa0c7b

Compare with similar skills

Managing Cargo Dependencies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing Cargo Dependencies compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Managing Cargo Dependencies this skillhashintel/hash	1.7k	—	~1.2k	Automated safety check: Pass	AGPL-3.0	today
Pnpm Engineteambit/bit	18k	—	~1.9k	Automated safety check: Pass	Custom licence	today
Dependency UpdaterAsvarox/allkaraoke	261	4 repos	~3.5k	Automated safety check: Pass	MIT	today
Uv Package ManagerYikai-Liao/symusic	189	16 repos	~4k	Automated safety check: Notes	MIT	1 mo ago
Next Python Stdlib Upgrade PickerRustPython/RustPython	22k	—	~257	Automated safety check: Pass	MIT	today
BazelMoosync/Moosync	259	—	~722	Automated safety check: Pass	GPL-3.0	6 days ago

Similar skills

Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Dependency Updater
Asvarox/allkaraoke
Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.
261 GitHub starsUsed in 4 repos~3.5k tokens
DevelopmentAuto-check passed
Uv Package Manager
Yikai-Liao/symusic
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows.
189 GitHub starsUsed in 16 repos~4k tokens
DevelopmentAuto-check: notes
Next Python Stdlib Upgrade Picker
RustPython/RustPython
Picks the next CPython standard library module ready for a RustPython upgrade, skipping modules that already have an open upgrade pull request.
22k GitHub stars~257 tokensUpdated today
DevelopmentAuto-check passed
Bazel
Moosync/Moosync
Hermetic Bazel build, test, and packaging commands for the Moosync project.
259 GitHub stars~722 tokensUpdated 6 days ago
DevelopmentAuto-check passed
Dep Auditor
laolaoshiren/claude-code-skills-zh
审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实；当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock，或生成不改依赖的中文审计报告时使用
878 GitHub stars~895 tokensUpdated 3 days ago
DevelopmentAuto-check passed

Questions about Managing Cargo Dependencies

What does Managing Cargo Dependencies do?

Cargo.toml dependency management patterns for HASH workspace. Managing Cargo Dependencies is an agent skill from hashintel/hash.toml dependency management patterns for HASH workspace.

When should I use Managing Cargo Dependencies?

Managing Cargo Dependencies fits situations like: removing dependencies; organizing Cargo.toml sections; configuring version pinning and default features; managing public dependencies.

How do I install Managing Cargo Dependencies in Claude Code?

Run `npx skills add hashintel/hash --skill managing-cargo-dependencies -a claude-code`. Or copy the skill folder (.agents/skills/managing-cargo-dependencies in hashintel/hash) into .claude/skills/managing-cargo-dependencies in your project. Claude Code loads it when a task matches its description.

How do I install Managing Cargo Dependencies in Codex?

Run `npx skills add hashintel/hash --skill managing-cargo-dependencies -a codex`. Or copy the skill folder (.agents/skills/managing-cargo-dependencies in hashintel/hash) into .agents/skills/managing-cargo-dependencies in your project. Codex loads it when a task matches its description.

Can I use Managing Cargo Dependencies in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashintel/hash --skill managing-cargo-dependencies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-cargo-dependencies, .gemini/skills/managing-cargo-dependencies, .github/skills/managing-cargo-dependencies and .opencode/skills/managing-cargo-dependencies in your project.

What does Managing Cargo Dependencies need to run?

SKILL.md names no scripts, command-line tools or credentials: Managing Cargo Dependencies is instructions for the agent only.

Does Managing Cargo Dependencies access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Managing Cargo Dependencies safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managing Cargo Dependencies use?

Managing Cargo Dependencies is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing Cargo Dependencies use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.

What are the alternatives to Managing Cargo Dependencies?

Skills that share tags, products or a category with Managing Cargo Dependencies: Pnpm Engine (teambit/bit, 18k stars), Dependency Updater (Asvarox/allkaraoke, 261 stars), Uv Package Manager (Yikai-Liao/symusic, 189 stars) and Next Python Stdlib Upgrade Picker (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Cargo Dependencies?

hashintel (a GitHub organization) maintains it in hashintel/hash, which has 1,668 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashintel/hash on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Managing Cargo Dependencies

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Cargo Dependencies Management

Core Principles

Quick Reference

The 4-Section Pattern

Quick Add Process

Detailed Guides

Common Patterns

Adding a New External Dependency

Making a Dependency Public

Optional Dependencies

References

Files

Compare with similar skills

Similar skills

More from hashintel/hash

Related

Questions about Managing Cargo Dependencies