Terminal Command Execution

Execute terminal commands safely and reliably with clear pre-checks, output validation, and recovery steps. Use when users ask to run shell/CLI commands, ins...

Security Scan

The skill's instructions align with a command-runner, but they give broad discretion to probe system state and infer targets without clear, enforceable limits — this can lead to privacy/exposure risks despite the stated safety rules.

Purpose & Capability

The name/description (run and verify terminal commands) matches the SKILL.md: it explicitly instructs the agent how to inspect state, run incremental commands, handle failures, and verify outcomes. No external credentials or installs are requested, which is proportionate to the stated purpose.

Instruction Scope

The runtime instructions authorize inspecting the environment (cwd, `ls`, `git status`, process/listen state, logs) and to 'infer the exact command target from context'. That gives the agent broad discretion to read filesystem state and other local information potentially unrelated to a user's explicit request. While the document warns to keep secrets out of logs, there are no concrete guardrails (for example: explicit consent requirements, allowed paths, or deny-lists) to prevent accidental exposure of sensitive files or data during discovery probes.

Install Mechanism

Instruction-only skill with no install spec and no code files. This minimizes installation risk since nothing is written to disk by the skill itself.

Credentials

The skill requests no environment variables, credentials, or config paths. The lack of requested secrets is appropriate for a local command-execution helper.

Persistence & Privilege

The skill does not request always:true and is user-invocable. It does not request permanent system presence or modify other skills' configurations.

Scan Findings in Context

[no_code_files_or_regex_findings] expected: The scanner found no code files or regex matches. This is expected because the skill is instruction-only (SKILL.md). Absence of findings does not imply the instructions are safe.

What to consider before installing

This skill is coherent with a terminal-runner, but it gives the agent wide latitude to probe your filesystem and system state. Before installing or using it: 1) Prefer giving explicit, precise commands and paths rather than vague goals so the agent doesn't 'infer' and probe unrelated files. 2) Require the agent to ask for confirmation before running any discovery or state-inspection commands that could reveal sensitive files (e.g., listing home directories, reading logs, or running recursive searches). 3) Never allow destructive commands (rm -rf, mass chmod/chown, force resets) without explicit, context-specific consent. 4) Be mindful that outputs may contain secrets—avoid running commands that echo credentials or private keys. 5) If you need stronger protections, restrict the skill's allowed working directory or run it in a sandboxed environment. If you want a safer assessment, provide examples of the exact commands the skill will run or the clarifying-question logic it uses so I can re-evaluate with higher confidence.

Overview

Use this skill to run terminal commands with minimal risk and predictable outcomes. Prefer fast inspection, explicit intent checks, and verification after each state-changing step.

Workflow

1. Clarify goal and scope.

• Infer the exact command target from context (path, service, tool, environment).
• If request is ambiguous and risky, ask one concise clarifying question.

2. Pre-flight checks.

• Confirm working directory and required binaries.
• Inspect current state before changing it (for example ls, git status, process/listen state).
• Prefer non-destructive probes first.

3. Execute commands incrementally.

• Run the smallest command that advances the task.
• For multi-step tasks, validate each step before continuing.
• Use reproducible commands and avoid interactive flows when non-interactive options exist.

4. Handle failures systematically.

• Read stderr first and identify root cause class: permission, path, missing dependency, syntax, network, or runtime state.
• Apply one fix at a time, then re-run only the affected command.
• If privileged/destructive action is required, request user approval before proceeding.

5. Verify outcomes.

• Check exit status and observable state changes.
• For installs, verify with a version/health command.
• For edits, verify resulting files and behavior.

6. Report clearly.

• Summarize what ran, what changed, and current status.
• Include exact next command only when additional user action is required.

Safety Rules

• Avoid destructive commands by default (rm -rf, force resets, broad chmod/chown) unless explicitly requested.
• Never assume network, permissions, or package managers are available; test first.
• Prefer scoped operations (specific files/paths/services) over global changes.
• Keep secrets out of command output and logs.

Command Patterns

• Discovery: pwd, ls -la, rg --files, which <tool>
• Validation: <tool> --version, health/status commands, targeted smoke tests
• Diagnostics: inspect logs/errors first, then adjust one variable at a time