shell

Execute literal shell commands via /shell and report exit status and output.

Updated Dec 17, 2024

Search Tags:#automation #safety #terminal #shell #command-execution #execution-context

Ready to run

npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill shell-laf-us

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shell
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.cursor/skills-cursor/shell
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill shell-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you need to execute terminal commands exactly as written, this skill provides a controlled way to run them only after explicit user invocation.

Core Features & Use Cases

Literal command passthrough: forwards the exact command you provide after /shell without rewriting.
Deterministic execution: runs commands in a terminal tool and returns the exit status.
Use Case: ideal for quick checks, diagnostics, or controlled experiments where precise commands must be executed.

Quick Start

Tell the system to run a shell command by issuing /shell followed by the exact command you want executed.

Frequently Asked Questions about shell

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

FAQPage Schema

How do I run exact terminal commands without the AI rewriting them?▼

To run exact terminal commands without modification, invoke the /shell prefix and pass your literal command. The skill directly forwards the exact command to the terminal tool without rewriting, ensuring deterministic execution.

Can I use shell command execution for quick system diagnostics?▼

Yes, shell command execution is ideal for quick system diagnostics. By passing your diagnostic commands after /shell, the skill executes them in a terminal tool and reports the exact exit status and stdout/stderr output.

What is the best way to execute controlled terminal experiments safely?▼

The best way to execute controlled terminal experiments safely is by using the /shell invocation. This ensures commands are only executed when explicitly invoked by you, providing a controlled environment for precise command execution.

Does the terminal tool return the exit status and stderr for executed commands?▼

Yes, the terminal tool returns the exit status and both stdout and stderr for executed commands. It passes your literal command directly to the terminal and reports the results without any modification.

When should I not use literal command passthrough for command execution?▼

You should not use literal command passthrough if you need the AI to interpret, rewrite, or fix your terminal commands. This skill only executes exact commands provided after /shell without any modification or contextual rewriting.