Name: corehaptics
Rating: 56.00000000000001 (1 reviews)
Author: Prisma-Labs-Dev

Blog Docs Log inGet started

corehaptics

API reference: Core Haptics. Query for CHHapticEngine, haptic patterns, tactile feedback.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/corehaptics/SKILL.md

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.

The body is admirably concise and well-structured as an overview that delegates detail to referenced doc files, but its actionability is limited by the absence of a search method and its progressive disclosure is undermined by referenced files that are not actually present in the bundle.

Suggestions

Add one concrete example of how to query the docs (e.g. a sample search pattern or the specific sections to check first) so the guidance is executable rather than directional.

Render the file references as markdown links (e.g. [corehaptics-index.md](corehaptics-index.md)) and ensure those files ship in the references/ bundle so navigation is verifiable.

Add a brief checkpoint for the not-found case (e.g. "If the answer is not in these docs, say so and list the closest relevant files") to round out the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: one directive sentence ("Search these docs to answer questions about haptic feedback APIs"), a tight return-format spec, and a file inventory with one-line descriptions — no padding or explanation of concepts Claude already knows, matching the score-5 anchor.	5 / 5
Actionability	It provides concrete targeting (named files with descriptions and a defined output format) but gives no search method, example query, or guidance on how to query the docs, leaving it incomplete — fitting the score-3 anchor of some concrete guidance with missing key details.	3 / 5
Workflow Clarity	As a simple single-task skill the action (search docs → return summary + file paths) is clear and the output format is specified, but there is no checkpoint for the not-found case and the search step itself is loose, placing it at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is a clean overview with a well-signaled one-level-deep ## Files section pointing to corehaptics-index.md and chhapticengine.md, but those referenced files are not present in the skill bundle and are given as plain backtick paths rather than navigable links, leaving a minor organization gap at 4.	4 / 5
	Total	16 / 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 is third-person, specific to a named framework, and uses relevant haptic keywords, but it omits any explicit "when to use" trigger guidance, which caps completeness and keeps trigger-term quality from the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Core Haptics, CHHapticEngine, haptic patterns, or tactile/vibration feedback on Apple platforms."

Include natural synonyms users actually say ("vibration", "Taptic Engine", "haptics") alongside the API class name to broaden trigger coverage.

List 1-2 more concrete actions (e.g. "build and play haptic patterns") to lift specificity from a single verb to comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Core Haptics) and one concrete action ("Query for") applied to specific objects (CHHapticEngine, haptic patterns, tactile feedback), but offers only a single verb so coverage is not comprehensive — matching the score-3 anchor rather than the multi-action score-4 anchor.	3 / 5
Completeness	It states a clear "what" (API reference for Core Haptics, query for haptic entities) but provides no "Use when..." trigger clause; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"Core Haptics", "haptic patterns", and "tactile feedback" are relevant natural terms, but common synonyms users say ("vibration", "Taptic Engine", "rumble") are absent and "CHHapticEngine" leans toward API jargon, fitting the score-3 anchor of some keywords missing variations.	3 / 5
Distinctiveness Conflict Risk	"Core Haptics" and "CHHapticEngine" denote a specific Apple framework with minimal conflict risk, but the absence of explicit trigger guidance leaves minor overlap risk with a general Apple-API or haptic skill, placing it at 4 rather than 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/corehaptics/SKILL.md
Commit: 4986260

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.