Skip to content
TrustedSkillsbeta
Back to all skills

Fp Check

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

Checks floating-point numbers for common errors like NaN, infinity, or rounding issues – vital for numerical stability and debugging.

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 fp-check -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/fp-check/skills/fp-check/SKILL.md
Scanned
8 files, 693 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 fp-check skill performs functional property checks on Rust code. It analyzes your codebase to verify that functions behave as expected, ensuring correctness and preventing regressions. This skill helps identify potential bugs early in the development cycle by automatically testing function behavior against defined properties.

When to use it

  • Rust project maintenance: Regularly check existing Rust projects for functional property violations.
  • New feature development: Ensure new features adhere to expected behavior and don't introduce regressions.
  • Refactoring code: Verify that refactored code maintains its original functionality.
  • Automated testing pipelines: Integrate fp-check into CI/CD workflows for continuous verification of functional properties.

Key capabilities

  • Functional property checking for Rust code
  • Automatic test generation based on function signatures
  • Regression prevention through automated checks

Example prompts

  • "Run fp-check on my project's src/lib.rs file."
  • “Check the calculate_average function in data_processing.rs for functional property violations.”
  • "Generate tests for all functions in the utilities module."

Tips & gotchas

  • Requires a Rust development environment and familiarity with Rust code structure.
  • The effectiveness of fp-check depends on well-defined function signatures and clear expectations of behavior.