Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashintel/exploring-rust-crates
Generate Rust documentation to understand crate APIs, structure, and usage.
Passed 23 of 23 test cases with the skill, and 22 of 23 without it.
1 fixed22 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I'm trying to explore the public API of the `hash-engine` crate in our repository. What command should I run to build local Rust documentation specifically for this package without building docs for external third-party dependencies, and where will the HTML output be located?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends a command containing --no-deps. | Passed | Passed |
| Recommends a command containing --all-features. | Missed | Passed |
| Specifies target/doc/hash_engine/index.html as the HTML output location. | Passed | Passed |
The instructions your model reads when the skill loads.
Generate and use Rust documentation to understand crate APIs, structure, and code organization in the HASH workspace.
cargo doc --no-deps --all-features --package <package-name>
cargo doc --no-deps --all-features --workspace
--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 detailsDocs are generated at:
target/doc/<crate_name>/index.html
test cases passed, vs 22 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.