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, and the mention of 'OpenClaw' is an odd choice that users may not use.
Suggestions
Expand trigger terms to include more natural variations like 'jot down', 'write a note', 'Notes app', 'notebook', or 'save a note'.
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 skill for the `memo` CLI tool. Its main weakness is that many commands rely on interactive prompts, and the skill doesn't address how Claude should handle these in an automation context—this significantly limits actionability. Adding non-interactive alternatives or explaining how to pipe input would make this much more useful.
Suggestions
Document non-interactive usage patterns (e.g., piping note content via stdin, specifying folder and title as arguments) so Claude can actually execute these commands without interactive prompts.
Add a verification step after installation (e.g., 'Verify: `memo notes` should list existing notes') and guidance on what to do if permission prompts appear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line serves a purpose—commands are listed with minimal explanation, and Claude's intelligence is respected throughout. No unnecessary explanations of what Apple Notes is or how CLI tools work. | 3 / 3 |
Actionability | Commands are listed clearly but many are interactive (e.g., `-a`, `-e`, `-d`, `-m` open interactive prompts), which limits Claude's ability to use them programmatically. There's no guidance on non-interactive usage, piping input, or how to handle the interactive prompts from a script/automation context. | 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, the setup section lacks a verification step (e.g., 'Verify installation: `memo notes`'), and there's no guidance on error handling or what to do when permissions aren't granted. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear section headers. Each command category is its own section, making it easy to scan and find the relevant command. 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.