CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/tui-snapshot-tester

Snapshot testing for terminal UI apps (TUIs) - captures rendered terminal frames as deterministic SVG / text snapshots, diffs them on every run, surfaces a reviewable HTML report on failure, and supports `--snapshot-update` to accept changes intentionally. Wraps `pytest-textual-snapshot` for Python Textual apps; provides equivalent recipes for Ratatui (Rust) `insta` snapshots, Charm Bracelet (Go) `teatest` golden files, and Ink (Node) `ink-testing-library`. Use for any TUI where layout regressions otherwise reach users via `screenshot looks wrong in terminal`.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and well-sequenced with review and determinism checkpoints across four languages. Its main weakness is progressive disclosure: everything lives in one monolithic file with the secondary-language recipes inline rather than split into clearly signaled reference files.

Suggestions

Move the Rust/Ratatui, Go/Bubble Tea, and Node/Ink recipes (Steps 5–7) into separate reference files (e.g. references/rust.md, references/go.md, references/node.md) and link to them from the primary Python path so the main SKILL.md stays lean.

Keep the Textual/Python workflow as the single inline quick-start and summarize the other languages as one-line pointers with their update command, surfacing full recipes only on demand.

Consider extracting the determinism checklist (Step 8) and anti-patterns table into a shared reference so both the primary and secondary recipes can point to one canonical source.

DimensionReasoningScore

Conciseness

The body is code-dominant with minimal connective prose; framing like the Overview quotes the authoritative source tersely rather than padding, so most tokens earn their place and it assumes Claude's competence.

3 / 3

Actionability

Provides fully executable, copy-paste-ready code for all four languages plus a CI yaml and concrete commands (`pip install`, `pytest --snapshot-update`, `cargo insta accept`, `go test -update`, `jest -u`), matching the 'fully executable' anchor.

3 / 3

Workflow Clarity

A clear Step 1–9 sequence with explicit review/determinism checkpoints — the HTML-report review loop before `--snapshot-update`, the determinism gate, and the anti-patterns table — gives feedback loops for the mutating snapshot-update operation.

3 / 3

Progressive Disclosure

Sections are well-organized and external references are clearly signaled, but the skill is a single ~250-line file with no bundle files and the Rust/Go/Node recipes inline; the secondary-language content that could be split into one-level reference files is kept inline.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, naming concrete actions and per-language tools while giving an explicit 'Use for' clause with a natural user utterance. It is third-person throughout and clearly distinct from adjacent testing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "captures rendered terminal frames as deterministic SVG / text snapshots, diffs them on every run, surfaces a reviewable HTML report on failure" — and names the specific tool per language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (capture/diff/report/update frames) and when ("Use for any TUI where layout regressions otherwise reach users via `screenshot looks wrong in terminal`"), with an explicit trigger clause present.

3 / 3

Trigger Term Quality

Covers natural terms users would say — "TUI", "terminal UI apps", "snapshot testing", and the verbatim utterance trigger "screenshot looks wrong in terminal" — giving good coverage of how a user would actually phrase the need.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (TUI layout snapshot testing) with distinct triggers and named tools, and is differentiated from text-CLI testing and browser screenshot skills, so it is unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents