apple-reminders
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates specific capabilities with concrete actions and a clear technical scope around the remindctl CLI tool. However, it lacks explicit trigger guidance ('Use when...') and misses natural language terms users might say when needing reminder management, which could reduce discoverability.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to manage Apple Reminders, create todos, or work with their reminder lists'
Include natural user terms like 'todo', 'tasks', 'remind me', 'reminder app', 'macOS reminders' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list, add, edit, complete, delete' and additional capabilities like 'lists, date filters, and JSON/plain output'. | 3 / 3 |
Completeness | Clearly answers 'what' (manage reminders via CLI with specific operations), but lacks an explicit 'Use when...' clause to guide Claude on when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Apple Reminders' and 'remindctl CLI' which are relevant, but missing natural user terms like 'todo', 'tasks', 'remind me', or 'reminder app' that users would actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting 'Apple Reminders' and the specific 'remindctl CLI' tool - unlikely to conflict with other skills due to the precise tool and platform naming. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices: it's concise, provides executable commands, clearly delineates when to use vs. not use the tool, and includes a practical disambiguation example. The structure allows Claude to quickly find the right command without wading through unnecessary explanation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands directly without explaining what reminders are or how CLI tools work. Every section serves a purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands for all operations. Examples cover the full workflow from viewing to creating to completing reminders with concrete syntax. | 3 / 3 |
Workflow Clarity | For a CLI reference skill, the workflow is appropriately clear. Setup steps are sequenced, and the 'When to Use' section provides excellent decision-tree guidance. The clarification example demonstrates a validation checkpoint for ambiguous requests. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Setup, View, Manage, Create, etc.) with clear headers. For a focused CLI skill under 100 lines, no external file references are needed and the structure enables quick scanning. | 3 / 3 |
Total | 12 / 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 | |
- 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.