axiom-implement-iap

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is highly actionable with executable StoreKit 2 code, a clear phased workflow, and useful checklists. Weaknesses are minor: slight redundancy between checklist and pitfalls, only one explicit validation checkpoint, and reliance on external (non-bundled) references for detail.

Suggestions

Add an explicit validate→fix→retry feedback loop for the build/test cycle (e.g., 'If products fail to load, re-check the .storekit scheme and retry') to push workflow_clarity toward 5.

Deduplicate the Implementation Checklist and Critical Pitfalls, or cross-reference one from the other, to tighten conciseness.

Provide bundled reference files (e.g., in-app-purchases.md, storekit-ref.md) inside the skill so the 'Related' pointers resolve within the bundle rather than to external skills.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward, assuming competence with phased structure, checklists, and 'CRITICAL' markers; it is not a 5 because the Implementation Checklist partially duplicates the Critical Pitfalls and a few inline comments ('App Store Requirement', 'CRITICAL: Always finish') could be trimmed.	4 / 5
Actionability	It provides a complete, copy-paste-ready StoreManager implementation plus executable purchase-UI, subscription-status, and restore snippets covering the common cases, matching the 'fully executable; copy-paste ready code; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	A clear six-phase sequence exists with an explicit validation checkpoint ('Test products load before proceeding') and an implementation checklist; it is not a 5 because there is only one explicit validate step and no error-recovery feedback loop (validate → fix → retry) for the build/test cycle.	4 / 5
Progressive Disclosure	Content is well-organized into phases with a 'Related' section signaling one-level-deep pointers to detailed patterns and API references; it is not a 5 because those pointers target external skills (axiom-integration) rather than a bundled reference set, and bulk inline code (full StoreManager, subscription handling) could be split into reference files.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is concise, third-person, and includes an explicit 'Use when' trigger with a distinct IAP/StoreKit niche. Its main weakness is modest specificity — the actions are domain-level labels rather than a comprehensive list of concrete capabilities.

Suggestions

Expand the 'what' with concrete capabilities (e.g., 'configure StoreKit products, handle transaction verification, manage subscriptions, restore purchases') to lift specificity from 3 to 4-5.

Add common synonyms/extensions like 'IAP', 'paywall', or 'purchase' to broaden trigger-term coverage toward a 5.

Dimension	Reasoning	Score
Specificity	The description names the domain plus three actions ('add in-app purchases, implement StoreKit 2, or set up subscriptions'), but these are high-level domain labels rather than granular, comprehensive actions, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor; not a 4 because the actions lack the breadth seen in 'extract text, fill forms, merge, convert images'.	3 / 5
Completeness	Both 'what' (add/implement/set up IAP) and 'when' (explicit 'Use when the user wants to...') are present; it stops short of 5 because the what and when are merged into a single clause rather than a clearly separated, fully explicit pairing with multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural terms users would say are present ('in-app purchases', 'StoreKit 2', 'subscriptions'), giving good keyword coverage; a 5 would require synonyms/extensions like 'IAP', 'paywall', 'buy', or 'subscriptions' variants that are absent.	4 / 5
Distinctiveness Conflict Risk	The phrase carves a clear niche (in-app purchases + StoreKit 2 + subscriptions) with distinct triggers and minimal overlap risk against unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 69ffef6

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.