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 ./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 concrete trigger scenarios. The main weakness is that trigger terms could include more natural language variations users might say (e.g., 'jot down', 'Notes app') and the reference to 'OpenClaw' is non-standard.
Suggestions
Add more natural language trigger variations such as 'jot down', 'write a note', 'Notes app', or 'notebook' to improve keyword coverage.
Replace 'OpenClaw' with a more generic reference or remove it, as users are unlikely to use that term 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 listed) and 'when' (explicit 'Use when' clause with 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 an unusual term that wouldn't naturally appear in user queries. | 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 CLI reference skill that covers the main operations of the `memo` tool. Its main weaknesses are minor redundancy, reliance on interactive prompts without showing non-interactive alternatives for automation, and lack of verification steps after destructive operations like delete. The organization is clean but the actionability could be improved with concrete input/output examples.
Suggestions
Show non-interactive usage patterns where possible (e.g., piping content for note creation) to make the skill more useful for automation scenarios.
Add a verification step after destructive operations like delete (e.g., 'After deleting, confirm with `memo notes -s "title"` to verify removal').
Remove the redundant 'Notes' section at the bottom — its content is already covered in 'Setup' and 'Limitations'.
Include at least one example showing expected terminal output so Claude knows what success looks like.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — 'macOS-only' is stated twice, and the 'Notes' section at the end largely repeats information from 'Setup' and 'Limitations'. Some descriptions like 'Interactive selection of note to delete' are obvious and could be omitted. | 2 / 3 |
Actionability | Provides concrete CLI commands for each operation, which is good. However, many commands just open interactive prompts (e.g., -a, -e, -d, -m) without showing how to pass arguments non-interactively, limiting automation usefulness. No examples of expected output or complete workflows are shown. | 2 / 3 |
Workflow Clarity | Each operation is listed clearly as a single command, but there's no sequenced multi-step workflow, no validation/verification steps (e.g., confirming a note was created), and no error handling guidance. For a CLI management skill that includes delete operations, some verification guidance would be expected. | 2 / 3 |
Progressive Disclosure | For a simple, single-file CLI reference skill with no bundle files, the content is well-organized into logical sections (View, Create, Edit, Delete, Move, Export, Limitations). The structure is clean and easy to navigate without needing external references. | 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
- trpc-group/trpc-agent-go
- Commit
9f4b734
- 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.