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.

72

Quality

88%

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

77%

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

A well-structured navigation skill with clear routing logic and concrete symptom-to-file mappings, undermined mainly by repeated restatement of the same mappings and by references to skills/*.md files that are not present in the bundle.

Suggestions

Ship the referenced bundle files (skills/core-location.md, core-location-ref.md, core-location-diag.md, mapkit.md, mapkit-ref.md, mapkit-diag.md) or remove the references — progressive disclosure only works when the linked content exists.

Collapse the duplicated skill-to-topic mappings: pick one canonical routing surface (e.g. the Quick Reference table) and have the decision tree / Example Invocations point back to it instead of restating the same file list four times.

Verify the 'skills/' path prefix matches the actual bundle layout; the references use a nested skills/ path but no such directory exists in the bundle.

DimensionReasoningScore

Conciseness

The body is lean routing content with no concept-padding, but the same skills/*.md -> topic mapping is restated across the Quick Reference table, the dot decision tree, the numbered decision tree, Critical Patterns, and Example Invocations, adding tokens that do not all earn their place. Not a 3 because it could be tightened by collapsing redundant mappings.

2 / 3

Actionability

Gives concrete, specific routing — each symptom maps to an exact file (e.g. "Location updates never arrive -> skills/core-location-diag.md"), and the decision tree prescribes precise next steps. As an instruction-only skill, the absence of code is not penalized because the guidance is actionable and copy-paste-ready routing.

3 / 3

Workflow Clarity

Sequenced decision logic (domain -> Core Location or MapKit -> type -> file) is laid out in both a graphviz decision tree and a numbered list, with example invocations. No destructive/batch operations are involved, so the absence of validation checkpoints is not penalized.

3 / 3

Progressive Disclosure

The overview is well-organized into one-level-deep, clearly signaled references (main/-ref/-diag split), which would otherwise score 3, but none of the referenced files (skills/core-location*.md, skills/mapkit*.md) actually exist in the bundle, so the disclosed content cannot be navigated to. Not a 1 because the structure and signaling are genuinely sound, but not a 3 because the references do not resolve to real files.

2 / 3

Total

10

/

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 description that concisely states both what it covers and when to use it, with natural trigger terms and a clearly delineated niche. Third-person voice is used throughout with no first/second person.

DimensionReasoningScore

Specificity

Names multiple concrete capability areas — "location services, maps, geofencing", "debugging location/MapKit issues", and "Core Location, CLMonitor, MapKit, annotations, directions" — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both: what it covers ("Covers Core Location, CLMonitor, MapKit, annotations, directions") and when to use it ("Use when implementing location services, maps, geofencing, or debugging location/MapKit issues").

3 / 3

Trigger Term Quality

Uses natural terms a user would say — "location services", "maps", "geofencing", "MapKit" — with good coverage of common phrasings rather than obscure jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (location/maps) with distinct triggers unlikely to collide with unrelated skills; not a level above since the scale tops out, and not below as it is far from generic.

3 / 3

Total

12

/

12

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.