CtrlK
BlogDocsLog inGet started
Tessl Logo

reminders

Apple Reminders via rem CLI: add, list, search, update, complete, delete.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is concise, highly actionable, and well-structured for a simple CLI skill, with explicit write-verification guidance; the only minor gap is that the validation feedback loop is global rather than an explicit per-destructive-step checkpoint.

Suggestions

Make the read-back validation an explicit per-step checkpoint within the Update/Complete/Delete workflow (e.g., '3. Verify: rem show <id> -o json; if not as expected, repeat') to model a clear validate->fix->retry loop.

DimensionReasoningScore

Conciseness

The body is lean and imperative — only commands, flags, and non-obvious gotchas — with no explanation of what Reminders is or how CLIs work, so every token earns its place.

5 / 5

Actionability

It provides fully executable, copy-paste-ready rem commands covering the common cases (add with all flags, search, update, complete, delete, list management).

5 / 5

Workflow Clarity

A clear sequence exists with an explicit read-back validation rule ('Always read back after writes; do not trust exit status alone') and a find-UUID-then-mutate pattern, but the validate->fix->retry feedback loop is stated once globally rather than shown as an explicit per-step checkpoint, so it falls just short of 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is single-purpose and under 100 lines, yet it is well organized with clear section headers, meeting the simple-skill exception for a top score.

5 / 5

Total

19

/

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.

The description is specific and distinctive, clearly naming the tool and its concrete capabilities, but it lacks an explicit 'when to use this' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user wants to manage Apple Reminders, to-dos, or tasks on macOS').

Include common synonyms like 'to-do' or 'task' alongside 'reminders' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (Apple Reminders via rem CLI) and six concrete CRUD actions (add, list, search, update, complete, delete) — comprehensive, matching the multiple-specific-actions anchor rather than the minor-gaps 4.

5 / 5

Completeness

The 'what' is explicit and strong, but there is no 'Use when...' or equivalent trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

Natural terms like 'Apple Reminders' and 'reminders' are present, but common synonyms such as 'to-do' or 'task' are missing, so it lands at good-but-not-comprehensive coverage rather than 5.

4 / 5

Distinctiveness Conflict Risk

It targets a single specific Apple app and a specific CLI tool, forming a clear niche with minimal overlap risk, matching the distinct-triggers anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
Reviewed

Table of Contents

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.