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.

79

Quality

100%

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

100%

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/index skill that efficiently points to detail files with clear navigation, decision trees, and explicit conflict-resolution routing with diagnostic feedback loops. No bundle files are present, so references point to external suite files at one level of depth.

DimensionReasoningScore

Conciseness

A lean router skill with no concept padding; every section is a routing pointer. Minor redundancy between the Quick Reference table and the Decision Tree, but no verbosity.

3 / 3

Actionability

For an instruction/router skill the guidance is concrete and actionable: specific symptom-to-file routing, named suite references, and explicit conflict-resolution steps.

3 / 3

Workflow Clarity

Routing is clearly sequenced via the table and decision tree, and the conflict-resolution section provides an explicit diagnostic feedback loop ('start with watch-device-diag; run without debugger; if it behaves correctly the fault is the tunnel').

3 / 3

Progressive Disclosure

Clear overview index with well-signaled one-level-deep references to skills/*.md and external suites; no deep nesting and content is appropriately split out.

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.

A strong, trigger-rich description that names a clear domain and enumerates many concrete capabilities with an explicit 'Use when' clause. It leans second person ('Use when building...') but that form matches the rubric's endorsed good examples.

DimensionReasoningScore

Specificity

Lists multiple concrete watchOS capabilities ('app structure, independent apps, Watch Connectivity, Smart Stack widgets, complications, controls, RelevanceKit, background tasks, ClockKit migration') rather than vague language.

3 / 3

Completeness

Explicit 'Use when building ANY watchOS app' trigger answers 'when', and the enumerated capability list answers 'what'.

3 / 3

Trigger Term Quality

Natural terms a watchOS developer would say ('watchOS app', 'complications', 'Smart Stack widgets', 'Watch Connectivity', 'background tasks') are well covered.

3 / 3

Distinctiveness Conflict Risk

The watchOS-specific scope and capability list form a clear niche unlikely to trigger for non-watch 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.