shell

Execute user-provided shell commands verbatim and report exit statuses.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/caezium/skills --skill shell-caezium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shell
Source: https://github.com/caezium/skills/tree/main/shell
Command: npx skills add https://github.com/caezium/skills --skill shell-caezium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Allows running a literal shell command only when explicitly requested, avoiding misinterpretation of user input and preserving system safety.

Core Features & Use Cases

  • Run exact shell commands as provided by the user, without modification.
  • Provide immediate execution results to support debugging, automation, and problem-solving tasks.

Quick Start

Provide the exact shell command to run after /shell and I will execute it verbatim.

Frequently Asked Questions about shell

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute shell commands on demand without modification?

To execute shell commands on demand, use the /shell trigger followed by your exact command. The system runs the literal input verbatim, ensuring precise command execution for debugging and terminal verifications without altering your syntax.

Can I run terminal commands verbatim for debugging purposes?

Yes, you can run terminal commands verbatim for debugging. By providing the exact shell command after the /shell trigger, the system executes it precisely as written and reports the immediate execution results and transparent exit status.

How does on-demand command execution handle system safety?

On-demand command execution handles system safety by only running commands when explicitly requested via the /shell trigger. This avoids misinterpretation of user input and preserves system safety by requiring a controlled, explicit user request.

What is the best way to pass terminal commands verbatim for immediate execution?

The best way to pass terminal commands verbatim for immediate execution is to append your exact command after the /shell trigger. This ensures the system processes the literal string exactly as provided, supporting automation and transparent exit status reporting.

Are there limitations to running shell commands verbatim in a controlled environment?

The limitation of running shell commands verbatim in a controlled environment is that the system only executes commands explicitly requested after the /shell trigger. It does not modify or interpret user input, requiring you to provide fully formed and accurate commands.

Why does my shell command execution require an explicit user request?

Shell command execution requires an explicit user request to preserve system safety and avoid misinterpretation. By demanding a controlled /shell trigger before running literal commands, the system ensures that only intentional, verbatim commands are processed.