Skip to content
TrustedSkillsbeta
Back to all skills

Unsafe Checker

Checked
thurbeen·vlatest·backend·MIT

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

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

thurbeen

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 thurbeen/rust-skills at 6029cb39b5.

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

Commit
6029cb39b5
Manifest
skills/unsafe-checker/SKILL.md
Scanned
57 files, 7,175 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 thurbeen-unsafe-checker skill analyzes Rust code to identify and highlight uses of the unsafe keyword. It helps developers understand where they are bypassing Rust's safety guarantees, enabling more informed decisions about potential risks. This skill provides a detailed report on each instance of unsafe blocks or functions within a given codebase.

When to use it

  • Code Reviews: Use this skill during code reviews to quickly identify and assess the usage of unsafe Rust code.
  • Security Audits: Integrate it into security audits to pinpoint areas where safety invariants might be compromised.
  • Learning Rust: New Rust developers can leverage this tool to understand how and why unsafe is used in existing projects.
  • Refactoring: When refactoring code, use the skill to track down all instances of unsafe blocks for potential conversion to safe alternatives.

Key capabilities

  • Identifies all uses of the unsafe keyword.
  • Provides detailed reports on each instance found.
  • Highlights specific lines of code containing unsafe blocks or functions.
  • Supports analysis of Rust source files.

Example prompts

  • "Analyze this Rust file for unsafe usage: [file path]"
  • "Show me all instances of the unsafe keyword in this project."
  • "Find any unsafe code related to memory management in this repository."

Tips & gotchas

  • The skill requires access to the Rust source code being analyzed.
  • While it identifies unsafe blocks, it doesn't automatically determine if they are correctly implemented; manual review is still crucial.