CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-notes

Manage Apple Notes via memo CLI: create, search, edit.

62

Quality

75%

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

Quality

Content

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

A tight, command-first reference for a simple CLI skill: every command is executable, prerequisites and limitations are stated, and non-obvious flag behavior is called out. The main weaknesses are the duplicated 'Rules' section and the absence of any safety/validation guidance around the destructive delete operation.

Suggestions

Add validation/confirmation guidance for the destructive `memo notes -d` (e.g., verify the selected note with `memo notes -s "title"` before deleting, or confirm with the user first) to lift workflow clarity.

Merge the 'Rules' section into 'When to Use'/'When NOT to Use' to remove the duplicated triggering guidance and tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean — terse command blocks with inline comments and no explanation of concepts Claude already knows — but the 'Rules' section substantially restates 'When to Use'/'When NOT to Use', a minor duplication that could be trimmed. This places it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Every section gives copy-paste-ready commands (e.g., `memo notes -a -f "Folder Name"`, `memo notes -ex`) covering the common cases, and the non-obvious `-a` bare-flag/$EDITOR behavior is explicitly clarified. This matches the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

Each operation is a single unambiguous command, but the destructive `memo notes -d` has no validation or confirmation guidance, and per the rubric guideline missing validation in destructive operations caps workflow clarity at 3 even for simple skills. It is not a 2 because the command sequences that exist are clear and complete.

3 / 5

Progressive Disclosure

This is a single-file skill (~80 body lines) with no bundle files; all content genuinely belongs inline and is organized into clearly titled, navigable sections (Prerequisites, When to Use / NOT to Use, Quick Reference, Limitations, Rules). Nothing needs to be split out, matching the well-organized-sections exception for simple skills.

5 / 5

Total

17

/

20

Passed

Description

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

A concise, third-person description that clearly states what the skill does with concrete verbs, but it omits any 'Use when...' trigger guidance, which is its main structural gap and caps completeness. Trigger terms are good though not exhaustive of natural synonyms. Distinctiveness is strong because the domain is narrowly and unambiguously scoped.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks to create, search, or edit Apple Notes or wants notes synced across Apple devices') to lift completeness.

Include natural trigger synonyms such as 'Notes.app', 'iCloud notes', or 'add a note to my phone' for broader keyword coverage.

Mention the additional supported actions (delete, move, export) so the description matches the body's full capability set.

DimensionReasoningScore

Specificity

"Manage Apple Notes via memo CLI: create, search, edit" names the domain and several concrete actions, matching the 'lists several specific actions; minor gaps' anchor. It is not a 5 because capabilities demonstrated in the body (delete, move, export) are absent from the description.

4 / 5

Completeness

The 'what' is clear (manage Apple Notes via memo CLI: create, search, edit) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3. Not a 4 because the 'when' is entirely absent rather than merely implicit or less specific.

3 / 5

Trigger Term Quality

"Apple Notes" plus "create, search, edit" are natural phrases a user would say, giving good keyword coverage. Not a 5 because common variations and synonyms ("Notes.app", "note", "add to notes", "iPhone notes") are missing.

4 / 5

Distinctiveness Conflict Risk

"Apple Notes via memo CLI" carves out a clear niche with distinct triggers (Apple's Notes app specifically, not Obsidian/Bear/agent memory), minimizing conflict risk with adjacent note-taking skills.

5 / 5

Total

16

/

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.

Validation — 13 / 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.