shell

Execute literal shell commands and return stdout, stderr, and exit status.

Updated Aug 27, 2026

Search Tags:#automation #cli #safety #execution #command #terminal #shell

Ready to run

npx skills add https://github.com/cuongnm-dev/team-ai-config --skill shell-cuongnm-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shell
Source: https://github.com/cuongnm-dev/team-ai-config/tree/main/cursor/skills-cursor/shell
Command: npx skills add https://github.com/cuongnm-dev/team-ai-config --skill shell-cuongnm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run literal shell commands provided after /shell, ensuring they run exactly as received in the terminal.

Core Features & Use Cases

Execute the exact shell command text following /shell without modification.
Return exit status, stdout, and stderr to you for verification.
Use cases include quick one-off tasks, debugging, and maintenance commands.

Quick Start

Provide the /shell payload, and I will execute it as a literal shell command in the terminal.

Frequently Asked Questions about shell

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

FAQPage Schema

How do I execute literal shell commands and get the exit status?▼

To execute shell commands, provide the literal command text after the invocation prompt. The tool runs the command verbatim in a terminal execution environment and returns the exit status alongside stdout and stderr outputs for verification.

Can I run terminal commands for debugging without modification?▼

Yes, you can run terminal commands for debugging without modification. The tool preserves the provided command text verbatim without altering it, ensuring the terminal execution environment processes exactly what you input for accurate debugging results.

What is the best way to automate one-off CLI tasks and verify the output?▼

The best way to automate one-off CLI tasks is to provide the exact command payload to the tool. It executes the literal shell command directly in the terminal and returns the stdout, stderr, and exit status for immediate verification.

Does the command execution tool require a terminal execution environment?▼

Yes, the command execution tool requires a terminal execution environment to function properly. It relies on this environment to process the literal shell commands you provide and to accurately capture and return the stdout, stderr, and exit status.

What happens if I invoke the shell command tool without providing a command?▼

If you invoke the shell command tool without providing a command, it will prompt you to provide one. This ensures that the terminal execution environment receives the necessary literal command text to execute and return the expected outputs.

Are there limitations when running maintenance commands using this approach?▼

A key limitation is that the tool runs commands verbatim without modification, so any errors in the maintenance commands will execute as written. It returns stdout, stderr, and exit status, but does not inherently prevent unsafe CLI operations.