Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
79
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apple-reminders/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly naming the tool, platform, and concrete operations supported. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing natural user-facing trigger terms (e.g., 'to-do', 'tasks', 'set a reminder') that would help Claude match this skill to typical user requests.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to manage, create, or check reminders on macOS, or mentions Apple Reminders or the remindctl tool.'
Include natural trigger terms users would say, such as 'to-do', 'tasks', 'set a reminder', 'reminder list', or 'check my reminders' to improve matching beyond the CLI tool name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: list, add, edit, complete, delete. Also mentions specific features like lists, date filters, and JSON/plain output. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and features, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'Apple Reminders', 'remindctl', 'macOS', and action verbs, but misses natural user phrases like 'to-do', 'tasks', 'reminder app', or 'set a reminder'. Users are more likely to say 'reminders' generically than mention the CLI tool name. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: specifically targets Apple Reminders via the `remindctl` CLI on macOS. Unlikely to conflict with other skills due to the specific tool name, platform, and domain. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted CLI reference skill that is concise, highly actionable, and well-organized. Every section provides exact commands with real arguments, making it immediately useful. The only weakness is the lack of explicit workflow sequencing for multi-step operations (e.g., setup flow or verifying actions succeeded), though this is a minor issue for a primarily reference-oriented skill.
Suggestions
Consider adding a brief setup workflow sequence (install → authorize → verify with `remindctl status`) to make the onboarding path explicit.
Add a note about verifying operations (e.g., after `remindctl add`, use `remindctl today` to confirm) for robustness in scripted workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is a concrete command or essential context. No unnecessary explanations of what Reminders are or how CLIs work. The skill assumes Claude's competence and keeps every token purposeful. | 3 / 3 |
Actionability | Every section provides exact, copy-paste-ready CLI commands with specific flags and arguments. The full range of operations (CRUD, filtering, output formats) is covered with concrete examples. | 3 / 3 |
Workflow Clarity | Individual commands are clear, but there's no explicit multi-step workflow with validation checkpoints. For example, there's no guidance on verifying a reminder was created successfully, or a workflow for bulk operations with error checking. The setup flow (install → authorize → check status) is implied but not sequenced explicitly. | 2 / 3 |
Progressive Disclosure | For a single-purpose CLI reference skill under 50 lines with no need for external references, the content is well-organized into logical sections with clear headers. The flat structure is appropriate for the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
ec8d4f8
Table of Contents
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.