CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-docs-index

Index of Apple developer documentation for iOS, macOS, and related frameworks. Use when looking up what APIs exist in a framework, browsing available documentation, or deciding what docs to fetch. Covers SwiftUI, UIKit, Core Animation (QuartzCore), XCTest, HealthKit, Combine, SwiftData, and more.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apple-docs-index/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 concise and actionable with a well-organized overview table, but its progressive disclosure is undermined because every referenced index file is absent from the bundle. Resolving the missing files is the single highest-impact improvement.

Suggestions

Ship the referenced index files (e.g. xctest-index.md, healthkit-index.md, combine-index.md) alongside SKILL.md, or remove their rows from the table, so navigation does not dead-end.

Tighten the opening "Use these to" bullet list, which largely restates the frontmatter description, to recover token budget.

Add a one-line validation cue for the fetch workflow (e.g. confirm a returned page is non-empty / valid Markdown before using it) to lift workflow clarity.

DimensionReasoningScore

Conciseness

Lean body with no padding of concepts Claude already knows; the opening bullet list ("Browse / Find / Decide") slightly duplicates the description and "Index files list all available documentation pages" is mildly over-explanatory, keeping it just below 5.

4 / 5

Actionability

Provides copy-paste-ready commands ("cat healthkit-index.md | head -100", "grep -i 'workout' healthkit-index.md") and concrete URL patterns; not 5 because the fetch workflow mixes procedural steps and an illustrative markdown snippet rather than fully executable code throughout.

4 / 5

Workflow Clarity

Four numbered use-modes are clearly laid out, and the missing-framework path offers a fallback chain (sosumi mirror -> Apple JSON endpoint) that acts as recovery; read-only lookups need no validation checkpoints, so it stays at 4 rather than 5 for lacking explicit verification steps.

4 / 5

Progressive Disclosure

The overview table signals one-level-deep references clearly (framework -> file -> size -> topics), but none of the referenced index files (e.g. xctest-index.md, healthkit-index.md, ../swiftui/swiftui-overview.md) exist in the bundle, so navigation dead-ends in practice; this keeps it below 4 despite good signaling.

3 / 5

Total

15

/

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, well-structured description that clearly conveys both purpose and trigger conditions with concrete, natural language and a specific framework niche. The only soft spot is trigger-term synonym breadth and minor overlap risk with sibling Apple documentation skills.

DimensionReasoningScore

Specificity

Names three concrete actions — "looking up what APIs exist in a framework, browsing available documentation, or deciding what docs to fetch" — matching anchor 4 (several specific actions, minor gaps); not 5 because the actions are more abstract than mechanical operations like "extract text, fill forms".

4 / 5

Completeness

Explicitly states the what ("Index of Apple developer documentation for iOS, macOS, and related frameworks") and the when ("Use when looking up… browsing… or deciding what docs to fetch") with concrete trigger phrases, matching the anchor 5 example structure.

5 / 5

Trigger Term Quality

Natural trigger phrases ("looking up what APIs exist", "browsing available documentation") plus a broad set of framework names (SwiftUI, UIKit, HealthKit, etc.) give good keyword coverage; not 5 because "documentation" repeats without synonym/extension breadth.

4 / 5

Distinctiveness Conflict Risk

Clear Apple-developer-docs niche with distinct framework triggers; capped at 4 rather than 5 because the body explicitly references sibling "installed Apple skills," signaling minor overlap risk with closely related skills.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
Prisma-Labs-Dev/apple-skills
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.