apple-notes
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.
82
78%
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 may not use.
Suggestions
Expand trigger terms to include more natural variations like 'Notes app', 'jot down', 'write a note', 'notebook', or 'memo' to improve discoverability.
Replace 'OpenClaw' with more generic phrasing (e.g., 'the user') since users are unlikely to reference that name in their requests.
| 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) and 'when' (explicit 'Use when' clause listing trigger scenarios like adding, listing, searching notes, and 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 unusual and may not match what users naturally say. | 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
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise reference for the `memo` CLI tool with clear section organization and specific commands. Its main weakness is that many operations are interactive (edit, delete, move, export), which is problematic for an AI agent, and no non-interactive alternatives or expected output examples are provided. Adding guidance on handling interactive prompts programmatically or showing expected outputs would significantly improve actionability.
Suggestions
Address how Claude should handle interactive prompts — can flags like `memo notes -a "Title"` accept piped input or additional arguments to avoid interactive mode?
Add expected output examples for at least `memo notes` and `memo notes -s` so Claude knows what to parse and present to the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section is tightly written with just the command and a brief description. No unnecessary explanations of what Apple Notes is or how CLI tools work. The 'Notes' section at the end has minor redundancy with 'macOS-only' repeated from Setup, but overall very token-efficient. | 3 / 3 |
Actionability | Commands are concrete and specific (e.g., `memo notes -f "Folder Name"`), but many operations rely on interactive prompts (edit, delete, move, export) without showing how to use them non-interactively or what the expected output looks like. For an AI agent, interactive prompts are problematic and no workaround or scripting approach is provided. | 2 / 3 |
Workflow Clarity | This is essentially a reference card for individual commands rather than a multi-step workflow, which is appropriate for the skill's nature. However, there's no guidance on error handling (e.g., what happens if a note isn't found, if permissions aren't granted), and the interactive nature of many commands is noted as a limitation without providing a clear path forward for automation scenarios. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear section headers for each operation type. No external references are needed, and the structure allows quick scanning to find the relevant command. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- openclaw/openclaw
- Commit
b9f5d02
- 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.