bash

Executes shell commands in the workspace with output and error capture.

4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/mkalkere/agent-coordinator --skill bash-mkalkere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bash
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/core/bash
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill bash-mkalkere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides direct access to the operating system shell from the workspace, enabling you to run commands, scripts, and system operations without leaving your development environment.

Core Features & Use Cases

  • Execute arbitrary shell commands in the workspace to automate tasks such as version control operations, building, testing, dependency installation, and system inspection.
  • Safely run scripts and one-off commands while capturing stdout, stderr, and exit codes for reliable automation and auditing.
  • Use case example: quickly verify repository status, install dependencies, or run a project-specific maintenance task from within the AI-assisted workflow.

Quick Start

Provide a shell command you want to run in the workspace, and the skill will execute it and return the output.

Frequently Asked Questions about bash

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

FAQPage Schema
How do I execute shell commands in my workspace without leaving the development environment?

To execute shell commands in your workspace, you provide the desired command to the skill, which spawns a subprocess to run it and captures the resulting stdout, stderr, and exit code. This allows you to perform system operations directly within your environment.

Can I run scripts for version control, builds, and tests directly in the project workspace?

Yes, you can run scripts for version control, builds, and tests directly in the project workspace. The skill executes arbitrary shell commands, enabling you to automate project-specific maintenance tasks and dependency installation safely.

Does executing shell commands as a subprocess capture stdout, stderr, and exit codes?

Yes, executing shell commands as a subprocess captures stdout, stderr, and exit codes. The builtin handler enforces timeout and safety checks while returning the command output, ensuring reliable automation and auditing for your workspace operations.

What is the best way to safely run one-off commands and inspect system output?

The best way to safely run one-off commands and inspect system output is by passing the command to the skill's builtin handler. It enforces safety checks and timeouts while spawning the subprocess, capturing the complete output for reliable auditing.

Are there limitations or safety checks when running general scripting tasks in the workspace?

When running general scripting tasks in the workspace, limitations are managed through enforced safety checks and timeouts. The subprocess handler restricts execution to ensure safe operation, capturing all standard output and errors without leaving the environment.