CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

photosui

API reference: PhotosUI. Query for PhotosPicker, PHLivePhotoView, photo selection.

Quality

79%

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 ./skills/photosui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 extremely lean and well-organized for a simple doc-lookup skill, with a clear output format and an unambiguous single action. The main defect is that the two referenced documentation files are missing from the bundle, breaking the skill's core navigation.

Suggestions

Add the referenced files (photosui-index.md, photospicker.md) to the bundle, e.g. under references/, so the listed navigation targets actually exist.

Replace "Search these docs" with a concrete instruction such as "Read the matching file below and answer from its contents."

Consider noting how to search (e.g. grep the files or read the index first) so the lookup method is fully executable.

DimensionReasoningScore

Conciseness

The body is 13 lines with zero padding: every line either directs the search ("Search these docs to answer questions about photo picker APIs"), defines the output format, or maps a file to its topic. It assumes Claude's competence and explains nothing Claude already knows.

5 / 5

Actionability

Concrete guidance is present: a file-to-topic mapping ("photosui-index.md - Framework overview, Live Photo views", "photospicker.md - SwiftUI PhotosPicker") plus a defined return format (Summary + File paths). Not 5 because "Search these docs" gives no concrete search method or command, leaving a minor gap for an instruction-only skill.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and the action is unambiguous: consult the matching doc file, then answer with a concise summary plus file paths. The simple-skill exception applies, and there are no destructive or batch operations requiring validation checkpoints.

5 / 5

Progressive Disclosure

The two-file index with one-line descriptions is well-signaled, one-level-deep navigation, but the referenced files (photosui-index.md, photospicker.md) are absent from the bundle — no references/ directory exists — so the navigation points to files that do not exist. Good structure, but the broken references keep it below 4.

3 / 5

Total

17

/

20

Passed

Description

65%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 names a distinct, well-scoped domain with strong API-specific trigger terms, but provides no explicit "Use when" trigger guidance and relies on a single generic action verb. Explicit usage triggers and fuller action coverage are the main gaps.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about PhotosPicker, PHLivePhotoView, or photo selection in SwiftUI/UIKit apps."

Replace the single generic verb "Query for" with concrete actions, e.g. "Look up PhotosUI APIs and symbols, and identify the relevant doc files for photo selection questions."

Include natural synonym variations such as "photo picker" and "Live Photo" alongside the API symbol names.

DimensionReasoningScore

Specificity

"API reference: PhotosUI" names the domain and "PhotosPicker, PHLivePhotoView, photo selection" name concrete subjects, but the only action verb is the generic "Query for". It fits anchor 3 (domain plus 1-2 concrete items, not comprehensive) rather than 4, which requires several specific listed actions.

3 / 5

Completeness

The "what" is clear (an API reference for PhotosUI covering photo selection), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"PhotosPicker", "PHLivePhotoView", and "photo selection" are terms users asking about these Apple APIs would naturally say. Not 5 because common variations such as "photo picker", "Live Photo", and "SwiftUI" are missing.

4 / 5

Distinctiveness Conflict Risk

PhotosUI is a specific Apple framework and "PhotosPicker"/"PHLivePhotoView" are symbols unique to it, giving a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/photosui/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.