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 CLI reference skill that covers the main operations of the `memo` tool. Its main weakness is limited actionability—many commands rely on interactive prompts without showing expected behavior or non-interactive alternatives, and there are no concrete workflow examples showing realistic usage patterns. The destructive delete operation lacks any mention of confirmation or safety checks.
Suggestions
Add concrete examples showing expected output for key commands (e.g., what `memo notes` output looks like, what the interactive selection looks like for edit/delete)
Document whether destructive operations (delete) have confirmation prompts, and add a verification step or warning
Include at least one end-to-end workflow example, such as creating a note in a specific folder or searching then editing a note
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line serves a purpose—commands are listed with minimal explanation, and there's no unnecessary elaboration on concepts Claude already knows. The 'Notes' section has minor redundancy with 'macOS-only' repeated from Setup, but overall very tight. | 3 / 3 |
Actionability | Commands are listed clearly (e.g., `memo notes -a`, `memo notes -s "query"`), but many operations rely on interactive prompts (edit, delete, move, export) without showing what the interaction looks like or how to script around them. There are no concrete end-to-end examples showing input and expected output. | 2 / 3 |
Workflow Clarity | Each operation is listed as a single command, which is fine for simple tasks, but there's no guidance on common multi-step workflows (e.g., create a folder then add a note to it, or search then edit). The delete operation is destructive but has no validation/confirmation step mentioned. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill under 50 lines, the content is well-organized with clear section headers. Each operation type has its own section, making it easy to scan and find relevant commands. No external references are needed given the scope. | 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
- attilaczudor/Test
- Commit
b3cef5f
- 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.