Name: apple-reminders
Rating: 60 (1 reviews)
Author: NousResearch

Blog Docs Log inGet started

apple-reminders

Apple Reminders via remindctl: add, list, complete.

Quality

71%

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

Quality

Content

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

A tight, highly actionable CLI reference that respects the reader's intelligence and covers the command surface thoroughly. The main gaps are the missing safety validation around destructive delete operations and a slightly over-inline due-vs-alarm section that could be split out.

Suggestions

Add a validation step before destructive commands, e.g. "Run `remindctl list <name>` or `remindctl today --json` to confirm the ID/list before `delete`/`--delete --force`, and confirm with the user for irreversible deletions" — this would lift workflow_clarity above the cap.

Move the extended due-vs-alarm explanation (EKCalendarItem/EKReminder docs note) into a small references/ file to tighten the main body.

Trim the restated iCloud-sync sentence in the intro, which duplicates the 'When to Use' section.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with almost no concept-explanation padding; the only trimmable bits are the "Apple's public EKReminder docs list only reminder-specific properties" aside and the Reminders.app/iCloud restatement, which is 'efficient with minor instances of over-explanation' rather than the every-token-earns-its-place level 5.	4 / 5
Actionability	Every section is copy-paste-ready `remindctl` syntax with realistic values ("Buy milk", "2026-05-15 14:00"), covering viewing, list management, creating, editing, completing, deleting, and output formats — fully executable guidance for the common cases.	5 / 5
Workflow Clarity	Sequences are unambiguous per command and there is a verify-with-JSON check after edits, but destructive operations are shown without validation — "remindctl delete 4A83 --force" and "remindctl list Work --delete" appear with no check-first or confirm-before-delete step, so the destructive-operations cap of 3 applies. Not score 2 because the per-command guidance itself is clear and rule 2 does mandate confirming content before creating.	3 / 5
Progressive Disclosure	The skill is self-contained (no references/scripts/assets bundle exists) with well-organized sections that keep everything appropriately inline for a CLI quick reference; this is 'good structure with minor organization gaps' rather than a 5, since the ~117-line body with the due-vs-alarm deep dive could plausibly live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

66%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 concrete actions in a distinct niche, but it omits any 'when to use' trigger guidance, which is its biggest weakness and caps completeness. Adding a Use-when clause with natural phrases users say would lift it substantially.

Suggestions

Append a trigger clause such as: 'Use when the user mentions reminders, the Reminders app, wants to-dos that sync to iPhone/iPad, or asks to be reminded about something personal.'

Include natural user phrasings like "remind me", "to-do", or "task" alongside "Apple Reminders" to improve trigger term coverage.

Optionally mention iCloud/iPhone sync as a differentiator from cron-based alerts and calendar skills.

Dimension	Reasoning	Score
Specificity	"add, list, complete" lists three concrete actions in the Reminders domain, but coverage has minor gaps — edit, delete, and list management from the body are absent, so it does not reach the comprehensive level 5.	4 / 5
Completeness	The 'what' is clear ("add, list, complete" via remindctl) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 4 because the 'when' is entirely absent rather than merely under-specified.	3 / 5
Trigger Term Quality	"Apple Reminders" and "add, list, complete" are natural phrases users would say, but common variations like "remind me", "to-do", "task", or "Reminders app" are missing, matching the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	"Apple Reminders via remindctl" carves a clear niche that is unlikely to trigger for calendar or generic task-management skills, but without explicit triggers there is minor overlap risk with other to-do/task skills, matching the 'mostly distinct' anchor rather than the minimal-risk level 5.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/apple/apple-reminders/SKILL.md
Commit: 68fa7e9

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.