Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashintel/rust-coding-style
HASH Rust coding style.
Passed 26 of 26 test cases with the skill, and 17 of 26 without it.
and 13 more in the full report
9 fixed17 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a function `process_items` that reads elements from a vector of numbers, and another function `clear_items` that modifies the vector elements without changing its size. What argument types should I use for the inputs?
| Checked | Without skill | With skill |
|---|---|---|
| Uses &[T] instead of &Vec<T> for immutable reading. | Missed | Passed |
| Uses &mut [T] instead of &mut Vec<T> for mutable element modifications without resizing. | Missed | Passed |
The instructions your model reads when the skill loads.
derive_more over manual trait implementations#[cfg(feature = "...")] patterncargo clippy with --all-features, --all-targets, and --no-deps from the rootcargo doc --no-deps --all-features for checking documentationrustfmt to format the code#[expect(lint, reason = "...")] over #[allow(lint)]pub)#[derive(Debug, Copy, Clone, Eq, Hash, PartialEq, derive_more::Display)]
pub struct UserId(Uuid);
impl Future<Output = T> + Send in trait definitions:fn get_data(
&self,
id: String,
) -> impl Future<Output = Result<Data, Report<DataError>>> + Send {
async move {
// Implementation
}
}
test cases passed, vs 17 / 26 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.