CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tipkit

Implement and review Apple TipKit feature-discovery UI for iOS 17+ apps. Use when adding or auditing in-app tips, contextual help, coach marks, Tip, TipView, popoverTip, rules, events, actions, display frequency, testing overrides, reusable tip identifiers, or iOS 18+ TipGroup and CloudKit tip sync; avoid for generic SwiftUI navigation or layout outside tip presentation.

Quality

92%

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

The canonical home for this skill is dpearson2699/swift-ios-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, highly actionable skill body: executable Swift examples for every common TipKit case, explicit ordering constraints, availability gates for iOS 18+/26+ APIs, and a clean one-level split into a real reference file. The main improvement opportunities are reducing redundancy between the Common Mistakes, Review Checklist, and body sections, and adding an explicit validation step to the implementation workflow.

Suggestions

Consolidate the configure-once guidance, which currently appears in 'Configure TipKit', the 'DON'T: Configure TipKit from a view' mistake, and the Review Checklist, into a single canonical statement referenced from the other spots.

Add an explicit verification step to the implementation workflow (e.g., confirm tip eligibility/display in a SwiftUI preview or UI test using the testing overrides) with a fix-and-retry loop, which would lift workflow clarity to anchor 5.

Consider trimming the 13-entry Contents anchor list or folding it into fewer grouped headings to cut navigation overhead.

DimensionReasoningScore

Conciseness

The body is dense and actionable with little concept explanation Claude already knows, but guidance like configure-once and gate-newer-APIs is repeated across "Configure TipKit", "Common Mistakes", and the "Review Checklist", and the 13-item Contents anchor list adds length. This fits the efficient-with-minor-trimmable-instances anchor; it is not lean enough for anchor 5 given that redundancy.

4 / 5

Actionability

Every section provides copy-paste-ready, executable Swift: full `Tips.configure(_:)` app-init example, `#Rule(Self.$hasSeenList)` parameter rules, event donations, `popoverTip` placement, custom `TipViewStyle` via configuration values, and concrete built-in launch arguments with stated precedence. This matches the fully-executable anchor covering the common cases.

5 / 5

Workflow Clarity

Sequencing constraints are explicit ("Call `Tips.configure(_:)` once during app initialization, before any tip can display"; "`Tips.resetDatastore()` must run before `Tips.configure(_:)`"; testing-override precedence) and the Review Checklist acts as a checkpoint for the review task. It falls short of anchor 5 because the implementation path lacks an explicit verify-eligibility/display validation step with a feedback loop, though the absent checkpoints are only minor gaps above anchor 4.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with a navigable Contents section, and advanced material is clearly signaled through a single one-level reference (references/tipkit-patterns.md, verified to exist and to contain exactly the promised patterns: custom styles, donation-valued event rules, TipGroup sequencing, CloudKit persistence, test strategies). This matches the clear-overview/well-signaled-references anchor with no nesting or buried references.

5 / 5

Total

18

/

20

Passed

Description

95%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: it pairs a concrete what with an explicit and detailed Use-when clause, includes both natural synonyms and specific API trigger terms, and adds a negative boundary clause to prevent mis-triggering on generic SwiftUI work. The only minor gap is that the action verbs (implement, review/audit) are fewer than the most comprehensive examples.

DimensionReasoningScore

Specificity

"Implement and review" names two concrete action verbs against a clearly defined domain ("Apple TipKit feature-discovery UI for iOS 17+ apps") with an enumerated scope, matching the anchor for several specific actions with minor gaps. It falls short of anchor 5 because the verb coverage is narrower than examples that list four or more distinct concrete actions.

4 / 5

Completeness

It explicitly answers both what ("Implement and review Apple TipKit feature-discovery UI for iOS 17+ apps") and when ("Use when adding or auditing in-app tips, contextual help, coach marks...") with concrete trigger phrases, mirroring the anchor-5 example. A 4 would require a less explicit or specific 'when' clause, which is not the case here.

5 / 5

Trigger Term Quality

The description covers natural user phrasings ("in-app tips", "contextual help", "coach marks") alongside API names ("Tip", "TipView", "popoverTip", "TipGroup", "CloudKit tip sync") and process terms ("display frequency", "testing overrides", "reusable tip identifiers"), matching the comprehensive-synonyms anchor. Anchor 4 would apply only if common variations were missing, which they are not.

5 / 5

Distinctiveness Conflict Risk

TipKit is a clear niche with distinct API-level triggers, and the explicit avoid-clause ("avoid for generic SwiftUI navigation or layout outside tip presentation") further reduces overlap risk with sibling SwiftUI skills. This matches the minimal-conflict-risk anchor rather than the minor-overlap anchor 4.

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

dpearson2699/swift-ios-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.