apple-notes
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
58
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apple-notes/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly listing concrete actions and targeting a well-defined niche (Apple Notes via memo CLI on macOS). However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when requesting help with their notes.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to manage Apple Notes, asks about their notes on Mac, or mentions the Notes app.'
Include natural trigger term variations like 'Notes app', 'Notes.app', or 'Mac notes' to improve matching with how users naturally phrase requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create, view, edit, delete, search, move, and export. Also specifies the tool ('memo CLI') and platform ('macOS'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with the list of actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Apple Notes' and 'macOS' which are natural terms, but misses common variations users might say like 'notes app', 'Notes.app', or just 'notes'. The term 'memo CLI' is tool-specific jargon users wouldn't naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: Apple Notes via a specific CLI tool on macOS. Unlikely to conflict with other skills due to the specific platform, app, and tooling mentioned. | 3 / 3 |
Total | 10 / 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 all major operations clearly. Its main weakness is the lack of concrete examples showing expected output or non-interactive usage patterns, and the absence of error handling guidance for known limitations (e.g., notes with attachments). The skill would benefit from showing what interactive prompts look like and providing automation-friendly patterns.
Suggestions
Add example output for at least one command (e.g., `memo notes` listing) so Claude knows what to expect and can interpret results.
Document what happens when attempting to edit a note with images/attachments—does it error, silently fail, or strip attachments?
Show a brief multi-step workflow example, such as creating a note and then moving it to a specific folder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Each section is brief, commands are clearly listed without unnecessary explanation. The 'Notes' section slightly overlaps with 'Setup' (macOS-only repeated), but overall token usage is very efficient. | 3 / 3 |
Actionability | Commands are concrete and copy-paste ready (e.g., `memo notes -f "Folder Name"`), but the skill relies heavily on interactive prompts (edit, delete, move, export) without showing what the interaction looks like or how to script/automate these operations. No examples of expected output or non-interactive usage patterns are provided. | 2 / 3 |
Workflow Clarity | Each operation is listed clearly as a single step, but there are no multi-step workflows showing common task sequences (e.g., create a note then move it to a folder). The limitations section is helpful but there's no guidance on error handling or what happens when operations fail (e.g., trying to edit a note with attachments). | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill with no bundle files, the content is well-organized into logical sections with clear headers. The skill is under 50 lines and doesn't need external references; the flat structure is appropriate. | 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
44c1cc8
- 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.