Command Output Display
v1.0.0展示完整终端命令及其全部输出，包括正常、错误、长输出、交互和后台运行，格式清晰易读，便于理解和调试。
⭐ 0· 134·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description and SKILL.md are consistent: the skill's goal is to display executed commands and their complete outputs. There are no unrelated required binaries, environment variables, or install steps.
Instruction Scope
The instructions explicitly require showing full stdout/stderr, preserving colors, printing long outputs, binary output markers, and examples that read or create files (e.g., /home/admin/.openclaw/*), view journalctl logs, and run systemctl. That behavior is coherent with the stated purpose (full output display) but it also means the skill's usage can reveal sensitive files, credentials, or system state if the agent executes commands that access them.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is written to disk or fetched during install.
Credentials
The skill requests no env vars or credentials (proportional). However SKILL.md references absolute user paths and system commands that can access sensitive configuration and logs. While not a mismatch, this increases the risk of sensitive-output disclosure when commands are executed.
Persistence & Privilege
always:false and no special privileges requested. The skill can be invoked autonomously by the agent (disable-model-invocation:false), which is the platform default; combined with the instruction to display full outputs this makes accidental or automated disclosure possible if the agent runs privileged commands.
Assessment
This skill is a presentation guideline and is internally coherent, but it instructs the agent to show complete command outputs (including file contents, logs, and errors). Before installing or allowing autonomous use, consider: 1) only enable it for trusted agents or require user invocation rather than autonomous runs; 2) avoid running it in environments containing secrets or sensitive config (e.g., /home/*, systemd logs, database dumps); 3) test it in a disposable or sandbox environment first; 4) if you expect the agent to execute commands, restrict which commands it may run (deny ones that cat config files, read secrets, or dump credentials). If the skill had code files, an install step, or requested credentials, that would change the assessment.Like a lobster shell, security has layers — review code before you run it.
latestvk976j84qng3x07vt4sk6g1zch58325ex
License
MIT-0
Free to use, modify, and redistribute. No attribution required.