CtrlK
BlogDocsLog inGet started
Tessl Logo

lite-screenshots

Use when asked to add before/after screenshots of a Lite UI change to a pull request, when a PR touching apps/lite/ui needs its visual change shown, or when extending the screenshot catalogue in apps/lite/e2e/tests/screenshots.spec.ts. Captures both sides locally against seeded fixtures, publishes the surfaces that changed, and posts them to the PR.

76

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An operationally rich, highly actionable skill body with an excellent validated workflow and concrete commands throughout. Its only weakness is modest verbosity in rationale passages and a large single-file footprint that leaves minor room for splitting.

Suggestions

Tighten the CI-abandonment paragraph in the intro to the operational conclusion (run locally, not in CI) and move the full backstory to a brief note, trimming rationale that does not change what Claude does.

Consider moving 'One-off capture' and 'Extending the catalogue' into reference files linked from the main flow, reducing the SKILL.md footprint while keeping the core 6-step flow prominent.

A few repeated justifications ('which reads as "my change did nothing"', 'which looks exactly like "this change is not visual"') could be consolidated into a single 'why a 0-changed result is ambiguous' callout to save tokens.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence with no basic-concept padding, but several rationale passages (the CI-abandonment backstory, repeated 'which reads as...' justifications) could be trimmed without losing operational value.

4 / 5

Actionability

Provides fully executable copy-paste console blocks (real pnpm/gh/jq/curl commands) and concrete TypeScript spec templates covering the common capture, compare, publish, and post cases.

5 / 5

Workflow Clarity

A clear numbered 1–6 flow with explicit validation checkpoints ('Check the unapply took effect', 'Fetch one raw URL before posting', 'Look at the images, do not just trust exit codes') and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but as a ~320-line self-contained monolith the secondary 'One-off capture' and 'Extending the catalogue' sections could plausibly live in separate reference files.

4 / 5

Total

18

/

20

Passed

Description

100%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.

A strong, third-person description that concretely states both the capability and the trigger conditions with natural keywords and specific file paths. It cleanly hits the top anchor on every dimension with no vagueness or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Captures both sides locally against seeded fixtures, publishes the surfaces that changed, and posts them to the PR' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (captures/publishes/posts) and when via a clear 'Use when asked to add... when a PR touching apps/lite/ui needs its visual change shown, or when extending the screenshot catalogue' trigger clause.

5 / 5

Trigger Term Quality

Covers natural terms users would say ('before/after screenshots', 'Lite UI change', 'pull request'/'PR', 'visual change', 'screenshot catalogue') plus synonyms and a concrete file path, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The 'Lite UI', 'apps/lite/ui', and 'apps/lite/e2e/tests/screenshots.spec.ts' anchors carve a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

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.

Repository
gitbutlerapp/gitbutler
Reviewed

Table of Contents

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.