axiom-media

Use when working with camera, photos, audio, haptics, ShazamKit, on-device music analysis, face grouping and video highlights, screen recording, casting to non-AirPlay routes, SharePlay playback, the user's Apple Music library, lock-screen metadata, or CarPlay app design, templates, and navigation. Covers AVCaptureSession, AVFoundation, Core Haptics, MediaPlayer, MusicKit, NowPlaying, ScreenCaptureKit, DockKit.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

An excellent router body: symptom-to-reference mapping is concrete and unambiguous, cross-domain routing rules are decisive, and the Anti-Rationalization table packs real trap knowledge. It loses points for encoding the same routing map in four redundant forms and for referencing ~25 skill files that are absent from this bundle, leaving the navigation structure unverifiable.

Suggestions

Collapse the redundancy: the dot decision tree, the numbered Decision Tree list, and the Example Invocations all restate the Quick Reference table's mapping — keep the table plus one routing form and trim the rest.

Make reference paths match the bundle layout: the body points to skills/*.md but the bundle ships no such directory; either include those files (e.g., under references/) or use paths that resolve from SKILL.md's location.

Consolidate the scattered OS-version gates (OS27, iOS 26, iPhone 17, macOS 12.3+) into a single availability table so version notes stop being repeated inline across rows.

Dimension	Reasoning	Score
Conciseness	The routing map is encoded four times — Quick Reference table, dot decision tree, numbered Decision Tree list, and Example Invocations — so at least one full section is redundant; dense version markers ("OS27", "iOS 26", "iPhone 17", "macOS 12.3+") throughout also add tokens that could be consolidated. Mostly efficient high-value content (the Anti-Rationalization table earns every token), but it could be tightened, fitting the middle anchor.	3 / 5
Actionability	As an instruction-only router, the guidance is fully executable: every symptom maps to a specific file and pattern ("camera-capture.md (Pattern 8, deferred start)"), cross-domain rules are decisive ("stay here" vs "invoke axiom-integration"), and the Anti-Rationalization table cites exact APIs (SHManagedSession, AVDelegatingPlaybackCoordinator.hostClockTime, persistentID) — the analog of copy-paste-ready guidance for a router skill.	5 / 5
Workflow Clarity	The single routing action is unambiguous: a decision tree, a numbered decision list, and stay-here/invoke-X cross-domain rules leave no doubt which reference to open for any media task, and the inline fallback note handles the non-Claude-Code case. No destructive or batch operations exist, so no validation cap applies.	5 / 5
Progressive Disclosure	The body follows the ideal one-level-deep index pattern ("See skills/..." per symptom, clearly signaled), but none of the ~25 referenced files exist in this bundle — there is no skills/, references/, scripts/, or assets/ directory alongside SKILL.md — so every reference path dangles relative to the actual bundle structure and navigation cannot be verified.	3 / 5
	Total	16 / 20 Passed

Description

83%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 router-style description: an explicit 'Use when' trigger list covering the full media domain plus a 'Covers' statement naming the frameworks in scope. Its main weakness is generic verbs and a few missing colloquial trigger phrases, which keep specificity and trigger-term quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	The description names many specific feature-level capabilities ("on-device music analysis", "face grouping and video highlights", "casting to non-AirPlay routes", "lock-screen metadata") plus concrete frameworks (AVCaptureSession, ScreenCaptureKit, DockKit), but the verbs are generic ("working with", "Covers") rather than concrete actions, so it sits between the 3 and 5 anchors.	4 / 5
Completeness	It explicitly answers both questions: "Use when working with [long list of concrete trigger domains]" for when, and "Covers AVCaptureSession, AVFoundation, Core Haptics, MediaPlayer, MusicKit, NowPlaying, ScreenCaptureKit, DockKit" for what, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage ("camera", "photos", "haptics", "screen recording", "SharePlay playback", "the user's Apple Music library", "CarPlay") with framework names as anchors, but a few natural phrases users would say are missing (e.g., "identify songs"/"song recognition", "video playback", "microphone").	4 / 5
Distinctiveness Conflict Risk	The Apple-media niche is made distinct by framework names (ShazamKit, CarPlay, SharePlay, DockKit), but the leading generic terms "camera, photos, audio" carry minor overlap risk with non-Apple or sibling media skills, fitting the 'mostly distinct; minor overlap' anchor rather than the minimal-conflict anchor.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CharlesWiltgen/Axiom
Path: .claude-plugin/plugins/axiom/skills/axiom-media/SKILL.md
Commit: c297598

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.