CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

usernotifications

API reference: UserNotifications. Query for local/remote notifications, triggers, notification content.

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

Quality

Content

96%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 an exemplar of lean doc-search skill design: an explicit output contract and a concise annotated index with no wasted tokens. The only notable weakness is that the six referenced documentation files are not present in the bundle, so the otherwise excellent one-level reference structure cannot be verified end-to-end.

DimensionReasoningScore

Conciseness

The ~28-line body is lean with zero padding: a one-line purpose statement ("Search these docs to answer questions about notification APIs."), a minimal return format, and a terse file index. Every token earns its place and no concepts Claude already knows are explained.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: an explicit output contract (Summary + File paths) and a topic-to-file map (e.g., "`unnotificationrequest.md` - Creating notification requests") covering the common query cases. An agent knows exactly what to do, with no gaps to justify a 4.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines whose single action (search the listed docs, return a summary plus relevant file paths) is unambiguous and well organized, meeting the simple-skill exception. No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The structure is anchor-5 quality — a clear overview with well-signaled, individually annotated one-level-deep references under '## Files'. However, none of the six listed .md files exist in the bundle (no references/ directory is present), so the references do not resolve as shipped; that unresolved navigation is the gap that keeps this at 'good structure; minor organization gaps' rather than 5.

4 / 5

Total

19

/

20

Passed

Description

53%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 clearly states what the skill covers but omits any explicit 'when to use it' guidance, and its trigger vocabulary misses common natural phrases like 'push notifications' and 'notification permissions'. It identifies the UserNotifications niche distinctly enough to avoid most conflicts.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks about local or push notifications, notification triggers, or UNUserNotificationCenter APIs.'

Include natural user-facing synonyms such as 'push notifications', 'notification permissions/authorization', and 'notification center' alongside the technical terms.

Name the concrete query facets users ask about (e.g., requesting authorization, scheduling triggers, customizing title/body/badge) rather than the single generic verb 'Query'.

DimensionReasoningScore

Specificity

The description names the domain ("API reference: UserNotifications") and one concrete action ("Query for local/remote notifications, triggers, notification content"), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions, so it falls short of a 4.

3 / 5

Completeness

There is a clear 'what' ("API reference: UserNotifications. Query for local/remote notifications, triggers, notification content") but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is entirely absent rather than merely imprecise, so it cannot reach 4.

3 / 5

Trigger Term Quality

Relevant keywords are present ("local/remote notifications", "triggers", "notification content"), but common user-facing variations are missing — e.g., "push notifications", "notification permissions", "notification center". This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"UserNotifications" names a specific framework, giving a clear niche, but generic terms like "triggers" and "notifications" create minor overlap risk with other notification-related skills. This fits 'mostly distinct; minor overlap risk' — not the minimal-conflict anchor at 5.

4 / 5

Total

13

/

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/usernotifications/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.