CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-clips

Build iOS App Clips with invocation URLs, App Clip Codes, NFC, QR codes, Safari banners, Maps, Messages, target setup, App Store Connect experiences, size/capability constraints, NSUserActivity routing, SKOverlay promotion, App Group/keychain handoff, ephemeral notifications, location confirmation, and full-app migration. Use when creating App Clips or wiring App Clip invocation, experience configuration, or full-app handoff.

Quality

92%

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

The canonical home for this skill is dpearson2699/swift-ios-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured skill body: lean, highly specific guidance with explicit validation checkpoints, feedback loops, and a shipping checklist, backed by a clean three-file reference layer that is clearly signaled and correctly scoped. The only minor improvements are trimming the brief concept-restatement and HIG advice, and noting that full code examples live one level deep in the references.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, high-value specifics ("com.apple.developer.on-demand-install-capable", "APPCLIP active compilation condition", "_XCAppClipURL") with almost no padding, but the opening purpose line and the HIG-style UX advice in Common Mistakes ("Avoid marketing-only clips, ad-heavy flows, splash screens...") explain concepts Claude largely already knows and could be trimmed. Not a 5 because of those minor over-explanations; not a 3 because the bulk is efficient and irreducible.

4 / 5

Actionability

Concrete, executable guidance dominates: exact entitlement keys, the bundle-ID format "com.example.MyApp.Clip", ".onContinueUserActivity(NSUserActivityTypeBrowsingWeb)", "appclips:example.com", and "app-clip-bundle-id" banner keys. Not a 5 because full copy-paste code is deferred to reference files, leaving minor gaps inline; not a 3 because what is written is specific and executable, not pseudocode or vague hints.

4 / 5

Workflow Clarity

Setup is numbered and sequenced, and each major section ends with an explicit validation checkpoint with a retry loop ("rearchive until both pass", "repeat until the App Clip and installed full app reach the same destination"), capped by a Review Checklist with "fix failures and rerun the same gate". This matches the anchor: explicit validation steps, feedback loops for error recovery, and a checklist for a complex process.

5 / 5

Progressive Disclosure

A clear overview with three real, one-level-deep references, each well-signaled with both scope and a load condition ("Read ... when implementing invocation URL routing...", "Load it whenever any of those topics is in scope"), plus a Contents TOC; referenced files and anchors (size-limits, feasibility-review-template) all exist. Boundary-level content stays in SKILL.md while implementation detail is pushed to references — no nesting beyond one level.

5 / 5

Total

18

/

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.

A strong description: comprehensive, specific coverage of the App Clips domain with an explicit "Use when" trigger clause and natural trigger terms throughout. The only minor weakness is that parts of the capability list are topic nouns rather than concrete verb-led actions.

DimensionReasoningScore

Specificity

The description lists many specific items ("invocation URLs, App Clip Codes, NFC, QR codes, Safari banners, ... SKOverlay promotion, App Group/keychain handoff, ephemeral notifications, location confirmation, and full-app migration") with comprehensive coverage, but entries like "Maps, Messages, NFC" are topics rather than verb-led concrete actions, so it sits just below the anchor-5 action style. Not a 3 because it far exceeds 1-2 concrete actions and has no vague filler.

4 / 5

Completeness

It explicitly answers both what ("Build iOS App Clips with invocation URLs, ... and full-app migration") and when ("Use when creating App Clips or wiring App Clip invocation, experience configuration, or full-app handoff") with concrete trigger phrases, matching the anchor-5 example structure exactly. Not a 4 because the when-clause is already explicit and specific.

5 / 5

Trigger Term Quality

It comprehensively covers the natural terms a user would say for this niche — "App Clips", "App Clip Codes", "NFC", "QR codes", "Safari banners", "App Store Connect", "creating App Clips", "full-app handoff" — including the canonical Apple vocabulary users would use. Not a 4 because no commonly used natural synonym for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

"iOS App Clips" with distinct triggers like "App Clip Codes", "NSUserActivity routing", and "SKOverlay promotion" carves out a clear niche with minimal conflict risk against general iOS development skills. Not a 4 because these triggers are unambiguous and would not naturally fire a different skill.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dpearson2699/swift-ios-skills

Path

skills/app-clips/SKILL.md

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.