Skip to content
TrustedSkillsbeta
Back to all skills

Wycheproof

Checked
trailofbits·vlatest·backend·CC-BY-SA-4.0

Wycheproof analyzes code for potential vulnerabilities like race conditions and deadlocks, safeguarding your applications from unexpected behavior.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add trailofbits/skills --skill wycheproof -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

trailofbits

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned trailofbits/skills at 82fe822625.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
82fe822625
Manifest
plugins/testing-handbook-skills/skills/wycheproof/SKILL.md
Scanned
2 files, 515 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The wycheproof skill provides a mechanism to verify that code adheres to established style guides and best practices. It can analyze Rust code, identifying deviations from the official Rust style guide and suggesting corrections. This helps maintain consistent coding standards across projects and improve overall code quality.

When to use it

  • Enforcing Style Guides: Integrate wycheproof into your CI/CD pipeline to automatically check for style violations before merging code changes.
  • Code Reviews: Use the skill's output during code reviews to quickly identify and address stylistic issues, saving time and ensuring consistency.
  • Learning Rust Best Practices: Newcomers to Rust can use wycheproof as a learning tool to understand and adopt idiomatic Rust coding patterns.
  • Large Codebases: Maintainability of large projects benefits from consistent formatting enforced by the skill.

Key capabilities

  • Rust code style checking
  • Adherence to official Rust style guide
  • Identification of stylistic deviations
  • Suggestions for corrections

Example prompts

  • "Check this Rust file for style violations: src/main.rs"
  • "Analyze the following code snippet and suggest improvements based on the Rust style guide: [code snippet]"
  • "Run wycheproof on my entire project."

Tips & gotchas

  • Requires a working Rust development environment to be effective. The skill will likely need access to rustc or cargo.