CtrlK
BlogDocsLog inGet started
Tessl Logo

app-clips

When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/app-clips/SKILL.md
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.

A solid, actionable reference with concrete code, exact limits, and a checklist, weakened by verbosity and a lack of validation feedback loops in its workflow. Progressive disclosure is held back by inline detail that a longer skill like this would normally split into reference files.

Suggestions

Trim Claude-already-knows content (the full App Clip surface enumeration, trade-off table, ASO-implication prose) and editorial filler to tighten the body toward the token-efficient score-3 anchor.

Add explicit validation/verification checkpoints to the checklist, e.g. a 'verify size < 15MB in the Xcode size report before proceeding' step with a fix-and-recheck loop, to lift workflow_clarity above 2.

Move the detailed App Clip experience and card-design spec tables into a separate reference file (e.g. references/card-design.md) and link to it from a concise overview, improving progressive_disclosure toward a one-level-deep structure.

DimensionReasoningScore

Conciseness

The ~155-line body is mostly factual spec rather than padded prose, but it retains content Claude largely already knows (an exhaustive enumeration of App Clip surfaces, trade-off tables, ASO-implication prose) and editorial filler ('This forces you to ship only the essential experience'), matching the score-2 anchor of being mostly efficient but could be tightened. It is not a 3 because not every token earns its place, and not a 1 because it avoids tutorial-style concept explanation.

2 / 3

Actionability

It provides executable Swift code (SKOverlay.AppClipConfiguration), a concrete URL scheme, exact character/pixel limits (18 chars, 13 chars, 3000x2000px), named App Store Connect paths, and a copy-ready checklist, matching the score-3 anchor of fully executable, copy-paste-ready guidance. It is not a 2 because the code and specs are concrete and complete, not pseudocode.

3 / 3

Workflow Clarity

The implementation checklist sequences Setup → UX → App Store Connect, but it is a flat checkbox list with no validation/verification checkpoints or fix-retry feedback loops for the risky 15MB size constraint, matching the score-2 anchor of steps present but checkpoints missing. Per the rubric, missing validation in such workflows caps the score at 2, so it cannot reach 3.

2 / 3

Progressive Disclosure

The single ~155-line SKILL.md is well-organized into headed sections with a Related Skills pointer, but there are no bundle files and detailed reference material (experience tables, card-design specs) is inlined rather than split out, matching the score-2 anchor of content that should be separate being inline. It is not a 3 because the simple-skill carve-out applies to under-50-line skills and this body is larger with no one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

90%

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 well-constructed description with strong trigger-term coverage, explicit when-guidance, and clear disambiguation from sibling skills. The only weakness is that the stated actions are generic verbs rather than distinct concrete capabilities.

DimensionReasoningScore

Specificity

It names the domain ('App Clips for app discovery and conversion') and three action verbs ('implement, optimize, or use'), but these are generic verbs rather than distinct concrete operations, matching the score-2 anchor 'Names domain and some actions, but not comprehensive'. It does not reach score 3 because it lacks multiple specific concrete actions like the 'extract text, fill forms, merge documents' example.

2 / 3

Completeness

It answers both 'what' ('implement, optimize, or use App Clips for app discovery and conversion') and 'when' with an explicit 'Use when the user mentions...' clause, matching the score-3 anchor that requires explicit triggers for both. It is not a 2 because the trigger guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

It lists a strong set of natural user terms — 'App Clip', 'app clip code', 'mini app', 'instant app', 'App Clip card', 'App Clip link', 'no download required', 'instant experience' — matching the score-3 anchor of good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (App Clips) with distinct triggers and explicitly disambiguates away from adjacent skills ('For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.'), making conflict unlikely. It is not a 2 because the disambiguation and distinct triggers remove the overlap risk noted at that level.

3 / 3

Total

11

/

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.