Skip to content
TrustedSkillsbeta
Back to all skills

Sls Trace Analyzer

Checked
abcfed·vlatest·testing·MIT

The Sls Trace Analyzer swiftly dissects SLT traces for anomalies and insights, boosting troubleshooting efficiency and rapid issue resolution.

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 abcfed/claude-marketplace --skill sls-trace-analyzer -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

abcfed

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 abcfed/claude-marketplace at f90c972905.

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

Commit
f90c972905
Manifest
plugins/abc-development-plugin/skills/sls-trace-analyzer/SKILL.md
Scanned
3 files, 996 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 sls-trace-analyzer skill analyzes execution traces to identify performance bottlenecks and potential errors. It can parse stack traces, pinpoint slow function calls, and provide insights into resource usage within a system. This allows for targeted optimization and debugging efforts.

When to use it

  • Debugging Performance Issues: Use when an application is running slowly or experiencing unexpected delays.
  • Analyzing Error Logs: Employ this skill to understand the root cause of errors by examining associated stack traces.
  • Optimizing Resource Usage: Identify functions consuming excessive resources (CPU, memory) based on trace data.
  • Post-Deployment Monitoring: Integrate with monitoring systems to proactively detect and address performance regressions.

Key capabilities

  • Stack Trace Parsing
  • Function Call Identification
  • Resource Usage Analysis
  • Error Context Extraction

Example prompts

  • "Analyze this stack trace: [paste stack trace here]"
  • "What functions are contributing most to the overall execution time?"
  • "Explain the error in this log and provide a possible solution."

Tips & gotchas

The skill's effectiveness depends on the quality of the provided execution traces. Ensure that tracing is enabled at an appropriate level within your application for accurate analysis.