CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-implement-iap

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

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./axiom-codex/skills/axiom-implement-iap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced IAP implementation guide with real StoreKit 2 code and clear phase-based workflow. Weaker on conciseness (mild section redundancy) and progressive disclosure (monolithic inline content with no internal bundle references).

Suggestions

Move the full StoreManager implementation and StoreKit API reference into reference files (e.g., references/store-manager.md, references/storekit-ref.md) and keep SKILL.md as a concise overview with one-level pointers.

Consolidate the overlapping Implementation Checklist, Critical Pitfalls, and Deliverables sections to remove redundancy.

Define the referenced-but-unshown helper methods (grantEntitlement(for:), updatePurchasedProducts()) so the code is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and uses lean phase/code/checklist structure, but the checklist, pitfalls, and deliverables sections overlap somewhat and could be tightened.

2 / 3

Actionability

Provides real, executable StoreKit 2 Swift code (StoreManager, purchase, restore, transaction listener) plus concrete Xcode steps, going well beyond pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced testing-first workflow (Phases 1–6) with explicit ordering constraints ('Create .storekit file BEFORE any Swift code', 'Test products load before proceeding') and an implementation checklist.

3 / 3

Progressive Disclosure

No bundle files are provided and the full StoreManager implementation and API snippets are inline in a ~160-line document; the only file pointers are external 'Related' references rather than well-signaled one-level bundle references.

2 / 3

Total

10

/

12

Passed

Description

82%

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 focused, concrete description with explicit 'when' triggers and natural keywords for the iOS IAP domain. Its main weakness is the absence of a standalone 'what does this do' capability statement separate from the trigger clause.

Suggestions

Lead with an explicit capability statement (e.g., 'Implements production-ready in-app purchases using StoreKit 2.') before the 'Use when...' clause so both 'what' and 'when' are clearly stated.

Add common natural trigger variations such as 'IAP', 'monetize', or 'buy button' alongside 'in-app purchases' and 'subscriptions'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('add in-app purchases, implement StoreKit 2, or set up subscriptions') rather than vague language, matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

The 'Use when...' trigger is explicit, but the 'what does this do' capability is only implied through the trigger verbs rather than stated as a standalone capability statement, so it does not fully match the score-3 two-part structure.

2 / 3

Trigger Term Quality

Includes natural terms users would actually say ('in-app purchases', 'subscriptions') alongside the domain-specific 'StoreKit 2', giving good coverage of likely trigger phrases.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (iOS in-app purchases / StoreKit 2) with distinct triggers, making it unlikely to fire for unrelated skills.

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
CharlesWiltgen/Axiom
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.