Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
hashintel avatar

Exploring Rust Crates

  • 3 installs
  • 1.6k repo stars
  • Updated August 5, 2026
  • hashintel/hash

Generates and uses Rust documentation to understand crate APIs, module hierarchy, and code organization in the HASH workspace.

About

Uses cargo doc to explore a Rust crate's functions, types, traits, and structure within the HASH workspace. A developer uses it when learning an unfamiliar crate or finding APIs in the Rust codebase.

  • Generates docs for a specific package or the whole workspace
  • Focused on understanding crate API and module hierarchy

Exploring Rust Crates by the numbers

  • 3 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #98 of 121 Rust skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hashintel/hash --skill exploring-rust-crates

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs3
repo stars1.6k
Last updatedAugust 5, 2026
Repositoryhashintel/hash

What it does

Generates and uses Rust documentation to understand crate APIs, module hierarchy, and code organization in the HASH workspace.

Files

SKILL.mdMarkdownGitHub ↗

Exploring Rust Crates

Generate and use Rust documentation to understand crate APIs, structure, and code organization in the HASH workspace.

Generating Documentation

For a Specific Package

cargo doc --no-deps --all-features --package <package-name>

For the Entire Workspace

cargo doc --no-deps --all-features --workspace

Key Flags

  • --no-deps: Document local code only (faster, less noise)
  • --all-features: Include all feature-gated APIs
  • --package <name>: Target a specific crate
  • --workspace: Document all crates in the workspace
  • --document-private-items: Include internal implementation details

What Generated Docs Provide

1. Crate organization - Module hierarchy and component relationships 2. Public API surface - All public functions, types, traits, and constants 3. Usage examples - Code examples from doctest blocks 4. Error documentation - Documented error conditions and handling 5. Type relationships - Trait implementations, type aliases, associated types

Viewing Documentation

Docs are generated at:

target/doc/<crate_name>/index.html

Tips

  • Generate docs before diving into unfamiliar Rust code
  • Cross-reference # Errors sections for error handling patterns
  • Look for # Examples sections for idiomatic usage patterns

Related skills

Rustbackenddocs

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.