CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

storekit

API reference: StoreKit 2. Product, Transaction, subscriptions, StoreView, SubscriptionStoreView.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/storekit/SKILL.md
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 exemplar lean reference-index skill: concise, well-structured, with a clearly conditioned fallback workflow for fetching more documentation. The only material concern is that none of the six referenced sibling .md files exist in the bundle as reviewed, which leaves the otherwise ideal progressive-disclosure structure unverifiable at runtime.

DimensionReasoningScore

Conciseness

The body is ~19 lines with zero padding: one scoping line ("StoreKit 2 for in-app purchases and subscriptions (iOS 26+)"), a compact file index table, and a three-step fetch rule. No concepts Claude already knows are explained — every token earns its place.

5 / 5

Actionability

The fetch workflow is concrete, including a copy-paste-ready URL mapping example ("/documentation/storekit/product maps to https://sosumi.ai/documentation/storekit/product"), but "Search this skill's local .md files first" gives no explicit command (e.g., grep) and there is no worked example of consuming a reference page. This is the 'mostly executable with minor gaps' anchor rather than the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

A clear numbered escalation with explicit conditions ("If the topic is not here...", "If no installed skill has the page...") covering local files, then other installed Apple skills, then the internet mirror. This is a read-only doc lookup, so no validation checkpoint applies, and under the simple-skill exception the unambiguous single-purpose sequence scores 5.

5 / 5

Progressive Disclosure

Textbook structure: a lean SKILL.md acting as an index with a table of six clearly signaled, one-level-deep reference files plus fallback fetch instructions. Held below 5 because the referenced files (storekit-overview.md, product.md, transaction.md, subscriptioninfo.md, storeview.md, subscriptionstoreview.md) are not present in the bundle as provided, so the references cannot be verified as real files — the structure matches the 5 anchor but the navigation cannot be confirmed end-to-end.

4 / 5

Total

18

/

20

Passed

Description

65%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 specific, distinctive description that clearly names its niche and topic coverage, but it only answers "what" — it never tells Claude when to use the skill, and it omits the common user phrasings "in-app purchases"/"IAP". Adding an explicit use-when clause with those synonyms would move it into the good-example tier.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about StoreKit 2, in-app purchases, subscriptions, or Product/Transaction APIs in Swift or SwiftUI" — its absence currently caps completeness at 3.

Include the natural synonyms "in-app purchases" and "IAP" so users who never say "StoreKit" still trigger the skill.

State the action in third person (e.g., "Provides an API reference for...") rather than only listing topic names, so the capability is explicit rather than implied by "API reference:".

DimensionReasoningScore

Specificity

"API reference: StoreKit 2. Product, Transaction, subscriptions, StoreView, SubscriptionStoreView" names the domain and five concrete API topics, but contains no action verbs describing what the skill does — coverage is specific while capabilities are only implied by "API reference". It sits between the minimal-action anchor (2) and the several-specific-actions anchor (4).

3 / 5

Completeness

The "what" is clear (an API reference for StoreKit 2 covering the listed types), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the what half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

"StoreKit 2", "subscriptions", "Transaction", "Product", "StoreView", "SubscriptionStoreView" are natural terms an iOS developer would actually say. A few common synonyms are missing — most notably "in-app purchases", "IAP", and "purchases" — which keeps it below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

"StoreKit 2" carves out a clear niche with distinct triggers — anyone mentioning StoreKit, SubscriptionStoreView, or StoreKit's Transaction type means this skill. Overlap risk with a general SwiftUI skill is minimal since the StoreKit framing dominates.

5 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/storekit/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.