apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).
- License 许可
- MIT
- 最近更新
- 2026-04-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- apple-notes
- author
- YOUSEF SHTIWE
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "Notes", "Apple", "macOS", "note-taking" ], "related_skills": [ "obsidian" ] } }
- platforms
- [ "macos" ]
- description
- Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).
- prerequisites
- { "commands": [ "memo" ] }
03 SKILL.md 正文
Apple Notes
Use memo to manage Apple Notes directly from the terminal. Notes sync across all Apple devices via iCloud.
Prerequisites
- macOS with Notes.app
- Install:
brew tap antoniorodr/memo && brew install antoniorodr/memo/memo - Grant Automation access to Notes.app when prompted (System Settings → Privacy → Automation)
When to Use
- User asks to create, view, or search Apple Notes
- Saving information to Notes.app for cross-device access
- Organizing notes into folders
- Exporting notes to Markdown/HTML
When NOT to Use
- Obsidian vault management → use the
obsidianskill - Bear Notes → separate app (not supported here)
- Quick agent-only notes → use the
memorytool instead
Quick Reference
View Notes
memo notes # List all notes
memo notes -f "Folder Name" # Filter by folder
memo notes -s "query" # Search notes (fuzzy)
Create Notes
memo notes -a # Interactive editor
memo notes -a "Note Title" # Quick add with title
Edit Notes
memo notes -e # Interactive selection to edit
Delete Notes
memo notes -d # Interactive selection to delete
Move Notes
memo notes -m # Move note to folder (interactive)
Export Notes
memo notes -ex # Export to HTML/Markdown
Limitations
- Cannot edit notes containing images or attachments
- Interactive prompts require terminal access (use pty=true if needed)
- macOS only — requires Apple Notes.app
Rules
- Prefer Apple Notes when user wants cross-device sync (iPhone/iPad/Mac)
- Use the
memorytool for agent-internal notes that don't need to sync - Use the
obsidianskill for Markdown-native knowledge management
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
subagent-driven-development
Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).
requesting-code-review
Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.
plan
Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.