shell

Execute literal shell commands in a terminal session.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/OM-bit-hub/daily_tracker --skill shell-om-bit-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shell
Source: https://github.com/OM-bit-hub/daily_tracker/tree/main/.agents/skills-cursor/shell
Command: npx skills add https://github.com/OM-bit-hub/daily_tracker --skill shell-om-bit-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute the exact shell command after the /shell invocation in the terminal, ensuring commands are run exactly as provided and not altered by the assistant.

Core Features & Use Cases

  • Literal execution of the text after /shell, running commands directly in a terminal session.
  • No repository inspection unless the command requires repository context, ensuring user intent remains intact.
  • Use Case: debugging or performing ad-hoc terminal operations without intermediary interpretation.

Quick Start

Invoke /shell followed by the exact command you want to run to execute it directly 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 run an exact terminal command without the assistant modifying it?

To execute an exact terminal command without modification, invoke /shell followed by the literal command text. The assistant runs the command directly in the terminal session without intermediary interpretation, ensuring user intent remains intact.

What is literal command execution in a terminal session?

Literal command execution is the process of running shell commands directly in a terminal exactly as provided. The /shell invocation bypasses assistant interpretation, returning the exit status, stdout, and stderr succinctly.

Can I use shell automation for ad-hoc terminal operations and debugging?

Yes, shell automation supports ad-hoc terminal operations and debugging. By invoking /shell with the exact command, you perform direct terminal execution without repository inspection unless the command itself requires repository context.

Does the shell command executor inspect my repository before running commands?

No, the shell command executor does not inspect the repository unless the command itself requires repository context. It focuses solely on literal execution of the text following the /shell invocation to preserve user intent.

What output does executing a shell command return?

Executing a shell command returns the exit status along with any stdout or stderr generated by the process. This output is presented succinctly to provide immediate feedback on the terminal operation.

When should I not use direct shell command execution?

You should avoid direct shell command execution when your task requires the assistant to interpret, validate, or modify the command before running it. This tool is designed exclusively for literal, on-demand terminal operations.