CtrlK
BlogDocsLog inGet started
Tessl Logo

screenshot-optimization

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

68

Quality

82%

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

65%

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

The content is concrete and highly actionable with excellent slot-by-slot guidance and copy-paste templates, but it is somewhat verbose and presents a long, mostly-inline body with an implicit workflow and a missing referenced file. Tightening the prose, adding an assessment-to-output checkpoint, and splitting reference material into bundle files would raise the weaker dimensions.

Suggestions

Trim the "You are an expert..." preamble and condense elaborative prose so every token earns its place (improves conciseness).

Add an explicit validation/review checkpoint between the Initial Assessment and the Screenshot Plan (e.g., confirm target audience and top-3 features before drafting slots) to strengthen workflow clarity.

Move the detailed 10-slot strategy, design-brief checklist, and competitor-audit table into a references/ bundle file (and create or correct the `app-marketing-context.md` reference) so the body stays an overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and mostly efficient (slot framework, do/don't tables, formulas) with little padding of concepts Claude already knows, but the "You are an expert in App Store creative optimization..." preamble and some elaboration could be tightened, matching the score-2 anchor of mostly efficient with room to trim rather than the fully lean score-3 bar.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: a 10-slot strategy with patterns to use/avoid, a `[Benefit Headline] + [Feature UI] + [Supporting Detail]` formula, a slot-by-slot output template, and a design-brief checklist — well above the incomplete-guidance bar of score 2.

3 / 3

Workflow Clarity

The "Initial Assessment" (numbered 1–5) and slot sequence give a present sequence, but there are no validation checkpoints or feedback/recovery loops between assessment, design, and audit, fitting score-2 (sequence present, checkpoints implicit) rather than score-3 (explicit validation steps).

2 / 3

Progressive Disclosure

Sections are well-organized, but at ~160 lines with no bundle files the content is largely inline (the full 10-slot strategy, design brief, and audit tables could be split), and the referenced `app-marketing-context.md` does not exist in the bundle — matching score-2 (some structure, content that should be separate is inline) rather than the one-level-deep-reference score-3 bar.

2 / 3

Total

9

/

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 strong: it states concrete actions, lists natural trigger phrases, answers both what and when, and explicitly distinguishes the skill from adjacent ones. No changes needed.

DimensionReasoningScore

Specificity

Names the App Store domain and three concrete actions — "design, optimize, or evaluate App Store screenshots and preview videos" — meeting the score-3 bar for multiple specific concrete actions rather than the partial coverage of score 2.

3 / 3

Completeness

Explicitly answers both what ("design, optimize, or evaluate App Store screenshots and preview videos") and when ("When the user wants to..." and "Also use when the user mentions..."), satisfying the score-3 requirement for both clauses.

3 / 3

Trigger Term Quality

Lists natural user phrases — "screenshots", "app preview", "product page design", "screenshot design", "creative assets", "what should my screenshots show" — giving broad coverage of terms a user would actually say, beyond the partial set of score 2.

3 / 3

Distinctiveness Conflict Risk

Carves a clear App Store-screenshot niche and explicitly disambiguates siblings ("For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit."), making conflict unlikely as the score-3 anchor requires.

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.

Repository
Eronred/aso-skills
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.