Name: apple-reminders
Rating: 83.2 (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

—

Does it follow best practices?

Impact

96%

1.71x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

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

The content is concise, actionable, and well-organized for a simple CLI skill, with copy-paste-ready commands and clear when-to-use guidance. The only notable gap is the absence of verification steps around its destructive and batch operations.

Suggestions

Add a verification step before destructive/batch operations (e.g., run `remindctl <view>` to confirm IDs before `complete` or `delete --force`).

Document how to recover from or confirm a destructive action (such as re-listing the list after `--delete` to verify it was removed).

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: short labeled sections of executable commands with inline comments and no conceptual padding about what reminders are.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands across view/list/create/complete/delete/output tasks with concrete examples and a clear date-format reference.	3 / 3
Workflow Clarity	Setup and commands are well sequenced, but destructive/batch operations ("complete 1 2 3", "delete 4A83 --force", list "--delete") lack verification checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	A short (under 50 lines), single-purpose skill with no external bundle files, organized into clear well-labeled sections, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	11 / 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.

The description is specific and well-scoped to Apple Reminders, naming concrete actions and clear output features. Its main weakness is the absence of an explicit 'Use when...' trigger clause and broader natural-term coverage.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers (e.g., 'Use when the user mentions reminders, Apple Reminders, to-dos with due dates, or wants tasks synced to iOS').

Include common natural variations of the trigger term ("to-do", "remind me", "tasks") alongside "Apple Reminders" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("list, add, edit, complete, delete") plus feature support ("lists, date filters, and JSON/plain output"), matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	"Apple Reminders" is a natural term users say, but common variations ("to-do", "remind me", "tasks") are missing, so it stops at 'some relevant keywords'.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to the Apple Reminders app via remindctl, a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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
Commit: 737835b

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.