CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

carplay

Build CarPlay-enabled apps using the CarPlay framework. Use when creating navigation, audio, communication, EV charging, parking, or food ordering apps for the car display, working with CPTemplateApplicationScene, CPInterfaceController template hierarchies, CPListTemplate, CPMapTemplate, CPNowPlayingTemplate, configuring CarPlay entitlements, or integrating with CarPlay Simulator for testing.

Quality

87%

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

75%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, actionable skill body with real entitlement keys, plist manifests, Swift snippets, a testing section, common mistakes, and a review checklist. The main gaps are minor: some non-self-contained code snippets, no error-recovery guidance, and slight duplication between the main file and the reference.

Suggestions

Make code snippets self-contained or explicitly mark elided symbols (e.g., define settingsTab, zoomOut, and origin/destination, or annotate them as placeholders) so the examples are copy-paste ready.

Add brief failure-signature guidance to Common Mistakes (e.g., what a crash from a missing entitlement key or wrong scene delegate method looks like in Xcode) to create diagnose-fix-retry feedback loops.

Deduplicate content repeated between sections (tab-bar root rule, WidgetKit boundary) and trim category detail that duplicates references/carplay-patterns.md sections to tighten token budget.

DimensionReasoningScore

Conciseness

The body is lean — dense tables, executable snippets, and no basic-concept padding — but contains redundancy: the tab-bar-as-root rule appears in both Navigation Hierarchy and Common Mistakes, and the WidgetKit/ActivityKit boundary is stated in both the scope paragraph and a DON'T section.

4 / 5

Actionability

Concrete Swift, plist, and bash guidance covers the common cases, but several snippets reference undefined symbols (settingsTab, origin/destination, zoomOut, performSearch, detailTemplate), so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

Setup (5-step project configuration), testing, and a 17-item review checklist give a clear sequence with validation checkpoints, but there are no error-recovery feedback loops (e.g., what a missing entitlement or wrong delegate method failure looks like and how to diagnose it).

4 / 5

Progressive Disclosure

A single one-level-deep reference (references/carplay-patterns.md, verified to exist) is clearly signaled at the top and in the References section, but the main file's category sections (e.g., Communication, food ordering) overlap thematically with sections in the reference file, so the split could be cleaner.

4 / 5

Total

16

/

20

Passed

Description

92%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: concrete, comprehensive, and third-person, with an explicit 'Use when' clause covering all six CarPlay app categories plus setup and testing triggers. Only minor synonym coverage is missing.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — building CarPlay apps, working with CPTemplateApplicationScene, CPInterfaceController template hierarchies, CPListTemplate, CPMapTemplate, CPNowPlayingTemplate, configuring CarPlay entitlements, and integrating with CarPlay Simulator — covering the domain comprehensively rather than with minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the what ('Build CarPlay-enabled apps using the CarPlay framework') and an explicit 'Use when…' clause with concrete trigger phrases spanning the app categories, key classes, entitlements, and simulator testing.

5 / 5

Trigger Term Quality

Natural trigger terms like 'navigation, audio, communication, EV charging, parking, or food ordering apps for the car display', 'CarPlay entitlements', and 'CarPlay Simulator' give good coverage, but a few natural user phrasings (e.g., 'car screen', 'head unit', 'Now Playing') are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (the CarPlay framework) with highly specific class-name and entitlement triggers that no closely related skill (e.g., WidgetKit or general iOS development) would claim, so conflict risk is minimal.

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