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

Blog Docs Log inGet started

apple-reminders

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

Quality

77%

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%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 whose commands are executable and well-organized. Its gaps are the missing validation checkpoints around destructive delete operations and a non-operational migration note that wastes tokens.

Suggestions

Add a validation step before destructive operations, e.g. view reminders/list contents first and confirm with the user before running `--delete` or `--force`.

Remove or relocate the "PilotDeck Migration Note" section — it is review metadata, not operational guidance.

Document how reminder IDs are obtained (e.g. note that IDs come from the output of `remindctl today`) before using them in `complete`/`delete` commands.

Dimension	Reasoning	Score
Conciseness	The body is lean — command blocks with inline comments, no over-explanation of concepts Claude knows — but the "PilotDeck Migration Note" section is non-operational review metadata that could be trimmed, matching anchor 4 rather than 5.	4 / 5
Actionability	Every section provides copy-paste-ready commands with concrete flags and examples (viewing, list management, creating, completing, deleting, output formats), covering the common cases fully.	5 / 5
Workflow Clarity	Setup, viewing, and management sections are clearly sequenced, but destructive operations ("remindctl delete 4A83 --force", "remindctl list Work --delete") have no validation or verification steps; the rubric caps workflow clarity at 3 for destructive operations without validation.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; ~100 lines of well-sectioned CLI reference are appropriately inline with clear headers (When to Use, Commands, Date Formats, Examples), making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

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

A concise, specific, third-person description that clearly states what the skill does and names a distinct niche. Its main weakness is the absence of any "Use when..." trigger guidance, which caps completeness.

Suggestions

Append a trigger clause, e.g. "Use when the user mentions Apple Reminders, to-dos, or wants tasks synced to their iPhone/iPad Reminders app."

Add natural synonyms users would say ("to-dos", "tasks", "Reminders app", "iOS") to improve trigger term coverage.

Consider mentioning output formats (JSON/TSV) or scoping to macOS only to sharpen capability claims.

Dimension	Reasoning	Score
Specificity	The description lists five concrete CRUD actions ("List, add, edit, complete, or delete") plus management of "reminder lists", comprehensively covering the tool's capabilities.	5 / 5
Completeness	The "what" is clear (specific actions via remindctl), but there is no "Use when..." clause or equivalent trigger guidance; the rubric guideline caps completeness at 3 for a missing explicit trigger clause.	3 / 5
Trigger Term Quality	"Apple Reminders" and "reminder lists" are natural phrases users would say, but common synonyms like "to-do", "task", "Reminders app", or "iOS" are missing, so coverage falls short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Apple Reminders" plus the named tool (remindctl) carves a clear niche distinct from generic task/todo or calendar skills, with minimal conflict risk.	5 / 5
	Total	17 / 20 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: 66bfd09

Reviewed: 2 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.