Skip to content
TrustedSkillsbeta
Back to all skills

Debug Cli

Checked
microck·vlatest·testing

Debug Kubernetes deployments directly from the command line using microck's AI-powered analysis and troubleshooting suggestions.

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 microck/ordinary-claude-skills --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

microck

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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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 microck/ordinary-claude-skills at 1056d293d4.

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

Commit
1056d293d4
Manifest
skills_all/debug-cli/SKILL.md
Scanned
4 files, 412 lines
Copies in repo
2 — all of them scanned
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 microck-debug-cli skill provides command line debugging capabilities to AI agents. It allows users to execute commands within a shell environment, inspect variables, and troubleshoot issues in real time. This is particularly useful for complex tasks requiring iterative refinement or interaction with external tools.

When to use it

  • Troubleshooting Agent Errors: When an agent encounters unexpected behavior or errors during task execution.
  • Interactive Development: For agents undergoing development or needing adjustments based on live feedback.
  • Environment Inspection: To examine the state of a virtual environment or system that the agent is operating within.
  • Complex Task Debugging: When an agent needs to interact with external tools or APIs and requires debugging assistance.

Key capabilities

  • Shell execution
  • Variable inspection
  • Real-time troubleshooting

Example prompts

  • "Run ls -l in the current directory."
  • "What is the value of the user_name variable?"
  • "Execute ping google.com and show me the output."

Tips & gotchas

The agent needs appropriate permissions to execute commands within the shell environment. Be mindful of security implications when granting these permissions, especially in production environments.