Skip to content
TrustedSkillsbeta
Back to all skills

Unsafe Checker

Checked
zhanghandong·vlatest·backend

This "Unsafe Checker" analyzes text for potentially harmful or risky content, safeguarding users and applications from misuse.

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

zhanghandong

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 zhanghandong/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

What it does

The unsafe-checker skill identifies and flags potentially unsafe or insecure code patterns in Rust projects. It scans source files for common vulnerabilities, such as improper memory management, unchecked inputs, or usage of unstable APIs.

When to use it

  • Before merging pull requests in a Rust project to ensure security
  • During code reviews to catch risky practices early
  • As part of an automated CI/CD pipeline to enforce safety standards

Key capabilities

  • Scans Rust source files for unsafe patterns
  • Highlights potential memory-related issues
  • Detects use of unstable or deprecated APIs
  • Integrates with common development workflows

Example prompts

  • "Check this Rust file for unsafe code patterns."
  • "Scan the latest commit for security vulnerabilities in Rust."
  • "Analyze the project for unsafe usage of raw pointers."

Tips & gotchas

  • Ensure that your Rust environment is up to date for accurate detection.
  • The tool may flag legitimate code if used improperly; always review flagged items manually.