CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a well-structured routing overview: concise high-signal knowledge, concrete file-level next-actions, an explicit triage sequence with error-path routing, and clean one-level-deep progressive disclosure via the Quick Reference table and decision tree. It assumes Claude's competence and adds only what Claude would not already know.

DimensionReasoningScore

Conciseness

The body is information-dense routing and edge-case knowledge (App Review section numbers, cert expiry durations, parity rules) that Claude would not already know; it does not pad with explanations of what Apple Pay is. Length reflects genuinely needed breadth rather than verbosity.

3 / 3

Actionability

Every symptom maps to a concrete named file (skills/apple-pay.md, skills/payments-diag.md) and named API surfaces, with a decision tree and numbered routing list giving precise next-actions; per the code-vs-instruction note, the absence of code is not penalized when the routing guidance is this concrete.

3 / 3

Workflow Clarity

The numbered 'Simplified routing' list plus decision tree give an unambiguous triage sequence, including an explicit error path ('Something not working?' -> skills/payments-diag.md) and anti-rationalization rows flagging common failure modes.

3 / 3

Progressive Disclosure

The body is a pure overview/index pointing to one-level-deep references (skills/*.md, skills/*-ref.md) via a Quick Reference table and decision tree, with references clearly signaled by symptom and no deeply nested chains.

3 / 3

Total

12

/

12

Passed

Description

100%

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 excellent: it opens with an explicit 'Use when' trigger, enumerates concrete payment surfaces and capability domains, and sharply distinguishes itself from axiom-integration via an explicit negative-scope clause. Trigger terms are natural and well-covered, and conflict risk is low.

DimensionReasoningScore

Specificity

Names concrete payment surfaces ('Apple Pay, Wallet passes, Tap to Pay, Orders in Wallet') and capability domains ('entitlements, certs, signing, App Review payment rules') — multiple specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both: the 'when' via the leading 'Use when accepting ANY real-world payment' trigger, and the 'what' via the enumerated surfaces and capability coverage.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'Apple Pay', 'Wallet passes', 'Tap to Pay', 'real-world payment', 'in-app purchase' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The explicit negative scope ('NOT in-app purchase / digital content (use axiom-integration)') carves out a clear niche and resolves the primary conflict with the sister skill.

3 / 3

Total

12

/

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.