Skip to content
TrustedSkillsbeta
Back to all skills

Sf Debug

Checked
jaganpro·vlatest·testing·MIT

Inspects internal state & execution flow of jaganpro agents to diagnose issues during test runs.

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 jaganpro/sf-skills --skill sf-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

jaganpro

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 jaganpro/sf-skills at 53c9956c42.

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

Commit
53c9956c42
Manifest
skills/sf-debug/SKILL.md
Scanned
10 files, 1,604 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 Sf Debug skill analyzes Salesforce debug logs to diagnose issues during test runs and identify root causes. It helps users understand governor limit problems, stack traces, slow queries, CPU/heap pressure, and facilitates a reproduction-to-fix loop based on log evidence. This skill is specifically designed for analyzing .log files generated by Salesforce environments.

When to use it

  • When you need to determine the root cause of issues identified in Salesforce debug logs.
  • For diagnosing governor limit errors.
  • To investigate slow queries and performance bottlenecks.
  • To analyze CPU or heap pressure within a Salesforce org.
  • When attempting to reproduce and fix problems based on evidence found in log files.

Key capabilities

  • Analysis of Salesforce debug logs (.log files).
  • Interpretation of stack traces and exception analysis.
  • Identification of governor limit issues.
  • Investigation of SOQL/DML/CPU/heap performance.
  • Classification of issue severity (Critical, Warning, Info).
  • Recommendation of root-cause oriented fixes that are bulk-safe and testable.

Example prompts

  • "Analyze this Salesforce debug log for governor limit issues."
  • "Can you identify the cause of this slow query based on the provided log?"
  • "What's causing the CPU pressure shown in this Salesforce log file?"

Tips & gotchas

  • The skill requires a Salesforce org alias to retrieve logs.
  • It is not intended for debugging Apex tests or implementing code fixes; use sf-testing and sf-apex for those tasks respectively.
  • To get the most out of this skill, provide an approximate timestamp or transaction window related to the failing event.