Skip to content
TrustedSkillsbeta
Back to all skills

Rr Debugger

Checked
gadievron·vlatest·backend

The Rr Debugger swiftly identifies and resolves issues within your Rr workflows, boosting efficiency and ensuring accurate results.

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 gadievron/raptor --skill rr-debugger -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

gadievron

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 gadievron/raptor at 990d9f3cd7.

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

Commit
990d9f3cd7
Manifest
.claude/skills/crash-analysis/rr-debugger/SKILL.md
Scanned
3 files, 395 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 rr-debugger skill provides debugging capabilities for Raptor, a Rust-based runtime environment. It allows you to inspect the state of your Raptor programs during execution, identify errors, and understand program flow. This is achieved through features like breakpoints, variable inspection, and stack traces within the Raptor environment.

When to use it

  • Troubleshooting unexpected behavior: Use rr-debugger when a Raptor program isn't working as expected and you need to pinpoint the cause.
  • Understanding complex logic: Step through code execution to better understand how intricate algorithms or data structures are behaving.
  • Debugging performance issues: Identify bottlenecks in your Raptor programs by observing variable values and function calls during runtime.
  • Learning Raptor internals: Use it to explore how the Raptor runtime itself operates.

Key capabilities

  • Breakpoints: Set breakpoints within Raptor code to pause execution at specific lines.
  • Variable inspection: Examine the values of variables during program execution.
  • Stack traces: View the call stack to understand the sequence of function calls leading to a particular point in the program.

Example prompts

  • "Set a breakpoint on line 25 of main.rs."
  • "Inspect the value of variable 'x' at this point."
  • "Show me the current call stack."

Tips & gotchas

The rr-debugger skill is specifically designed for use with Raptor programs written in Rust. Familiarity with Rust debugging concepts and the Raptor runtime environment will be helpful to maximize its effectiveness.