shell

Executes user-provided text as literal shell commands in the terminal.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/pulak999/ai-tooling --skill shell-pulak999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shell
Source: https://github.com/pulak999/ai-tooling/tree/main/ai-assistant-kit/cursor-skills-cursor/shell
Command: npx skills add https://github.com/pulak999/ai-tooling --skill shell-pulak999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want an AI assistant to run an exact terminal command without rewriting, explaining, or inspecting the repository first, you need a direct pass-through execution path. ## Core Features & Use Cases - Literal Command Execution: Treats all text after the /shell invocation as the exact shell command and runs it immediately with the terminal tool. - No Rewriting or Inspection: Skips command modification, explanation, and repository inspection unless the command itself requires repository context. - Status Reporting: Reports the exit status and important stdout or stderr after execution. - Use Case: Type /shell ls -la to list directory contents instantly, or /shell git status to check your working tree without any AI interpretation of the command. ## Quick Start Invoke /shell followed by the exact terminal command you want executed, such as asking to run /shell npm test.

Frequently Asked Questions about shell

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

FAQPage Schema
How do I run an exact shell command through an AI assistant?

Invoke /shell followed by the literal command text. The skill passes everything after the invocation directly to the terminal tool without rewriting, explaining, or improving the command.

How to execute terminal commands without AI modifying them?

Use the /shell invocation, which treats all following text as the literal command. The skill explicitly prohibits rewriting or inspecting the repository before execution unless the command itself requires repository context.

What happens if I invoke /shell with no command?

The skill asks which command you want to run. It does not guess or execute anything when no text follows the /shell invocation.

Does the shell skill check the repository before running commands?

No, it skips repository inspection by default. Inspection only occurs when the command itself requires repository context to execute correctly.

What output does the shell skill return after execution?

It runs the command first, then briefly reports the exit status along with any important stdout or stderr produced by the command.