CtrlK
BlogDocsLog inGet started
Tessl Logo

appintents

API reference: App Intents. Query for Siri, Shortcuts, Spotlight integration, exposing app functionality.

58

Quality

68%

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/appintents/SKILL.md
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.

The body is admirably lean and well-structured as an overview with clearly signaled references, but its core 'search these docs' instruction lacks a concrete retrieval method and the referenced bundle files are absent.

Suggestions

Specify how to search the docs concretely (e.g. a grep command, a tool call, or a note to read the listed .md files directly) so the action is fully executable.

Ensure the referenced files (appintents-overview.md, appintents-appintent.md, appintents-appshortcut.md) actually exist in the bundle, or note where they live.

Add a brief validation step for the answer (e.g. confirm cited file paths exist before returning them) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows; every section (Return Format, Files) earns its place.

5 / 5

Actionability

The Return Format and Files listing are concrete, but 'Search these docs' gives no specific retrieval method or executable command, leaving the core action underspecified.

3 / 5

Workflow Clarity

For this simple single-purpose skill the sequence (search docs, return summary plus file paths) is clear and the output format is unambiguous, with only minor openness in how to search.

4 / 5

Progressive Disclosure

The body is a clear overview pointing to one-level-deep references (appintents-overview/appintent/appshortcut .md), but those referenced bundle files do not actually exist in the bundle, a minor navigation gap that keeps it below 5.

4 / 5

Total

16

/

20

Passed

Description

61%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 concise and names a clear niche with strong natural trigger terms, but it omits any explicit 'when to use' guidance, which caps its completeness and holds it below the top anchors.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks about Siri, Shortcuts, Spotlight, or exposing app functionality to system services.'

Replace the generic 'exposing app functionality' with concrete actions like 'define App Intents, expose actions to Siri/Shortcuts, and register Spotlight shortcuts.'

Include common synonyms/file or API references (e.g. 'AppIntent protocol', 'App Shortcuts') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('App Intents') and several integration targets ('Query for Siri, Shortcuts, Spotlight integration'), but these are integration areas rather than concrete doable actions, and 'exposing app functionality' is generic.

3 / 5

Completeness

Clearly states the 'what' (API reference for App Intents integrations) but has no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Siri', 'Shortcuts', 'Spotlight', 'App Intents') with good coverage; a few synonyms or variation phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The App Intents / Siri / Shortcuts / Spotlight niche is mostly distinct with minor overlap risk; lack of an explicit trigger clause keeps it just short of a 5.

4 / 5

Total

14

/

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