CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

musickit

Integrate Apple Music catalog, playback, and personal library using MusicKit. Use when requesting MusicKit authorization, searching the catalog, playing songs/albums/playlists, checking subscription status, offering subscription sheets, or managing user playlists.

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

78%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-structured, code-first overview with exemplary progressive disclosure into a single well-organized reference file. It falls short of top marks on actionability (library/playlist examples deferred out of body), conciseness (version-number target line), and workflow clarity (no authorization-denied or playback-failure recovery loop).

Suggestions

Add a brief in-body section or inline pointer for personal-library and playlist operations at the point where the description promises them, rather than deferring solely to the References section.

Trim the intro sentence that duplicates the frontmatter description, and move the 'Targets Swift 6.4 / iOS 26+' version detail into a dedicated section so it can be maintained without aging the overview.

Include a short error-recovery path for the denied-authorization case (MusicAuthorization.Status handling) and playback failures to complete the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Sections are lean (one orienting sentence plus code) with no explanation of concepts Claude already knows, but the intro ("Access the Apple Music catalog, play tracks, query personal cloud libraries, and present subscription upsells using MusicKit. Targets Swift 6.4 / iOS 26+") duplicates the description and embeds version numbers that will age. Per the time-sensitive guideline this keeps it at the 4 anchor ('efficient; minor instances that could be trimmed') rather than 5.

4 / 5

Actionability

Six complete, copy-paste-ready Swift snippets cover authorization, subscription verification, catalog search, charts, playback, and the subscription offer sheet. However "personal library" and "managing user playlists" — promised in the description — have no in-body example and are only deferred to the reference file, matching the 4 anchor ('minor gaps') rather than 5 ('specific examples cover the common cases').

4 / 5

Workflow Clarity

Sections follow a logical dependency order (permissions → subscription verification → search → playback) and the Review Checklist plus Common Mistakes ("Catch errors from player.play()" for "parental restrictions, offline status, or DRM") act as explicit checkpoints. There is no error-recovery feedback loop (e.g., what to do when authorization is denied), so it sits at the 4 anchor rather than 5; no destructive or batch operations apply, so no cap is triggered.

4 / 5

Progressive Disclosure

The ~128-line body holds core patterns while verified one-level-deep reference references/musickit-patterns.md (383 lines, well-organized with its own Contents) holds extended patterns, clearly signaled as "Extended patterns (custom playlists, Now Playing metadata, audio engine integration)". Content is appropriately split and easy to navigate via the Contents list — a match for the 5 anchor.

5 / 5

Total

17

/

20

Passed

Description

92%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 description: third-person, concrete, and explicit about both capabilities and trigger conditions, covering the full scope of the skill. The only weakness is modest synonym coverage in trigger phrasing.

DimensionReasoningScore

Specificity

The description lists six concrete actions — "requesting MusicKit authorization, searching the catalog, playing songs/albums/playlists, checking subscription status, offering subscription sheets, or managing user playlists" — which comprehensively cover every capability area of the skill. It exceeds the 4 anchor ('several specific actions; minor gaps') because nothing in the skill's scope is absent.

5 / 5

Completeness

Both questions are explicitly answered: what it does ("Integrate Apple Music catalog, playback, and personal library using MusicKit") and when to use it ("Use when requesting MusicKit authorization, searching the catalog, playing songs/albums/playlists...") with concrete trigger phrases — a direct match for the 5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Apple Music", "playing songs/albums/playlists", "subscription", "playlists", "catalog". A few natural terms users would say are missing (e.g., "stream music", "music permissions", "Now Playing"), so it fits the 4 anchor rather than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"MusicKit" and "Apple Music" establish a clear niche with distinct triggers; no other skill type would plausibly claim these triggers, matching the 5 anchor ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

thienqo/ios-skills

Path

skills/musickit/SKILL.md

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.