CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-reminders

Apple Reminders via remindctl: add, list, complete.

57

Quality

67%

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

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 highly actionable and concise with excellent command coverage, but destructive operations lack explicit validation checkpoints, capping workflow clarity, and there are minor organization gaps.

Suggestions

Add an explicit confirm/verify step before destructive commands (e.g., 'Before `delete` or list `--delete`, confirm the target with the user and show what will be removed').

Consider moving the full Date Formats matrix into a reference file once the skill grows, keeping the body as an overview.

Trim the 'Tasks sync across all Apple devices via iCloud' line or fold it into Prerequisites for tighter token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and command-driven, assuming Claude's competence; the lone line 'Tasks sync across all Apple devices via iCloud' is mild context padding that could be trimmed, fitting the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Provides copy-paste-ready remindctl commands covering viewing, list management, creation, completion/deletion, output formats, and date formats — matching the 'fully executable; covers common cases' anchor.

5 / 5

Workflow Clarity

Sequences are clear via grouped command sections, but destructive/batch operations (delete list, delete reminder, complete by ID) lack explicit validation/confirm steps; per the rubric this caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Single self-contained file with well-organized, clearly headed sections and no nested references; a few sub-sections (e.g., full date-format matrix) could be split out, so it sits just below a 5.

4 / 5

Total

16

/

20

Passed

Description

58%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 states a clear what and a specific tool/app niche, but lacks an explicit "Use when..." trigger clause and richer trigger-term synonyms, which cap completeness and trigger-term quality at 3.

Suggestions

Add a "Use when..." clause naming concrete triggers (e.g., 'Use when the user mentions reminders, Reminders app, or to-dos that should sync to iPhone/iPad').

Expand trigger terms with natural synonyms such as "reminders", "to-dos", and "tasks".

Mention list management and deletion among the listed actions for fuller capability coverage.

DimensionReasoningScore

Specificity

Lists three concrete actions ("add, list, complete") for a named domain, matching the 'several specific actions; minor gaps' anchor; delete and list-management are not mentioned, keeping it below 5.

4 / 5

Completeness

The "what" is clear (Apple Reminders via remindctl: add, list, complete) but there is no "Use when..." trigger clause; per the rubric, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Apple Reminders" is a natural term a user would say, but the description omits common variations/synonyms such as "reminders", "to-dos", or "tasks", fitting the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to "Apple Reminders via remindctl" gives it a clear niche with minimal conflict risk; minor overlap remains with general task/calendar tools, so it is not a 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
Open-Curiosity/gini-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.