Name: apple-reminders
Rating: 84 (1 reviews)
Author: trpc-group

apple-reminders

Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.

1.71x

Quality

79%

Does it follow best practices?

Impact

96%

1.71x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/apple-reminders/SKILL.md

The canonical home for this skill is apple-reminders in openclaw/openclaw

Quality

Content

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

An exemplary lean, fully executable CLI reference whose only real gap is safety around destructive operations — deletion and batch completion appear with no verify-before-acting step. Adding a validation checkpoint (list, confirm IDs, then delete) would bring the content to full marks.

Suggestions

Before destructive commands, add a verification step such as running 'remindctl list <name> --json' to confirm the reminder IDs before 'delete --force'.

Show the non-destructive default for delete (without --force) and explain what --force skips, so the destructive path is an explicit choice.

For batch completion, note how to confirm the IDs map to the intended reminders (e.g., run 'remindctl today' first) before running 'complete 1 2 3'.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-dense: every section is a short code block or bullet list with inline comments, no concept explanations Claude already knows, and no padding. Each token earns its place.	5 / 5
Actionability	All guidance is copy-paste-ready executable commands covering the common cases — viewing, list management, creation, completion, deletion, and output formats — with concrete flags and example values. Nothing is pseudocode or abstract.	5 / 5
Workflow Clarity	Sections are logically ordered, but the skill includes destructive and batch operations ('remindctl delete 4A83 --force', 'remindctl complete 1 2 3') with no validation or verification steps (e.g., listing first to confirm IDs), which caps workflow clarity at 3 per the rubric guidelines. It is not 2 because a rough, coherent sequence is present throughout.	3 / 5
Progressive Disclosure	A compact single-purpose CLI skill with no bundle files and no content that warrants external references; sections are well-organized and self-contained, satisfying the simple-skill condition for a top score.	5 / 5
	Total	18 / 20 Passed

Description

71%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 specific, well-scoped description with concrete verbs and good niche naming, undermined by the complete absence of a 'when to use' clause and thin synonym coverage. Adding trigger guidance and common user phrasings would lift the two weakest dimensions.

Suggestions

Append a trigger clause such as 'Use when the user mentions Apple Reminders, to-dos, or wants tasks synced to their iPhone' to fix the missing 'when' component.

Add natural synonyms users say — 'to-dos', 'tasks', 'due dates' — to the description to broaden trigger coverage.

Briefly signal the boundary with scheduling skills (e.g., 'for Apple Reminders, not calendar events or bot alerts') to reduce overlap with cron/alert tools.

Dimension	Reasoning	Score
Specificity	The description enumerates five concrete actions ('list, add, edit, complete, delete') plus supported features ('lists, date filters, and JSON/plain output') in third-person voice, giving comprehensive coverage of the CLI's capability surface.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	Natural terms like 'Apple Reminders', 'remindctl', 'lists', and 'date filters' are present, but common user phrasings such as 'to-dos', 'tasks', and 'due dates' are missing. Not 5 because synonym coverage is incomplete; not 3 because the included keywords are the ones users would most naturally say.	4 / 5
Distinctiveness Conflict Risk	'Apple Reminders' names a clear niche with distinct triggers, but requests like 'remind me to...' could also match cron/alert scheduling skills, and the description does not disambiguate. Mostly distinct with minor overlap risk, so 4 rather than 5; clearly more distinct than the anchor-3 'somewhat specific' case.	4 / 5
	Total	16 / 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: trpc-group/trpc-agent-go
Path: openclaw/skills/apple-reminders/SKILL.md
Commit: 9bb1c42

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