SkillAgentSearch skills...

terminal-screenshot

MUST be used right after changing any CLI color config (delta/bat/themes/lazygit pager) β€” renders the terminal's colored output to a PNG so Claude can actually SEE contrast, alignment, and highlighting instead of raw ANSI codes.

Install / Use

npx skills add daymade/claude-code-skills --skill terminal-screenshot

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Claude Code

Our assessment of terminal-screenshot

terminal-screenshot scores 92/100 on our quality scale, 914th of 4,698 Development & Engineering skills we index (top 20%).

Its SKILL.md is 6.4 KB long, well organised into 16 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so terminal-screenshot is actively maintained.
  • Our last check on 2026-10-27 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

terminal-screenshot compared with similar skills

All 4 of these similar skills score higher than terminal-screenshot; compare them before choosing.

SkillScoreStarsUpdatedFormat
terminal-screenshot (this skill)by daymade921.4k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md

Frequently asked questions

How do I install terminal-screenshot?
Run npx skills add daymade/claude-code-skills --skill terminal-screenshot. The install tabs above show the steps for each supported agent.
Which AI agents does terminal-screenshot work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is terminal-screenshot safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is terminal-screenshot still maintained?
The repository was last updated about 2 months ago, so terminal-screenshot is actively maintained.

name: terminal-screenshot description: >- MUST be used right after changing any CLI color config (delta/bat/themes/lazygit pager) β€” renders the terminal's colored output to a PNG so Claude can actually SEE contrast, alignment, and highlighting instead of raw ANSI codes. Use for delta git diff colors, bat syntax highlighting, starship prompt, eza/ls colors, or ripgrep matches. Trigger phrases: ηœ‹η»ˆη«―ζ•ˆζžœ, 终端ζˆͺε›Ύ, ιͺŒθ―ι…θ‰², terminal screenshot.

Terminal Screenshot

Render the colored output of a terminal command into a PNG image, then read that image to judge the result visually.

Why this exists

When a command's output arrives as a tool result, Claude sees plain text plus raw escape codes like \x1b[48;2;92;30;34m β€” not the rendered colors. That makes it impossible to honestly answer "is the diff's add/remove contrast strong enough?" or "did this theme come out too dark?". Reading hex values is guessing. This skill turns the output into an image so the judgement is based on what a human would actually see on screen.

The method: capture, then render

Two separate steps. Keep them separate β€” that separation is the whole trick.

Step 1 β€” Capture full-fidelity ANSI to a file

Most CLIs drop or downgrade colors when they detect they're not writing to a real terminal (a pipe or a child process). Force full coloring and save to a .ansi file. The exact flag depends on the tool β€” recipes below.

The single most important rule: never let the renderer run the command for you. freeze --execute "git diff | delta" looks convenient but produces a degraded result β€” delta (and lazygit, and anything that probes terminal capabilities) runs inside freeze's child pty, detects a reduced environment, and silently drops its background blocks, line-number column, and header box. Capture in a normal shell first, render second.

Step 2 β€” Render the ANSI file to PNG, then read it

Use the bundled wrapper, which prefers freeze and falls back to a stdlib renderer + headless Chrome:

scripts/render_ansi.sh <input.ansi> <output.png> [background_hex]

Then read the PNG with the Read tool and judge the colors.

Background color must match the real terminal, or a dark theme verified on a white page looks wrong. On macOS with Ghostty:

ghostty +show-config --default | grep '^background'   # e.g. 282c34 (the default)

Pass it as #282c34. If unknown, a dark terminal is usually near #1d1f21–#282c34.

Capture recipes per tool

Pick a --width close to the real terminal (β‰ˆ100–120) so wrapping matches.

