apple-reminders
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
86
Quality
83%
Does it follow best practices?
Impact
96%
1.71xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 tool focus, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and natural user keywords that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to manage todos, create reminders, or interact with Apple Reminders'
Include natural user terms like 'todo', 'tasks', 'remind me', 'reminder list' that users would actually say when needing this functionality
| 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'. Clear, actionable verbs. | 3 / 3 |
Completeness | Clearly answers 'what' (manage reminders via CLI with specific operations), but lacks explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Apple Reminders' and 'remindctl CLI' which are relevant, but missing natural user phrases like 'todo', 'tasks', 'remind me', or 'reminder app' that users would actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Apple Reminders via the remindctl CLI tool. Unlikely to conflict with other skills due to the specific tool name and Apple ecosystem focus. | 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 is clean and the content respects Claude's intelligence while providing all necessary specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose, commands are shown without verbose descriptions, and Claude's intelligence is respected throughout. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands for all operations. Setup, viewing, creating, completing, and deleting reminders all have concrete examples with real command syntax. | 3 / 3 |
Workflow Clarity | For this single-purpose CLI tool, the workflow is clear: setup → use commands. The 'When to Use' vs 'When NOT to Use' sections provide excellent decision guidance, and the clarification example shows a feedback loop for ambiguous requests. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (When to Use, Setup, Commands by category, Date Formats, Example). For a skill under 50 lines with no need for external references, this structure is appropriate and easy to navigate. | 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
50ef2f3
- 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.