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 ./openclaw/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 (e.g., 'jot down', 'Notes app').
Suggestions
Expand trigger terms to include more natural user phrasings like 'jot down', 'save a note', 'Notes app', or 'write a note' to improve discoverability.
| 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 users might say such as 'reminder', 'jot down', 'write a note', 'save a note', or 'Notes app'. | 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 efficient use of tokens. Its main weakness is limited actionability—many commands are interactive and the skill doesn't explain how to handle those interactions or provide complete workflow examples showing expected outputs. Adding non-interactive alternatives or example sessions would significantly improve usefulness.
Suggestions
Add example output for key commands (e.g., what `memo notes` or `memo notes -s "query"` returns) so Claude knows what to expect and can parse results.
Document any non-interactive flags or piping options for commands like edit, delete, and move, so Claude can automate these without requiring user terminal interaction.
Add a brief common workflow example, e.g., 'To create a note in a specific folder: first create the note with `memo notes -a "Title"`, then move it with `memo notes -m`'.
| 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/automate them. There are no complete workflow 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 interactive nature of many commands is mentioned but not explained, and there are no validation or error-handling steps. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.