Skip to content
TrustedSkillsbeta
Back to all skills

Debug Cli

Checked
antinomyhq·vlatest·testing·Apache-2.0

Automated CLI command debugging and error analysis using AntinomHQ's AI, streamlining test troubleshooting.

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 tailcallhq/forgecode --skill debug-cli -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

antinomyhq

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 antinomyhq/forge at d760d320d4.

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

Commit
d760d320d4
Manifest
.forge/skills/debug-cli/SKILL.md
Scanned
3 files, 243 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 provides a structured workflow for debugging and verifying changes to the forge CLI application. It focuses on systematic error analysis, using specific commands and flags to test functionality and reproduce issues. The core principle is to ensure changes are thoroughly tested in debug mode before any potential commitment.

When to use it

  • When developing or modifying the forge CLI application.
  • To systematically troubleshoot reported bugs within the forge CLI.
  • For testing new features added to the forge CLI.
  • When reproducing user-reported conversation issues with the CLI.
  • To verify fixes for identified bugs in a controlled environment.

Key capabilities

  • Build in Debug Mode: Uses cargo build for faster debugging cycles (avoiding --release).
  • Help Documentation Access: Provides commands to view current command and option documentation using --help.
  • Testing with -p Flag: Allows running forge with tasks in non-interactive mode.
  • Conversation Dumps: Exports conversations as JSON or HTML files for detailed analysis and reproduction.
  • Conversation Cloning: Enables creating copies of existing conversations to prevent modification of original bug evidence during debugging.

Example prompts

These are not user prompts to the skill, but example commands used with the skill:

  • ./target/debug/forge --help (To view main help documentation)
  • ./target/debug/forge -p "create a hello world rust program" (To test with a simple prompt)
  • ./target/debug/forge conversation dump <conversation-id> (To export a conversation as JSON)

Tips & gotchas

  • Always build in debug mode: Use cargo build, not cargo build --release.
  • Clone conversations before modifying: Never directly modify original conversations when debugging.
  • Understand the workflow: Follow the prescribed steps (build, documentation, testing, debugging) for effective troubleshooting.