CtrlK
BlogDocsLog inGet started
Tessl Logo

app-preview-video

When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).

78

Quality

98%

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

96%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 body is lean, highly actionable, and well-sequenced with validation checkpoints and an error-recovery loop. Its only gap is progressive disclosure: with no bundle files, all detailed reference material lives inline in a single >50-line file.

Suggestions

Move the platform spec tables (iOS/Play) and Common Rejection Reasons table into a references/ file (e.g. references/specs.md), keeping only a concise summary plus a one-level-deep pointer in SKILL.md, to strengthen progressive disclosure.

Extract the 3-Variant Strategy and Localization Strategy detail into a reference file and link to it, so SKILL.md stays a lean overview.

Consider replacing the persona line ("You are an App Store Preview video specialist…") with a task-scoped objective to further tighten conciseness.

DimensionReasoningScore

Conciseness

Table-driven and dense with no concept-over-explanation (no "what is an App Store" padding); assumes Claude's competence and every section earns its place; not score 4 because there are no notable instances of over-explanation to trim.

5 / 5

Actionability

Provides a copy-paste-ready script output template plus concrete specs (H.264/MP4/30fps/15–30s) and a rejection-issue→fix table that cover the common cases; not score 4 because guidance is fully executable rather than having minor gaps.

5 / 5

Workflow Clarity

Sequenced 5-step Initial Assessment intake, a pre-submission Production Checklist as validation checkpoint, and a Common Rejection Reasons table as an error→fix feedback loop; not score 4 because both checkpoints and a recovery loop are present.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep cross-skill handoffs (screenshot-optimization, ab-test-store-listing, localization), but all reference material (specs, rejection fixes, variant strategy) is inlined with no bundle-file split; not score 5 because content is not split across files, and not score 3 because structure and navigation are good.

4 / 5

Total

19

/

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.

The description is exemplary: concrete multi-action scope, comprehensive natural trigger phrases, explicit what/when guidance, and clear boundary routing to sibling skills. It uses third-person voice with no padding.

DimensionReasoningScore

Specificity

Lists four concrete actions ("plan, script, produce, or optimize") on a clearly named domain (App Store Preview videos / Google Play promo videos), matching the comprehensive-coverage anchor; not score 4 because the action list is multi-action and complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both "what" (plan/script/produce/optimize the autoplay videos shown in search and product pages) and "when" ("Use when the user mentions…" with concrete trigger phrases); not score 4 because the "when" is fully explicit with named triggers rather than weakly specified.

5 / 5

Trigger Term Quality

Enumerates a wide range of natural user phrases including synonyms ("App Preview", "preview video", "promo video", "Play Store video", "video script", "video specs", "should I add a preview video"); not score 4 because coverage is comprehensive rather than missing common variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (store preview/promo videos specifically) with distinct triggers and explicit boundary handoffs to screenshot-optimization and ab-test-store-listing; not score 4 because conflict risk is minimal and boundaries are explicitly drawn.

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