CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-location

Use when implementing location services, maps, geofencing, or debugging location/MapKit issues. Covers Core Location, CLMonitor, MapKit, annotations, directions.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/plugins/axiom/skills/axiom-location/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is a well-organized, concise router skill with strong navigation and conflict-resolution guidance, but it defers nearly all executable content to bundle files that do not exist, undermining both actionability and the progressive-disclosure promise.

Suggestions

Ship the referenced bundle files (skills/core-location.md, skills/core-location-ref.md, skills/core-location-diag.md, skills/mapkit.md, skills/mapkit-ref.md, skills/mapkit-diag.md) so the progressive-disclosure links resolve.

Add a minimal inline executable snippet or two (e.g. a CLMonitor condition example) so the skill is actionable even before a bundle file is opened.

Add explicit validation/retry checkpoints in the diagnostic routing (e.g. 'after fixing, re-confirm updates arrive') to lift the diagnostic workflow above an implicit sequence.

DimensionReasoningScore

Conciseness

Lean overview that assumes Claude's competence; no padding or explanations of basic concepts, and each section earns its place as navigation rather than restating known knowledge.

5 / 5

Actionability

Guidance is concrete in routing (symptom → file, decision tree, example invocations) but contains no executable code or commands itself; all actionable detail is deferred to bundle files that are not present in the bundle.

3 / 5

Workflow Clarity

Clear decision tree and numbered routing sequence with conflict-resolution priority (e.g. 'Try location FIRST'), though explicit validation checkpoints for diagnosing broken location are implied rather than stated as fix→retry loops.

4 / 5

Progressive Disclosure

Structure and one-level-deep references are well designed, but every referenced bundle path (skills/core-location.md, skills/mapkit.md, etc.) is absent from the actual bundle, so the progressive disclosure is not realizable as shipped.

2 / 5

Total

14

/

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.

The description is explicit, third-person, and clearly answers both 'what' and 'when' with concrete domain-specific triggers and named Apple frameworks. It is near the top of the rubric with only minor synonym coverage gaps.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('location services, maps, geofencing', 'Core Location, CLMonitor, MapKit, annotations, directions') with minor gaps in coverage such as no mention of background location or privacy.

4 / 5

Completeness

Explicitly answers both what ('Covers Core Location, CLMonitor, MapKit, annotations, directions') and when ('Use when implementing location services, maps, geofencing, or debugging location/MapKit issues') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ('location services', 'maps', 'geofencing', 'MapKit') a user would actually say, but a few common synonyms or phrasings (e.g. 'GPS', 'pins on a map') are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to location/MapKit domain with specific named frameworks (Core Location, CLMonitor, MapKit); minimal conflict risk with unrelated skills.

5 / 5

Total

18

/

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.