CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tipkit

API reference: TipKit. Tip protocol, TipView, PopoverTipView, Tips.configure, inline and popover tips.

Quality

82%

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

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

A lean, well-structured reference-index skill with a clear escalation workflow and a genuinely token-efficient body. Its main weaknesses are minor: the local-search step could carry a concrete command, and the six reference files the entire skill depends on were not present in the provided bundle.

Suggestions

Add a concrete search command to step 1, e.g. `rg -i "tipview" *.md` or a grep equivalent, so the local lookup is copy-paste ready.

Verify the six referenced .md files actually ship with the skill bundle; the table links are well-organized but the files were absent next to SKILL.md in this copy, which would break the primary lookup workflow.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and assumes competence: one line of purpose ("TipKit for displaying contextual tips and feature discovery (iOS 26+)"), a table of reference files, and a three-step lookup procedure with no padding or explanation of concepts Claude already knows. It is not 4 because there are no instances of over-explanation to trim — the "(iOS 26+)" note is useful platform-availability information, not rotted time-sensitive guidance.

5 / 5

Actionability

The lookup procedure is mostly executable, including a copy-paste-ready URL mapping example ("/documentation/tipkit/tip maps to https://sosumi.ai/documentation/tipkit/tip") and a concrete file table. It is not 5 because step 1 ("Search this skill's local .md files first") lacks a concrete command and step 2 ("check the other installed Apple skills... then grep their local files") is somewhat open-ended rather than fully copy-paste ready; not 3 because the guidance is real and executable, not pseudocode.

4 / 5

Workflow Clarity

The "Fetching More Docs" section gives an unambiguous three-step escalation (local files → other installed Apple skills → sosumi.ai mirror) with a worked URL example. This is a simple single-purpose lookup skill under 50 lines with no destructive or batch operations, so no validation checkpoints are required, and the single action is unambiguous — qualifying for 5 under the simple-skill exception. Not 4 because nothing in the sequence is missing or merely implicit.

5 / 5

Progressive Disclosure

The body is a clean overview: a well-signaled table of six one-level-deep reference files plus a mirror-URL fallback, which is textbook structure. It is not 5 because the six referenced .md files (tipkit-overview.md, tip.md, tipview.md, etc.) are not present in the bundle alongside SKILL.md — the core "search these local files first" workflow cannot be verified to work as written. Not 3 because the references themselves are clearly signaled, one level deep, and nothing that belongs in separate files is inlined.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific, distinctive description that accurately enumerates the framework's key symbols with good trigger terms, but it omits any explicit "use when" trigger guidance, capping its completeness. Adding a trigger clause with natural phrases like "contextual tips" or "feature discovery" would raise both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when implementing contextual tips, onboarding hints, or feature discovery in SwiftUI/UIKit apps."

Include natural user phrases such as "contextual tips", "onboarding hints", or "feature discovery" alongside the API symbol names to broaden trigger-term coverage.

State the platform context (iOS/SwiftUI) in the description so users asking about tips in non-Apple contexts do not trigger this skill.

DimensionReasoningScore

Specificity

The description names the domain ("API reference: TipKit") and lists several specific concrete items — "Tip protocol, TipView, PopoverTipView, Tips.configure, inline and popover tips" — which is several specific items with minor gaps. It is not 5 because minor TipKit symbols are missing (e.g. TipClosure, Tips.Section) and the enumeration stops short of comprehensive; not 3 because it names far more than 1-2 concrete items.

4 / 5

Completeness

The "what" is clear — an API reference whose enumerated contents are listed — but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the what is specific and detailed rather than vague; not 4 because the when is entirely absent, not merely implicit-but-stated.

3 / 5

Trigger Term Quality

Phrases like "TipKit", "TipView", "inline and popover tips" are natural terms a user working with this framework would say, giving good keyword coverage. It is not 5 because common variations such as "contextual tips", "onboarding hints", "feature discovery", or "SwiftUI tips" are missing; not 3 because the coverage goes beyond a couple of generic keywords and includes multiple natural framework-specific terms.

4 / 5

Distinctiveness Conflict Risk

"TipKit" plus framework-specific symbols like "Tip protocol" and "PopoverTipView" carve out a clear niche with minimal conflict risk — these triggers would not naturally fire for any other skill. It is not 4 because the symbol-level terms leave essentially no overlap risk even against closely related Apple-documentation skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

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