CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

axiom-implement-iap

Use when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.

Quality

81%

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

75%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-sequenced, testing-first implementation guide with concrete Swift code, a checklist, and multi-tier testing instructions. Its weaknesses are moderate: undefined helper methods leave the core code non-executable as written, there is no failure-recovery guidance at the Phase 2 checkpoint, and several sections (Mission, Scope, Invocation Examples) duplicate each other or the description.

Suggestions

Define or provide implementations for grantEntitlement(for:), updatePurchasedProducts(), and loadProducts() (or point to the referenced axiom-integration files where they exist) so the StoreManager code is copy-paste executable.

Add an explicit feedback loop at the Phase 2 checkpoint — e.g. 'If products don't load, verify the .storekit file is selected in Edit Scheme → Run → Options and product IDs match Products.storekit before proceeding'.

Remove the redundant sections: the 'Your Mission' list duplicating the phase headers, the 'Invocation Examples' duplicating the description's triggers, and the stray top note that mislabels this implementation skill as an 'audit'.

DimensionReasoningScore

Conciseness

The body contains no explanations of concepts Claude already knows and is dominated by executable phases and code, but redundant sections could be trimmed: "Your Mission" duplicates the phase headers, the Scope section restates the mission, "Invocation Examples" duplicates the description's triggers, and the stray top note ("This audit may use Bash…") mislabels an implementation skill.

4 / 5

Actionability

Concrete throughout — a full StoreManager Swift class, purchase UI code, subscription status checks, restore button, and Xcode steps for the .storekit file — but the code is not copy-paste ready: grantEntitlement(for:), updatePurchasedProducts(), and loadProducts() are called but never defined, and "Test products load before proceeding" gives no command.

4 / 5

Workflow Clarity

Phases 1–6 are strictly sequenced with a testing-first mandate, an implementation checklist, and a four-tier testing ladder, and Phase 2 includes a checkpoint ("Test products load before proceeding"), but there is no error-recovery feedback loop for when products fail to load, which keeps it below the explicit validate-fix-retry anchor.

4 / 5

Progressive Disclosure

The file is well sectioned with one-level-deep pointers to deeper material (skills/in-app-purchases.md, skills/storekit-ref.md, iap-auditor agent), but those references use a non-standard format pointing at another skill's paths rather than a local bundle, and the complete StoreManager class is inline detail that could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

78%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 concise, third-person description with an explicit trigger clause and a clear iOS IAP niche. Its main limitation is that the "what" side is only implied through the trigger verbs and doesn't reflect the skill's full scope (restore, verification, transaction handling).

DimensionReasoningScore

Specificity

Lists three concrete actions — "add in-app purchases", "implement StoreKit 2", "set up subscriptions" — but omits major capabilities the body actually covers (restore purchases, transaction verification, purchase UI), so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The "when" is explicit ("Use when the user wants to…") and the "what" is embedded in the trigger verbs, but there is no standalone capability statement enumerating what the skill does, so it falls short of the clearly-explicit-both anchor.

4 / 5

Trigger Term Quality

"in-app purchases", "StoreKit 2", and "subscriptions" are phrases users naturally say, but common synonyms like "IAP", "monetization", "premium", or "paywall" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"In-app purchases" plus "StoreKit 2" carves a clear iOS IAP implementation niche with distinct triggers and minimal overlap risk with generic payment or subscription skills.

5 / 5

Total

17

/

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

CharlesWiltgen/Axiom

Path

axiom-codex/skills/axiom-implement-iap/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.