Name: eventkit
Rating: 62.4 (1 reviews)
Author: Prisma-Labs-Dev

Blog Docs Log inGet started

eventkit

API reference: EventKit. Query for EKEventStore, EKEvent, EKReminder, calendar access.

Quality

74%

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

Quality

Content

78%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 gives concrete return-format and file-index guidance for a simple query skill, but its progressive disclosure is undermined because none of the referenced detail files exist in the bundle. Resolving the file references would lift the structure score substantially.

Suggestions

Add the referenced files (eventkit-index.md, ekeventstore.md, ekreminder.md) to a references/ directory, or remove the file listing if the docs are supplied as fork context rather than bundle files.

Make the search/answer workflow slightly more explicit (e.g. one line on how to query the index files) to push workflow clarity to 5.

Clarify whether the listed files are bundle references or externally supplied context so the navigation contract is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a one-line purpose statement, a tight Return Format list, and a minimal Files index — assuming Claude's competence with no padded explanation, matching the score-5 anchor; it is more efficient than score 4 (no over-explanation to trim).	5 / 5
Actionability	Provides concrete, actionable guidance — an explicit Return Format (Summary + File paths) and a named file index with one-line descriptions — with only minor gaps (no explicit search method, relying on the Explore agent), fitting score 4 rather than 5 (not fully copy-paste/executable) or 3 (more concrete than pseudocode).	4 / 5
Workflow Clarity	As a simple single-purpose read-only query skill the action (search docs → return summary + file paths) is clear and unambiguous with no destructive/batch step requiring validation, landing at score 4 rather than 5 (the single-step could be slightly more explicit about sequencing) and above 3 (steps are not vague).	4 / 5
Progressive Disclosure	Structure is well-organized with a one-level-deep Files index, but every referenced file (eventkit-index.md, ekeventstore.md, ekreminder.md) is absent from the bundle (no references/ directory), so navigation is broken, fitting score 3 (structure present but references not actually usable) rather than 4 (references would need to resolve).	3 / 5
	Total	16 / 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.

The description is specific and distinct, naming concrete EventKit API entities and natural trigger terms, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Adding a trigger clause would raise it toward the top anchors.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Apple EventKit, EKEventStore, EKEvent, EKReminder, or calendar/reminders access on iOS/macOS."

Enumerate a couple of concrete actions beyond querying (e.g. creating events/reminders, requesting calendar access permissions) to push specificity toward 5.

Include common synonyms/extensions users might say ("iOS calendar", "reminders", "Apple calendar API") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the EventKit domain plus several concrete API entities ("EKEventStore, EKEvent, EKReminder, calendar access"), which lists multiple specific targets with only minor coverage gaps, matching the score-4 anchor rather than 3 (more than 1-2 concrete actions) or 5 (not fully comprehensive — no actions like create/edit/observe enumerated).	4 / 5
Completeness	Has a clear "what" (API reference / query for the listed classes) but no explicit "Use when..." trigger guidance, so per the judging guideline a missing trigger clause caps completeness at 3; it is not 4 (no "when" present at all) nor 2 (the "what" is concrete, not vague).	3 / 5
Trigger Term Quality	Includes the natural technical terms a user would say ("EventKit", "EKEventStore", "EKEvent", "EKReminder", "calendar"), giving good keyword coverage with only a few natural variations missing, fitting score 4 rather than 5 (lacks synonyms/extensions like "reminders", "iOS calendar", ".event") or 3 (more than just some relevant keywords).	4 / 5
Distinctiveness Conflict Risk	"EventKit" with its specific Apple framework class names carves a clear niche with distinct triggers and minimal conflict risk with other skills, matching the score-5 anchor; it is clearly more distinct than score 4's "minor overlap risk" case.	5 / 5
	Total	16 / 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/eventkit/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.