shell

Execute user-provided shell commands verbatim and return output.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executors face the risk of misinterpretation or modification of commands when relaying shell instructions. This Skill runs the user-provided command exactly as written, ensuring fidelity and speed.

Core Features & Use Cases - Verbatim command execution: runs the text following /shell as the literal shell command without changes. - Immediate terminal feedback: returns exit status and any standard output or errors. - Explicit invocation guard: only triggers when the user uses /shell and provides a command.

Quick Start Type /shell followed by the command you want executed, and I will run it exactly as written.

Frequently Asked Questions about shell

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

FAQPage Schema
How do I execute a literal shell command without modification?

To execute a literal shell command without modification, use the /shell invocation followed by your command. The Skill runs the text verbatim, avoiding any interpretation or changes, and returns the termination status and output.

How does verbatim command execution work for on-demand debugging?

Verbatim command execution for on-demand debugging works by running the exact text provided after /shell. It bypasses command modification, ensuring fidelity and speed while returning the exit status and standard output or errors.

What is the best way to automate terminal commands and ensure they run exactly as written?

The best way to automate terminal commands and ensure they run exactly as written is to invoke /shell with a non-empty command body. This triggers verbatim execution and returns immediate terminal feedback including exit status and errors.

Do I need explicit invocation to run shell commands for automation tasks?

Yes, you need explicit /shell invocation and a non-empty command body to run shell commands for automation tasks. This guard ensures the Skill only triggers on demand and executes the command exactly as written.

What are the limitations of using a verbatim shell command execution approach?

A limitation of verbatim shell command execution is that it only triggers with explicit /shell invocation and a non-empty command body. It avoids command modification but requires the user to provide the exact command syntax.