Name: apple-reminders
Rating: 62.4 (1 reviews)
Author: OpenBMB

Blog Docs Log in Get started

apple-reminders

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Quality

73%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable command reference for a single-purpose CLI skill, weakened only by missing validation guidance around destructive delete/complete operations and a slightly long monolithic structure. Adding a pre-delete confirmation step and trimming the migration note would help.

Suggestions

Add an explicit validation checkpoint before destructive operations, e.g., list reminders and confirm IDs before `remindctl delete ... --force`.

Trim or remove the 'PilotDeck Migration Note' and stray OpenClaw references that do not aid using the skill.

Consider moving the full command/date reference into a referenced file if the skill grows, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is command-dense with terse inline comments and assumes Claude's competence (no explaining what reminders are); nearly every token earns its place, though the trailing PilotDeck migration note is minor unnecessary spend that does not drop it to the 2 anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands across view/list/create/complete/delete with concrete flags and examples (e.g., `remindctl add --title "Call mom" --list Personal --due tomorrow`), plus date and output-format references.	3 / 3
Workflow Clarity	Sections are well sequenced and the intent-clarification example is a good checkpoint, but destructive/batch operations (`delete ... --force`, `complete 1 2 3`) lack any validation step, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a single well-organized file with clear sections and no bundle files to link, but at ~100 lines it exceeds the simple-skill threshold and keeps all command reference inline with no progressive split or signaled references.	2 / 3
	Total	10 / 12 Passed

Description

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.

A specific, third-person description with concrete actions and a clear niche, but it omits explicit "Use when" trigger guidance and has only partial coverage of natural user terms. Adding a trigger clause and a few synonyms would raise completeness and trigger_term_quality.

Suggestions

Append a 'Use when...' clause (e.g., 'Use when the user mentions Apple Reminders, to-dos, or tasks that should sync to their iPhone Reminders app') to satisfy completeness.

Add natural term variations like 'to-dos' and 'tasks' alongside 'Apple Reminders' to broaden trigger coverage.

Confirm the description stays third-person (it does) when editing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("List, add, edit, complete, or delete") plus reminder-list management, matching the multi-action anchor rather than the single-domain score-2 example.	3 / 3
Completeness	It clearly states what the skill does but has no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains the natural term "Apple Reminders" and "reminder lists," but misses common variations users say ("to-dos," "tasks," "Reminders app"), so coverage is partial rather than broad.	2 / 3
Distinctiveness Conflict Risk	"Apple Reminders ... via remindctl" names a specific app and tool, carving a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: OpenBMB/PilotDeck
Path: skills/apple-reminders/SKILL.md
Commit: c88d7d1

Reviewed: about 14 hours 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.