Skip to content
TrustedSkillsbeta
Back to all skills

Security Review

Checked
ncssm-robotics·vlatest·security·MIT

Helps with security, code review as part of implementing security and authentication workflows.

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 ncssm-robotics/ftc-claude --skill security-review -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

ncssm-robotics

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 ncssm-robotics/ftc-claude at 670e8c6722.

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

Scanned
1 file, 144 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 performs a security review of robotics code, specifically targeting potential vulnerabilities and insecure practices. It aims to identify weaknesses that could be exploited by malicious actors or lead to system failures. The tool provides feedback on coding standards and best practices related to secure robotics development.

When to use it

  • Before deploying robot code to production environments.
  • During security audits of existing robotics systems.
  • To educate developers about secure coding practices for robots.
  • When integrating third-party libraries or components into a robotics project.
  • As part of a continuous integration/continuous delivery (CI/CD) pipeline for robotics development.

Key capabilities

  • Automated code analysis.
  • Vulnerability identification.
  • Coding standards enforcement.
  • Security best practices recommendations.

Example prompts

  • "Analyze this Python script for security vulnerabilities: [script content]"
  • "Review this C++ robot control program and identify potential risks."
  • "Check this ROS node for insecure communication patterns."

Tips & gotchas

The skill is most effective when provided with complete code files or repositories. While it can identify common issues, a manual security review by a human expert remains crucial for comprehensive protection.