run-shell

Execute shell commands with configurable working directory and timeout.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill run-shell-allbeingsfuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-shell
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/system/run-shell
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill run-shell-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Run Shell skill lets agents perform system-level operations without manual terminal interaction, reducing context switching and human error when running commands, installing packages, or managing processes across platforms.

Core Features & Use Cases

  • Cross-platform command execution: Run bash on macOS/Linux and PowerShell on Windows with automatic PowerShell encoded command handling.
  • Controlled execution parameters: Specify working directory and timeout to safely run installs, builds, or cleanup tasks.
  • Use Case: Install dependencies in a project folder, run test suites, or execute maintenance scripts as part of an automated workflow.

Quick Start

Run the run-shell skill with a command and optional cwd and timeout, for example run the command to list files in a project directory with a 60 second timeout.

Frequently Asked Questions about run-shell

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

FAQPage Schema
How do I execute shell commands across Windows, macOS, and Linux from an automated workflow?

Executing shell commands across platforms is handled by running bash on macOS and Linux, and PowerShell with automatic encoded command handling on Windows, allowing system operations without manual terminal interaction.

Can I run PowerShell commands on Windows and bash scripts on macOS using the same execution method?

Yes, cross-platform command execution supports running bash on macOS and Linux while automatically handling PowerShell encoded commands on Windows, enabling consistent script execution across different operating systems.

How do I set a working directory and timeout when running build or test scripts?

Controlled execution parameters let you specify a working directory and timeout to safely run installs, builds, or cleanup tasks, ensuring scripts execute within a defined project folder and time limit.

What's the best way to automate package installation and process management without manual terminal access?

Automating package installation and process management is achieved by executing shell commands within controlled agent sessions, reducing context switching and human error during system-level operations like dependency installs.

Does run-shell support ad hoc system queries and directory management for automated maintenance scripts?

Yes, run-shell supports ad hoc system queries, directory management, running build or test scripts, and executing maintenance scripts, applying to a range of system operations across Windows, macOS, and Linux.

Why should I use controlled agent sessions for command execution instead of manual terminal interaction?

Controlled agent sessions provide deterministic execution for shell commands, reducing human error and context switching when performing system operations, running scripts, or installing packages across multiple platforms.