apple-notes-work-report

Audit and patch Apple Notes daily work reports against Codex session evidence.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill apple-notes-work-report-joey-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-notes-work-report
Source: https://github.com/Joey-Tools/codex-private-workflows/tree/main/.agents/skills/apple-notes-work-report
Command: npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill apple-notes-work-report-joey-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Daily work reports kept in Apple Notes can silently omit work done across multiple machines, and editing notes with AppleScript risks destroying list structure and #tag markers. This Skill audits the Work Report folder against ~/.codex history and remote-host sessions, then applies minimal, backup-protected edits that preserve the original note structure. ## Core Features & Use Cases - Evidence-based auditing: Compares note content against local ~/.codex history, remote-host rollouts, shell history, and iTerm logs to classify items as confirmed, likely omitted, or uncertain. - Tag-safe editing: Enforces two-tier backups (logical export and physical NoteStore.sqlite file-set copies) before writes, and preserves numbered lists, project grouping, and #tag markers. - Paste-ready drafting: Generates concise day-by-day English report drafts with stable project buckets like #HDR-streaming and #webex-message-archiver. - Use Case: Ask whether last week's Apple Notes daily reports missed any work; the Skill merges evidence from local and remote Codex sessions, drafts the missing buckets, and patches the notes only after a validated backup. ## Quick Start Use the apple-notes-work-report skill to check this week's Work Report notes in Apple Notes against my Codex history and draft any missing items.

Frequently Asked Questions about apple-notes-work-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Apple Notes work reports for missing items?

Export the target notes from the Work Report folder via AppleScript, then collect same-date evidence from ~/.codex history and remote-host sessions. Classify findings as confirmed, likely omitted, or uncertain, and present omissions separately from confirmed matches.

How to edit Apple Notes without losing hashtags?

AppleScript export may omit UI-visible #tag markers, so prefer minimal append-only edits on tagged notes. Before claiming full restore capability, quit Notes and physically back up NoteStore.sqlite, NoteStore.sqlite-wal, and NoteStore.sqlite-shm.

Can AppleScript read all tags in an Apple Notes note?

No. AppleScript body and plaintext exports can omit #tag markers visible in the Notes UI, so absence in the export does not prove a tag is missing. DB-level confirmation requires inspecting hashtag child rows in a copied NoteStore snapshot.

Why does local Codex history miss some of my work?

Long-lived remote sessions on other hosts do not appear in local ~/.codex traces, and manual terminal work may lack clean Codex transcripts. Merge remote rollout evidence and supplement with shell history and iTerm text logs before concluding a day is fully covered.

What backup is needed before editing a tagged Apple Notes note?

Two levels exist: a logical export backup for low-risk text edits, and a full-fidelity physical backup of the NoteStore.sqlite file set taken from a Notes-quit state for whole-store raw restore. Only the physical level protects tagged-note state.