Skip to content
TrustedSkillsbeta
Back to all skills

Validate Binaries

Checked
peteonrails·vlatest·devops·MIT

Verifies binary file integrity against checksums provided in a configuration file to detect tampering or corruption.

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 peteonrails/voxtype --skill validate-binaries -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

peteonrails

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 peteonrails/voxtype at 6d2fc6ddbf.

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

Scanned
1 file, 104 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

This skill, validate-binaries, likely performs checks on binary files to verify their integrity and potentially identify issues. The specific validation methods aren't detailed but could include checksum verification or structural analysis. It aims to ensure binaries are functional and haven’t been corrupted during transfer or storage.

When to use it

  • Automated build pipelines: Integrate into CI/CD systems to validate compiled executables before deployment.
  • Software distribution: Verify the integrity of downloaded binary packages for users.
  • Security audits: Check binaries for signs of tampering or malicious modifications.
  • Data recovery: Validate recovered binary files after a system failure or data corruption event.

Key capabilities

  • Binary validation
  • Integrity checks (implied)
  • Potential structural analysis (implied)

Example prompts

  • "Validate this binary file: /path/to/myprogram."
  • "Check the integrity of example.exe against checksum XYZ123."
  • "Run a validation check on all binaries in the /opt/software directory."

Tips & gotchas

The specific validation methods used by this skill are not detailed, so understanding its limitations requires further investigation or documentation from the author. It's likely that you will need to provide the binary file path for it to operate.