Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
78
71%
Does it follow best practices?
Impact
94%
2.68xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apple-notes/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies the tool, platform, and specific actions supported. It includes an explicit 'Use when' clause with reasonable trigger scenarios. The main weakness is that trigger terms could be broader to capture more natural user phrasings, and the mention of 'OpenClaw' is an odd choice that users wouldn't naturally use.
Suggestions
Add more natural trigger term variations such as 'Notes app', 'jot down', 'write a note', or 'notebook' to improve keyword coverage.
Replace 'OpenClaw' with more generic phrasing (e.g., 'the user asks to...') since users won't naturally reference that term.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create, view, edit, delete, search, move, and export notes. Also specifies the tool (`memo` CLI) and platform (macOS). | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Apple Notes via memo CLI with specific actions listed) and 'when' (explicit 'Use when' clause specifying trigger scenarios like adding, listing, searching notes, or managing folders). | 3 / 3 |
Trigger Term Quality | Includes natural terms like 'add a note', 'list notes', 'search notes', 'manage note folders', and 'Apple Notes', but misses common variations like 'reminder', 'jot down', 'write a note', 'notebook', or 'Notes app'. The reference to 'OpenClaw' is an unusual term that wouldn't naturally appear in user queries. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific tool (`memo` CLI), a specific platform (macOS), and a specific application (Apple Notes). Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable reference for the `memo` CLI tool with clear section organization and concrete commands. Its main weaknesses are the reliance on interactive prompts without non-interactive alternatives (limiting Claude's ability to actually execute these commands in automation), some redundancy in the Notes/Limitations sections, and lack of expected output examples or error handling guidance.
Suggestions
Add non-interactive usage examples or flags (if available) so Claude can execute commands without interactive prompts, or explicitly document that all operations require interactive terminal input and how Claude should handle that limitation.
Remove the redundant 'Notes' section by merging its content into 'Setup' and 'Limitations', and eliminate the duplicate 'macOS-only' mention.
Add example output for at least `memo notes` and `memo notes -s` so Claude knows what to expect and can parse results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with clear command examples, but includes some redundant information (e.g., 'macOS-only' is stated twice, 'Notes' section largely repeats 'Setup' and 'Limitations'). The 'Interactive selection of note to edit/delete' descriptions are somewhat obvious. | 2 / 3 |
Actionability | Provides concrete CLI commands for each operation, which is good. However, all commands rely on interactive prompts (e.g., `-a`, `-e`, `-d`, `-m`) without showing how to use them non-interactively or programmatically, which limits Claude's ability to automate tasks. No examples of expected output or how to pipe/script these commands. | 2 / 3 |
Workflow Clarity | Each operation is listed clearly as a single step, but there's no sequenced workflow for common multi-step tasks (e.g., create a folder then add a note to it, or search then edit). The interactive nature of many commands is noted but no guidance on handling prompts or error recovery is provided. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI reference skill with no bundle files, the content is well-organized into logical sections (Setup, View, Create, Edit, Delete, Move, Export, Limitations). The structure is flat and easy to scan, which is appropriate for this scope. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 8 / 11 Passed | |
ec8d4f8
Table of Contents
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.