using-terminal

Enforces safe terminal command execution using configured wrappers and output truncation rules.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill using-terminal-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-terminal
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/using-terminal
Command: npx skills add https://github.com/danielsuguimoto/skills --skill using-terminal-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running raw shell commands from an AI agent often produces bloated output, wasted tokens, and inconsistent behavior across projects. This Skill standardizes how terminal commands are executed by enforcing a pre-flight checklist, routing commands through a configured terminal wrapper, and preventing oversized output. ## Core Features & Use Cases - Pre-flight Checklist: Verifies wrapper configuration, working directory, and related skill invocation before every command. - Wrapper Subcommand Mapping: Maps raw commands (git, npm, cargo, pytest, docker, and more) to compressed wrapper subcommands defined in project spec files. - Output Truncation Control: Guides use of scope flags and pipes like --stat, --oneline, head, and tail to keep command output under control. - Use Case: Before running git log or a test suite, the agent checks <project-root>/docs/terminal-wrappers.md, prefixes the command with the configured wrapper, and adds compact flags so the output stays readable and token-efficient. ## Quick Start Read the project docs for terminal wrappers and then run my test suite using the configured terminal wrapper with compact output.

Frequently Asked Questions about using-terminal

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

FAQPage Schema
How do I run shell commands through a terminal wrapper?▼

Check the terminal-wrappers.md file in the project docs folder for the configured wrapper, then prefix your command with it and use the matching subcommand, such as terminal-wrapper git status or terminal-wrapper cargo test.

How to reduce token usage from terminal command output?▼

Use scope flags like --stat, --oneline, and --name-only, and pipe output through head, tail, grep, or wc to capture only the decisive slice. For git log and diff, always add --no-pager with --oneline or --stat.

When should I not use the terminal wrapper?▼

Skip the wrapper when none is configured, when commands need byte-exact stdout like checksums, for interactive TUI programs like vim or tmux, and for container CLI commands which manage their own output formatting.

Why should I avoid cd in terminal commands?▼

The shell already runs in the correct working directory, so cd is redundant and error-prone. Use absolute paths for file arguments instead, reserving cd only for cases where no absolute-path form exists.

What happens if the terminal-wrappers.md file is missing?▼

If the spec file is missing or empty, run raw commands without any wrapper and note the gap. Never invent wrapper configuration contents that are not documented.