axiom-payments

Use when accepting ANY real-world payment — Apple Pay, Wallet passes, Tap to Pay, Orders in Wallet. NOT in-app purchase / digital content (use axiom-integration). Covers entitlements, certs, signing, App Review payment rules.

Quality

77%

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 ./.claude-plugin/plugins/axiom/skills/axiom-payments/SKILL.md

Quality

Content

67%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-organized routing/index skill that clearly directs Claude to the right detailed file for each payments scenario, with strong decision-tree and anti-rationalization guidance. Its main weakness is redundancy: routing to the same files is repeated across five overlapping sections, inflating token cost without adding new information.

Suggestions

Consolidate the routing sections — pick one primary navigation aid (the Quick Reference table or the Decision Tree) and fold the others into it; the Example Invocations section largely duplicates 'When to Use' and could be cut or trimmed.

Move the Cross-Suite Routing detail (which repeats file pointers already in Quick Reference) into a single 'Related skills' callout that only lists the sibling-skill boundaries, not the intra-suite file paths again.

Verify the referenced skills/*.md files exist in the bundle or document their location; none are present under references/scripts/assets, so the one-level-deep references cannot be confirmed against actual bundle structure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient routing content, but the same ~10 target files are re-routed across five sections (Quick Reference table, Decision Tree, Simplified routing, Cross-Suite Routing, Example Invocations), creating noticeable duplication that could be consolidated.	3 / 5
Actionability	Concrete, specific routing guidance throughout — every situation maps to an explicit target file (e.g. 'See skills/apple-pay-vs-iap.md') and the numbered Simplified routing list gives unambiguous decision paths; minor gaps only.	4 / 5
Workflow Clarity	The routing workflow is clearly sequenced via the graphviz Decision Tree and the 9-step Simplified routing list with explicit branching labels; no validation checkpoints are needed for a pure routing skill, so the sequence clarity carries the score.	4 / 5
Progressive Disclosure	SKILL.md is a well-structured overview pointing one level deep to skills/*.md references signaled via tables and inline 'See' links; content is appropriately split, though the routing information is repeated across multiple sections rather than presented once with clear navigation.	4 / 5
	Total	15 / 20 Passed

Description

87%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 tight, well-targeted description that states what the skill covers, when to use it, and when to route elsewhere. It is concise, uses third-person/imperative voice, and supplies concrete trigger terms with strong distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('real-world payment') and lists several concrete capability areas — 'Apple Pay, Wallet passes, Tap to Pay, Orders in Wallet' plus 'entitlements, certs, signing, App Review payment rules' — giving broad coverage, though it enumerates areas more than discrete actions.	4 / 5
Completeness	Explicitly answers both what ('Covers entitlements, certs, signing, App Review payment rules') and when ('Use when accepting ANY real-world payment'), plus an explicit when-not ('NOT in-app purchase / digital content').	5 / 5
Trigger Term Quality	Strong natural keywords users would actually say ('Apple Pay', 'Wallet passes', 'Tap to Pay', 'in-app purchase', 'App Review') with good synonym coverage; a few natural terms (e.g. '.pkpass', 'payment sheet', 'StoreKit') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (real-world payments) with an explicit boundary disambiguator ('NOT in-app purchase / digital content (use axiom-integration)'), minimizing trigger conflict with sibling skills.	5 / 5
	Total	18 / 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: .claude-plugin/plugins/axiom/skills/axiom-payments/SKILL.md
Commit: 28c2f56

Reviewed: 4 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.