apple-noteslisted

Read, search, write Apple Notes on macOS and extract their images. Enforces an inbox/ready/done/docs layout per project. Use when the user references Apple Notes, "check my notes", "pull bug reports from Notes", or extract screenshots.
silvio-l/skills · ★ 0 · Data & Documents · score 70

Install: claude install-skill silvio-l/skills

# Apple Notes One dispatcher: `scripts/apple-notes <subcommand>`. AppleScript under the hood. Output is plain text by default, `--json` available where useful. ## Project layout (enforced by `init`, scanned by all reads) ``` Firma/ ← company folder (configurable; default "Firma" in iCloud) HellerIO/ ← one subfolder per app/repo inbox/ ← new, untriaged ready/ ← triaged, ready for work done/ ← merged / shipped docs/ ← templates, briefing, specs — NOT issues Whispaste/ inbox/ ready/ done/ docs/ ``` **Title-prefix convention** (the only requirement, surfaced by `triage`): `BUG:` `FEAT:` `IDEA:` `FB:` (user feedback) `TECH:` (tech debt / refactor). **Body**: free-form text. Non-technical partners write plain prose using the BUG / FEAT / IDEA / FB templates seeded under `docs/`. Only the TECH template (Silvio's own notes) carries a compact `·`-separated metadata first line — agents and `triage` do not require it for any other prefix. ## What each folder means → which one to read Pick the folder by **intent**. Crucial: a bare `notes <project>` lists *every* status, and `search` spans *every* project + status — so neither answers "what's new". Both will surface long-done and ready items as if they were fresh. This is the #1 mistake: do not answer an "incoming" question from `search` or an unscoped `notes`. | Folder | Meaning | Read it whe