CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-reminders

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

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/apple-reminders/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 body is a tight, executable command reference with strong boundary guidance, but destructive and batch operations lack validation checkpoints and the migration-note section adds noise.

Suggestions

Add a verification step before destructive/batch actions, e.g. run 'remindctl <view>' to confirm IDs before 'complete'/'delete', and confirm list deletion before '--delete'.

Remove or relocate the 'PilotDeck Migration Note' so the skill body contains only operational guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean command examples with inline comments and assumes Claude's competence, but the 'PilotDeck Migration Note' section is internal metadata padding that could be trimmed, keeping it just below 5.

4 / 5

Actionability

Commands are fully executable and copy-paste ready ('remindctl add --title "Call mom" --list Personal --due tomorrow') and cover the common cases across view, list, create, complete, delete, and output formats.

5 / 5

Workflow Clarity

A clear decision checkpoint appears in the clarifying-intent example, but destructive/batch operations like 'remindctl delete 4A83 --force' and 'remindctl complete 1 2 3' lack validation steps, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Content is well organized into clear sections (When to Use, Setup, Common Commands, Date Formats) in a self-contained file with no need for external references, but the migration-note noise and >50-line length leave minor organization gaps short of 5.

4 / 5

Total

16

/

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.

The description is specific and actionable with a clear tool name, but omits any 'Use when' trigger guidance, which caps completeness and limits its ability to be selected confidently over adjacent reminder/task skills.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user mentions Apple Reminders, the Reminders app, or wants to-dos that sync to iOS.'

Include a synonym like 'Reminders app' or 'to-dos' to improve trigger-term coverage and reduce overlap with generic task skills.

DimensionReasoningScore

Specificity

Lists five concrete actions ('List, add, edit, complete, or delete') plus reminder-list management via a named tool, giving comprehensive CRUD coverage rather than the minor gaps allowed at 4.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

'Apple Reminders' and 'reminder lists' are natural user terms and the tool is named, but common synonyms like 'Reminders app', 'to-dos', or 'tasks' are missing, so it sits above the minimal-coverage 3 anchor.

4 / 5

Distinctiveness Conflict Risk

The Apple-Reminders-specific niche plus the remindctl tool make it mostly distinct, but 'reminders' overlaps with generic task/reminder skills, leaving minor conflict risk short of the 5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
OpenBMB/PilotDeck
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.