CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-macos

Use when building ANY macOS app — windows, menus, sandboxing, distribution, AppKit bridging or modernization (control events, state restoration, concentric corners), or macOS-specific SwiftUI patterns.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

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.

A well-structured, token-efficient routing skill that clearly dispatches by symptom to one-level-deep references and disambiguates overlapping suites via conflict-resolution rules. Scoring is held back slightly by a few un-pathed cross-suite routes and referenced bundle files that are absent from the provided bundle.

Suggestions

Add concrete paths for cross-suite routes (e.g., 'See axiom-swiftui (skills/nav.md)' consistently, as is done for some entries) so every route resolves to a file.

Ensure the referenced skills/*.md bundle files (windows.md, menus-and-commands.md, swiftui-differences.md, etc.) are actually shipped with the skill so the signaled references resolve.

Consider a one-line 'how to use this skill' note above the Quick Reference so the routing workflow is explicit rather than implied by the table.

DimensionReasoningScore

Conciseness

Lean routing overview with a symptom→reference table and a compact DOT decision tree; it assumes Claude's knowledge of macOS/SwiftUI and contains no concept-explanation padding.

5 / 5

Actionability

Concrete navigation guidance via the Quick Reference table and decision tree ('See skills/windows.md'), but some cross-suite routes point to 'axiom-swiftui' without a concrete path, leaving minor gaps.

4 / 5

Workflow Clarity

The routing workflow is clearly sequenced by symptom through the decision tree and table with no destructive/batch operations requiring validation; it stops short of explicit recovery/feedback handling, which is acceptable for a router.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references organized in a table and decision tree, but the referenced bundle files (skills/*.md, axiom-payments/skills/apple-pay.md) are not present in the bundle, so navigation cannot be fully verified against the actual structure.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong, specific description with an explicit 'Use when' trigger and a comprehensive, concrete enumeration of macOS capabilities. The only minor gap is a few technical terms where more colloquial synonyms would broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'windows, menus, sandboxing, distribution, AppKit bridging or modernization (control events, state restoration, concentric corners), or macOS-specific SwiftUI patterns' — with comprehensive coverage of the macOS development domain.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated macOS capability areas) and 'when' via the concrete 'Use when building ANY macOS app' trigger clause.

5 / 5

Trigger Term Quality

Natural terms like 'building ANY macOS app', 'windows', 'menus', 'sandboxing', 'distribution' map to what users would say, but some phrasing ('AppKit bridging', 'concentric corners') is technical and a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to macOS-only concerns with distinct triggers; the 'ANY macOS app' framing and macOS-specific capabilities minimize conflict with sibling suites.

5 / 5

Total

19

/

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.