Skip to content
TrustedSkillsbeta
Back to all skills

Unsafe Checker

Checked
actionbook·vlatest·backend

This tool analyzes prompts for potentially harmful or dangerous instructions, safeguarding against misuse and promoting responsible AI interaction.

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 actionbook/rust-skills --skill unsafe-checker -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

actionbook

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 actionbook/rust-skills at 5c40d3ad78.

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

Commit
5c40d3ad78
Manifest
skills/unsafe-checker/SKILL.md
Scanned
57 files, 7,133 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

The unsafe-checker skill analyzes Rust code to identify potential safety violations and unstable features. It helps developers ensure their projects adhere to safe coding practices by flagging risky patterns before they cause runtime errors.

When to use it

  • Reviewing third-party crates for hidden unsafe blocks or deprecated APIs.
  • Validating complex logic in performance-critical modules where manual auditing is error-prone.
  • Integrating into CI/CD pipelines to automatically block unsafe code commits.
  • Auditing legacy Rust codebases before refactoring them to modern standards.

Key capabilities

  • Detects usage of unsafe blocks and warns about their implications.
  • Identifies unstable features marked with #![feature(...)].
  • Highlights deprecated functions or types that may break in future versions.
  • Provides context-aware suggestions for safer alternatives.

Example prompts

  • "Scan this Rust module for any unsafe code and explain why it's risky."
  • "Check if this crate uses any unstable features that might cause compilation errors later."
  • "Analyze the following function for deprecated API usage and suggest replacements."

Tips & gotchas

This tool is designed specifically for Rust projects; applying it to other languages will yield no results. While it catches many issues, it should complement—not replace—manual code reviews by experienced developers.