CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-reminders

Apple Reminders via remindctl: add, list, complete.

56

Quality

66%

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/apple-reminders/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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 highly actionable with comprehensive command examples and good section structure for a simple single-purpose skill, with only minor verbosity and a missing explicit validation step for destructive batch operations.

Suggestions

Trim the EKCalendarItem/EKReminder documentation paragraph since Claude already understands EventKit concepts.

Add an explicit validation checkpoint for destructive/batch operations, e.g. list IDs with --json before running complete/delete, and confirm count.

Tighten the due-vs-alarm prose into a short bullet rule rather than a multi-paragraph explanation.

DimensionReasoningScore

Conciseness

The body is mostly lean command reference with minimal preamble, but sections like the EKCalendarItem explanation and the due-vs-alarm prose add a little over-explanation that could be trimmed.

4 / 5

Actionability

Commands are concrete, executable, and copy-paste ready across create/list/view/complete/delete/edit scenarios with specific flags and JSON output examples.

5 / 5

Workflow Clarity

The 'Rules' section sequences guidance (clarify intent, confirm content/due before creating, use --json), and the edit example includes a verify-with-JSON checkpoint, but batch/destructive operations (complete/delete by ID) lack an explicit validate-before-act feedback loop.

4 / 5

Progressive Disclosure

No bundle files are present, and this is a single-purpose skill well under the threshold; the body is cleanly sectioned (Prerequisites, When to Use, Quick Reference, Date Formats, Rules), so the simple-skill exception applies.

5 / 5

Total

18

/

20

Passed

Description

50%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 concise and tool-specific, naming a clear niche and a few concrete actions, but it lacks an explicit 'Use when' trigger clause and broader natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Apple Reminders, create to-dos that sync to iPhone/iPad, or mentions remindctl'.

Expand the action list to cover edit, delete, due dates, and alarms so capabilities read comprehensively.

Include natural user phrases like 'remind me' (with a note to clarify agent alert vs Apple Reminder) and 'to-do'.

DimensionReasoningScore

Specificity

Names the domain (Apple Reminders via remindctl) and three concrete actions (add, list, complete), but the action set is generic and omits several real capabilities (edit, delete, alarms, due dates).

3 / 5

Completeness

The 'what' is clear (manage Apple Reminders via remindctl), but there is no 'Use when...' trigger clause; a missing explicit trigger guidance caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes 'Apple Reminders', 'remindctl', and 'tasks' as keywords but misses common natural phrases users say ('remind me', 'to-do', 'reminders app') and any file/list synonyms.

3 / 5

Distinctiveness Conflict Risk

The tool-specific 'remindctl' + Apple Reminders niche is distinct from generic task skills, with only minor overlap risk against general to-do/project-management skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
NousResearch/hermes-agent
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.