terminal-capture

Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

76%Weight 40%Scale 1-5

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

The content is highly actionable with executable code and a clear quick-start sequence, and it is mostly concise without concept padding. Its main weakness is workflow clarity: the batch screenshot workflow lacks validation checkpoints that outputs were generated successfully.

Suggestions

Add a verification step after running scenarios (e.g., check that expected PNG files exist and are non-empty) so the batch workflow has an explicit success checkpoint.

Move the full FlowStep/ScenarioConfig type reference and the supported-key list into a separate reference file linked from the body to reduce duplication with the quick-start examples.

Tighten the CI/verify chromium note and troubleshooting entries, which restate similar install guidance, to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code, API tables, and troubleshooting with no concept padding Claude already knows, but the full ScenarioConfig type block and FlowStep API partly duplicate details already shown in the quick-start examples and could be trimmed.	4 / 5
Actionability	Copy-paste-ready bash commands ("npx tsx integration-tests/terminal-capture/run.ts ..."), complete TypeScript scenario configs, the full FlowStep API with supported key names, and an output file table make the guidance fully executable across the common cases.	5 / 5
Workflow Clarity	Quick Start is numbered (write config, run, output) and troubleshooting maps cause to solution, but the batch run writes many screenshot files with no validation checkpoint verifying outputs succeeded, so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Clear section headers (Prerequisites, Architecture, Quick Start, FlowStep API, Examples, Troubleshooting) give good structure, but the bulk API and full type reference are inlined in a ~270-line file with no external reference files to offload them.	4 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 strong: it names the domain and several concrete actions, provides comprehensive natural trigger terms, and explicitly answers both what it does and when to use it. It is a clear, low-conflict, third-person description.

Dimension	Reasoning	Score
Specificity	"Automates terminal UI screenshot testing for CLI commands" plus "testing slash commands (/about, /context, /auth, /export), generating visual documentation" lists several concrete actions but stops short of a comprehensive enumeration, matching the anchor for several specific actions with minor gaps.	4 / 5
Completeness	It explicitly states what the skill does ("Automates terminal UI screenshot testing for CLI commands") and when to use it ("Applies when reviewing PRs... or when 'terminal screenshot'... is mentioned"), satisfying both halves with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases "'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture'" alongside contextual triggers like reviewing PRs that affect CLI output, giving comprehensive synonym-level coverage a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	The niche (terminal UI screenshot testing for CLI commands) with distinctive triggers like "terminal-capture" and named slash commands makes it clearly distinguishable with minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: QwenLM/qwen-code
Path: .qwen/skills/terminal-capture/SKILL.md
Commit: 054eabb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.