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.
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 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
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured reference card for the `memo` CLI tool with clear section organization and concrete commands. Its main weaknesses are the lack of non-interactive usage examples (critical for Claude's automation use case), some redundancy between sections, and missing error handling or validation guidance for operations that depend on macOS permissions and interactive prompts.
Suggestions
Add examples showing how to create notes non-interactively with body content (e.g., piping text or using flags), since Claude cannot interact with terminal prompts
Remove the redundant 'Notes' section by merging its content into 'Setup' and 'Limitations'
Add error handling guidance: what happens when permissions aren't granted, when a note with attachments is targeted for edit, or when a folder doesn't exist
| 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 slightly verbose for what Claude can infer. | 2 / 3 |
Actionability | Provides concrete CLI commands for each operation, which is good. However, the commands that rely on interactive prompts (-a, -e, -d, -m, -ex) lack guidance on how to handle those prompts programmatically or what to expect, and there are no examples of actual input/output. The skill doesn't show how to non-interactively create a note with body content, which is a key gap for automation. | 2 / 3 |
Workflow Clarity | Each operation is listed clearly as a single step, but there's no sequencing for multi-step workflows (e.g., create a folder then move a note into it), no error handling guidance, and no validation steps. For a CLI tool that requires macOS permissions and interactive prompts, missing guidance on what happens when permissions aren't granted or prompts fail is a notable gap. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no bundle files, the content is well-organized into clear sections (Setup, View, Create, Edit, Delete, Move, Export, Limitations, Notes). The structure is easy to scan and navigate. | 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 | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.