Agent skill

Terminal Inspection

by Porabuild in Porabuild/Poracode

Read what the user's Terminal panel is actually printing and report the evidence.

Apache-2.0Auto-check passed

Install Terminal Inspection

skills CLI
$ npx skills add Porabuild/Poracode --skill terminal-inspection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Porabuild/Poracode terminal-inspection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/terminal/skills/terminal-inspection .claude/skills/terminal-inspection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
terminal-inspection
GitHub stars
115
Token cost
~443 tokens
SKILL.md length
283 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Read what the user's Terminal panel is actually printing and report the evidence.

  • SKILL.md covers Find the pane, Read it, When there is nothing and Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Terminal Inspection is an agent skill from Porabuild/Poracode. Read what the user's Terminal panel is actually printing and report the evidence.

Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

Example prompts

  • “/terminal-inspection”

What it can do on your machine

Read from SKILL.md and the folder at commit e56fcc8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Terminal Inspection loads about 443 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 283 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~443

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Porabuild/Poracode at commit e56fcc8, republished under its Apache-2.0 licence (© Porabuild). 283 words, ~443 tokens.

Download SKILL.mdSave it as .claude/skills/terminal-inspection/SKILL.md (or your agent's skills folder).
name
terminal-inspection
description
Read what the user's Terminal panel is actually printing and report the evidence.

Terminal

The user is pointing at the integrated Terminal panel they opened for this worktree — a dev server, a test run, a build. Not your own TUI, not an agent thread, not a chat transcript, not a file with that name.

Find the pane

Call list_terminals and nothing else. It resolves the caller's project and worktree on its own, so there is no id to ask the user for and no reason to call get_current_thread, list_threads, or read_thread first.

Panes come back oldest to newest. One pane: read it. Several: start with the newest that has outputLength > 0, then go older only if the evidence you need is missing. outputLength counts what that live shell has emitted — it is not the content and not a quality signal.

Read it

Call read_terminal with a terminalId returned by the list. Never pass a threadId.

Read for the answer, not for volume. A failing run usually has one first real error and a long tail of consequences — find the first one. A dev server usually answers "is it up, on which port, with what warnings".

When there is nothing

No panes: say no running Terminal panel is attached to this worktree. Do not fall back to the agent's own scrollback or a chat transcript and present that as the terminal.

Zero output: say the pane is running but has not printed anything yet. That is a real answer.

Report

Quote the lines that carry the answer and name the terminalId they came from. Separate what the pane printed from what you concluded. Never echo tokens, keys, or connection strings that scrolled past, and do not paste the entire scrollback when a dozen lines settle the question.

© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/plugins/terminal/skills/terminal-inspection of Porabuild/Poracode.

Open the folder on GitHubat commit e56fcc8

Compare with similar skills

Terminal Inspection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Terminal Inspection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Terminal Inspection this skillPorabuild/Poracode115—~443Automated safety check: PassApache-2.0
Node Inspect Debuggeropenclaw/openclaw392k1 repos~894Automated safety check: PassMIT
Terminal Openeraffaan-m/ECC276k—~635Automated safety check: PassMIT
Terminal Opsaffaan-m/ECC276k2 repos~750Automated safety check: PassMIT
Terminal Opsaffaan-m/ECC276k—~439Automated safety check: PassMIT
Terminal Opsaffaan-m/ECC276k—~323Automated safety check: PassMIT

Similar skills

  • Node Inspect Debugger

    openclaw/openclaw

    Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

    392k GitHub starsUsed in 1 repo~894 tokens
    Frontend & DesignAuto-check passed
  • Terminal Opener

    affaan-m/ECC

    Open an executable and its argument array in a visible terminal window through a reusable, shell-free launch plan with dry-run, JSON, capability detection, detached fallback, and standalone recovery…

    276k GitHub stars~635 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Terminal Ops

    affaan-m/ECC

    Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~750 tokens
    Testing & QAAuto-check passed
  • Terminal Ops

    affaan-m/ECC

    ECCのための証拠優先のリポジトリ実行ワークフロー。ユーザーがコマンドの実行、リポジトリの確認、CIの失敗のデバッグ、正確な実行と検証の証明を伴う狭い修正のプッシュを必要とする場合に使用する。

    276k GitHub stars~439 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Terminal Ops

    affaan-m/ECC

    基于证据优先的仓库执行工作流,适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。

    276k GitHub stars~323 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • A skill your agent uses when inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment where screenshots alone are not enough.

    276k GitHub starsUsed in 1 repo~2k tokens
    Game DevelopmentAuto-check passed

More from Porabuild/Poracode

All 21 skills in this repo
  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    115 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes
  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    115 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    115 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    115 GitHub stars~745 tokensUpdated yesterday
    Auto-check passed
  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    115 GitHub stars~691 tokensUpdated yesterday
    Auto-check passed
  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    115 GitHub stars~718 tokensUpdated yesterday
    Auto-check passed

Questions about Terminal Inspection

What does Terminal Inspection do?

Read what the user's Terminal panel is actually printing and report the evidence. Terminal Inspection is an agent skill from Porabuild/Poracode. Read what the user's Terminal panel is actually printing and report the evidence.

How do I install Terminal Inspection in Claude Code?

Run `npx skills add Porabuild/Poracode --skill terminal-inspection -a claude-code`. Or copy the skill folder (resources/plugins/terminal/skills/terminal-inspection in Porabuild/Poracode) into .claude/skills/terminal-inspection in your project. Claude Code loads it when a task matches its description.

How do I install Terminal Inspection in Codex?

Run `npx skills add Porabuild/Poracode --skill terminal-inspection -a codex`. Or copy the skill folder (resources/plugins/terminal/skills/terminal-inspection in Porabuild/Poracode) into .agents/skills/terminal-inspection in your project. Codex loads it when a task matches its description.

Can I use Terminal Inspection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Porabuild/Poracode --skill terminal-inspection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/terminal-inspection, .gemini/skills/terminal-inspection, .github/skills/terminal-inspection and .opencode/skills/terminal-inspection in your project.

What does Terminal Inspection need to run?

SKILL.md names no scripts, command-line tools or credentials: Terminal Inspection is instructions for the agent only.

Does Terminal Inspection access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Terminal Inspection safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Terminal Inspection use?

Terminal Inspection is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Terminal Inspection use?

About 443 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Terminal Inspection?

Skills that share tags, products or a category with Terminal Inspection: Node Inspect Debugger (openclaw/openclaw, 392k stars), Terminal Opener (affaan-m/ECC, 276k stars), Terminal Ops (affaan-m/ECC, 276k stars) and Terminal Ops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Terminal Inspection?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 115 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.

Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.