| Tool | Capture command (writes full-color ANSI) | |------|------------------------------------------| | delta (git diff) | git --no-pager diff \| delta --dark --line-numbers --width=110 > /tmp/x.ansi | | git diff (native) | git -c color.ui=always --no-pager diff > /tmp/x.ansi | | bat | bat --color=always --style=numbers <file> > /tmp/x.ansi | | eza | eza -la --color=always --icons > /tmp/x.ansi | | ls (GNU) | ls -la --color=always > /tmp/x.ansi | | ls (macOS/BSD) | CLICOLOR_FORCE=1 ls -laG > /tmp/x.ansi | | ripgrep | rg --color=always 'pattern' <path> > /tmp/x.ansi | | anything else | CLICOLOR_FORCE=1 <cmd> > /tmp/x.ansi or <cmd> --color=always, or wrap in a real pty: script -q /dev/null <cmd> |

Note delta always emits its configured colors even to a file, so the only trap for delta is Step 1's rule (don't render it via freeze --execute).

Full example: verify a delta color change

# after editing [delta] colors in gitconfig, in any repo with a diff:
git --no-pager diff | delta --dark --line-numbers --width=110 > /tmp/diff.ansi
scripts/render_ansi.sh /tmp/diff.ansi /tmp/diff.png "#282c34"
# then: Read /tmp/diff.png and judge whether add/remove contrast is clear

TUI programs (lazygit, htop, top) β€” out of scope

Full-screen TUIs paint with cursor positioning, not a linear ANSI stream, so they can't be captured this way. To check a TUI's colors, verify the underlying piece in isolation β€” e.g. for lazygit's diff, render git diff | delta as above (lazygit calls the same delta config). For a true TUI screenshot, run it in a real terminal and capture the screen (a screencapture/computer-use task), not this skill.

Installing freeze (the preferred renderer)

freeze is charmbracelet/freeze β€” it renders ANSI to PNG/SVG/WebP with faithful background blocks and nice chrome.

Do not run brew install freeze β€” that installs an unrelated GUI app of the same name (a cask). The CLI lives in charmbracelet's tap or via go install:

# Option A β€” Homebrew tap (needs GitHub reachable)
brew install charmbracelet/tap/freeze

# Option B β€” go install (works behind a firewall via a Go module mirror)
GOPROXY=https://goproxy.cn,direct GOSUMDB=off \
  go install github.com/charmbracelet/freeze@latest
# binary lands in "$(go env GOPATH)/bin/freeze"

GOSUMDB=off is needed when the checksum database (sum.golang.org) is unreachable and go install hangs on "verifying module ... 504".

If freeze can't be installed, the wrapper automatically falls back to the bundled scripts/ansi2html.py (stdlib only) + headless Chrome β€” no extra dependency beyond a Chrome install. The fallback uses a fixed window size; widen --window-size in render_ansi.sh if output is clipped.

Bundled scripts

  • scripts/render_ansi.sh β€” render a captured .ansi file to PNG (freeze, else Chrome fallback). This is the entry point; call it after Step 1.
  • scripts/ansi2html.py β€” stdlib ANSIβ†’HTML converter used by the fallback path. Handles 24-bit truecolor, 256-color, bold, and resets, preserving background color blocks (the part naive renderers drop).

Common pitfalls

  • Letting the renderer run the command (freeze --execute "delta …") β†’ degraded output. Capture in a normal shell first, render the file second.
  • Non-TTY strips color β†’ force it (--color=always / CLICOLOR_FORCE=1 / script -q /dev/null).
  • Wrong background color β†’ a dark CLI theme rendered on a white page misjudges contrast. Use the real terminal background.
  • Light/dark mismatch β†’ if the terminal is dark, the CLI's colors must be its dark variant. Verifying a light=true config against a dark terminal shows inverted, hard-to-read colors (and is itself the bug, not the renderer's fault).
  • brew install freeze installs the wrong (GUI cask) tool β€” use the tap or go install.

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryDevelopment
Updated1mo ago
Forks219

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
terminal-screenshot β€” Claude Code Skill: Install & Safety Check | SkillAgent