CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-watchos

Use when building ANY watchOS app — app structure, independent apps, Watch Connectivity, Smart Stack widgets, complications, controls, RelevanceKit, background tasks, ClockKit migration.

67

Quality

81%

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

75%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 router skill that efficiently maps symptoms to suite files and gives concrete conflict-resolution rules, assuming Claude's intelligence throughout. Its main limitations are a decision tree that duplicates the quick-reference table and references to detail files that are not bundled here.

Suggestions

Collapse the graphviz Decision Tree or the Quick Reference table into a single routing artifact to remove the redundant coverage of the same symptom-to-file mappings.

For the most common routing targets, inline a one-line actionable hint so the skill remains useful even when the referenced skills/*.md files are not present in the bundle.

Confirm the referenced detail files (skills/platform-basics.md, skills/design-for-watchos.md, etc.) ship alongside this SKILL.md, or mark cross-suite references distinctly from in-suite ones so the disclosure depth is unambiguous.

DimensionReasoningScore

Conciseness

The body is a lean routing map that assumes Claude's competence and avoids explaining basics, but the graphviz Decision Tree largely restates the Quick Reference table, a minor redundancy that could be trimmed.

4 / 5

Actionability

Provides concrete file references and explicit decision rules (e.g. 'start with watch-device-diag; run the app without the debugger attached'), giving mostly actionable routing guidance with the minor gap that no executable code or commands are present.

4 / 5

Workflow Clarity

Routing is clearly sequenced via the Decision Tree and Conflict Resolution section with concrete tie-breaking rules; no destructive or batch operations apply, so the validation cap does not bind, but there are no explicit checkpoints because the skill routes rather than executes.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references ('See skills/...md'), but the referenced detail files are not present in this bundle, so the disclosure path cannot actually be followed to completion.

4 / 5

Total

16

/

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 strong, specific trigger description that explicitly pairs a 'Use when' clause with a concrete enumeration of watchOS sub-domains and watch-only framework terms. The only weakness is that capabilities lean on topic nouns rather than verb-actions, slightly capping specificity.

DimensionReasoningScore

Specificity

Lists several concrete sub-areas (Watch Connectivity, Smart Stack widgets, complications, RelevanceKit, ClockKit migration) with comprehensive coverage, but they are mostly noun-phrase topics rather than verb-actions, leaving a minor gap below the anchor-5 example.

4 / 5

Completeness

Explicitly answers 'when' via 'Use when building ANY watchOS app' and 'what' via the concrete topic list, matching the anchor for clearly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural watchOS terms and framework names a developer would actually say (complications, Smart Stack widgets, Watch Connectivity); a few common synonyms such as 'Apple Watch' are absent, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear watchOS niche with watch-only triggers (complications, RelevanceKit, ClockKit migration) gives minimal conflict risk with non-watchOS skills.

5 / 5

Total

18

/

20

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.