CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-shipping

Use when preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect. Covers submission checklists, rejection troubleshooting, metadata requirements, privacy manifests, age ratings, export compliance.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured router skill: actionable references, a clear decision tree, and good progressive disclosure. Its main weakness is redundancy — the routing table, routing sections, decision tree, simplified list, and example invocations all restate the same dispatch information, inflating the token budget.

Suggestions

Collapse the redundant routing representations: pick either the Quick Reference table OR the Routing Logic sections as the primary dispatch, and drop or sharply trim the others to cut token cost.

Trim the Example Invocations section — it largely duplicates the Quick Reference table and Simplified decision tree; keep only a handful of representative cases.

Consider merging the graphviz Decision Tree and the Simplified numbered list into one canonical routing sequence to avoid maintaining two parallel decision artifacts.

DimensionReasoningScore

Conciseness

The same routing decisions are restated four to five times — Quick Reference table, 11 Routing Logic sections, a graphviz Decision Tree, a Simplified numbered list, and ~30 Example Invocations — so the body is mostly efficient but carries substantial redundant content that could be tightened.

2 / 3

Actionability

Gives concrete, copy-paste-ready direction throughout — specific file paths ('See skills/app-store-diag.md'), agent launches ('Launch security-privacy-scanner agent'), and slash commands ('/axiom:triage sentry') — which is appropriately actionable for a routing skill.

3 / 3

Workflow Clarity

Provides an explicit, branching decision tree plus a simplified numbered sequence that walks Claude from symptom to the correct sub-skill/agent, with clear routing branches.

3 / 3

Progressive Disclosure

Acts as a lean overview that signals one-level-deep references (specific skills/*.md files and named agents) via a Quick Reference table and per-route Reference lines, with content appropriately split into sub-skills rather than inlined.

3 / 3

Total

11

/

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 specific, uses natural trigger terms, explicitly states both capabilities and when-to-use, and carves out a distinct niche. It is concise and avoids fluff. 'ANY' is mildly emphatic but does not undermine clarity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect' — plus a coverage clause naming checklists, metadata, privacy manifests, age ratings, and export compliance.

3 / 3

Completeness

Explicitly answers both what ('Covers submission checklists, rejection troubleshooting...') and when ('Use when preparing ANY app for submission...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('submit', 'App Store rejections', 'appeals', 'App Store Connect', 'privacy manifests', 'export compliance') with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — App Store shipping/submission workflow — with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.