Skip to content
TrustedSkillsbeta
Back to all skills

Return Stack

Checked
simhacker·vlatest·other·MIT

This skill simulates a function call stack to analyze program execution and pinpoint errors or uncover hidden logic.

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 simhacker/moollm --skill return-stack -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

simhacker

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 simhacker/moollm at 8f6d840b2f.

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

Commit
8f6d840b2f
Manifest
skills/return-stack/SKILL.md
Scanned
1 file, 266 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 allows an AI agent to retrieve and display a call stack, providing valuable debugging information. It can trace the sequence of function calls leading up to a specific point in code execution. This is particularly useful for understanding complex program behavior or identifying the source of errors.

When to use it

  • Debugging: When encountering unexpected behavior, use this skill to understand the chain of events that led to the issue.
  • Code Understanding: To quickly grasp how a particular function was invoked and its context within a larger program.
  • Performance Analysis: To identify bottlenecks by examining which functions are being called frequently.
  • Tracing Execution Flow: When needing to visualize the path of execution through a complex system.

Key capabilities

  • Retrieves call stack information.
  • Displays the sequence of function calls.
  • Provides context for debugging and code understanding.

Example prompts

  • "Show me the current call stack."
  • "What functions were called leading up to this point?"
  • "Display the execution trace."

Tips & gotchas

The accuracy of the returned call stack depends on the underlying environment and available debugging information. Ensure that the agent has sufficient permissions or access to retrieve the necessary data.