Skip to content
TrustedSkillsbeta
Back to all skills

Apex:Debug

Checked
benredmond·vlatest·testing·MIT

Examine internal apex code execution paths and variable states to diagnose complex Salesforce logic issues.

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 benredmond/apex --skill apex:debug -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

benredmond

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 benredmond/apex at 003ff00b19.

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

Scanned
1 file, 358 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 apex:debug skill provides debugging capabilities for Apex applications. It allows you to inspect variables, step through code execution, and identify potential issues within your Apex environment. This is particularly useful when troubleshooting complex logic or integrations.

When to use it

  • Troubleshooting Salesforce Apex errors: Use this skill when encountering unexpected behavior or error messages in your Apex code.
  • Debugging triggers and scheduled jobs: Quickly pinpoint the source of issues within asynchronous Apex processes.
  • Understanding complex business logic: Step through code execution to gain a deeper understanding of how different components interact.
  • Investigating performance bottlenecks: Identify slow-running sections of your Apex code.

Key capabilities

  • Variable inspection
  • Code stepping
  • Error identification
  • Apex environment debugging

Example prompts

  • "Debug this Apex class: [paste Apex class code]"
  • "Step through the execution of my trigger on Account."
  • "Inspect the values of these variables in my Apex method."

Tips & gotchas

This skill requires a Salesforce development environment with appropriate debugging permissions. The output will be specific to the context of your Apex application and may require familiarity with Apex code structure.