CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-iap

Use when the user mentions in-app purchase review, IAP audit, StoreKit issues, purchase bugs, transaction problems, or subscription management.

62

Quality

72%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%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 thorough, highly actionable audit prompt with strong sequencing and validation, but it is a long monolithic file that does not split detailed reference material into bundle files, and some explanatory passages could be trimmed.

Suggestions

Move the 13 detection-pattern definitions and/or the Phase 3 completeness table into references/ files, keeping SKILL.md as a phase-by-phase overview that points to them.

Tighten the narrative 'Why it matters' cells and the Pattern 13 Issue paragraph to their core failure mode and impact.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude knows StoreKit APIs, but several narrative passages could be tightened — e.g. the Phase 3 'Why it matters' user-visible-bug stories and the Pattern 13 Issue paragraph run long.

3 / 5

Actionability

Highly executable: exact grep patterns per pattern, copy-paste Swift fix snippets (e.g. the `paymentQueue(_:shouldAddStorePayment:)` extension), and concrete search strings cover the common cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit validation checkpoints — 'use Read to verify surrounding context before reporting', 'Require evidence from the Phase 1 map — don't speculate', the False Positives section, and the Phase 5 health-score gating — satisfying the batch-operation validation requirement.

5 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets are empty) and the ~300-line SKILL.md inlines detailed reference material (the 13 detection patterns and Phase 3 table) that could live in separate files; internal headers are clean but it is effectively a monolithic wall.

3 / 5

Total

16

/

20

Passed

Description

67%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 trigger-forward description with excellent natural keyword coverage and a strong, distinctive niche, but it lacks an explicit statement of what the skill does, leaving the 'what' only implied.

Suggestions

Add a leading 'what' clause before the 'Use when' trigger, e.g. 'Audits in-app purchase implementations for revenue-loss, rejection, and security issues. Use when the user mentions...'.

Surface 1-2 concrete actions (detect, verify, report) to lift specificity above the trigger-only framing.

DimensionReasoningScore

Specificity

The description names the domain richly ('in-app purchase', 'IAP audit', 'StoreKit', 'subscription management') but states no concrete action the skill performs — it is purely a trigger clause with no verb describing what the skill does.

2 / 5

Completeness

It has a clear explicit 'when' ('Use when the user mentions...') but no separate 'what' clause — the skill's action is only weakly implied via trigger nouns like 'IAP audit'/'review', falling between the 'when-only' anchor (2) and the 'both present' anchor (4).

3 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and abbreviations users actually say: 'in-app purchase review', 'IAP audit', 'StoreKit issues', 'purchase bugs', 'transaction problems', 'subscription management'.

5 / 5

Distinctiveness Conflict Risk

A clear niche (in-app purchases / StoreKit) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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.

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.