Skip to content
TrustedSkillsbeta
Back to all skills

Unsafe Checker

Checked
goooice·vlatest·backend

This "Unsafe Checker" by goooice identifies potentially harmful or dangerous content within generated responses, promoting safer AI interactions.

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

goooice

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 goooice/rust-skills at 57af2e8da9.

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

Commit
57af2e8da9
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 goooice-unsafe-checker skill analyzes Rust code to identify potential issues related to unsafe blocks. It helps developers understand where unsafe code is used and flags possible areas of concern for memory safety or undefined behavior. This promotes safer and more reliable Rust programs by encouraging careful consideration of unsafe operations.

When to use it

  • Code Review: Use this skill when reviewing Rust code, especially in projects with complex or critical functionality.
  • Learning Rust: New Rust developers can leverage the checker to understand best practices for using unsafe blocks.
  • Refactoring: When refactoring existing code that uses unsafe, use this skill to ensure no new issues are introduced.
  • Security Audits: Integrate it into security audits of Rust-based applications.

Key capabilities

  • Identifies unsafe blocks in Rust code.
  • Flags potential memory safety concerns within unsafe regions.
  • Provides insights into the usage of unsafe operations.

Example prompts

  • "Analyze this Rust code for unsafe block usage: [paste code here]"
  • "What are the potential risks associated with this unsafe block? [paste code here]"
  • "Can you identify any memory safety issues in this function? [paste code here]"

Tips & gotchas

The skill is written in Rust, so it's most effective when analyzing Rust source code. While it highlights potential concerns, the checker’s output should be reviewed by experienced Rust developers to fully assess and mitigate risks.