agentleFS
Simple-With-UsSimple-With-Us/BotFleet/.claude/skills/apple-notes/SKILL.md

apple-notes

Skill4 starsChanged 10 days agoApache-2.0View on GitHub

Write owner-facing Apple Notes in the `Coding` folder (local on this Mac) — plans, designs, reviews, handoffs, rollouts, living Completion notes. Use whenever Monet produces something the owner needs to read, not only when they say "Notes." Title [APP, Monet] … with a refreshed timestamp.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, openclaw-release-maintainer and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • hkyutongSkill

    openclaw-release-maintainer

    Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

    Also in 4 projects that use this

  • AtomicBot-aiSkill

    taskflow

    Also in 6 projects that use this

  • math-incSkill

    findmy

    Track Apple devices and AirTags via FindMy.app on macOS using AppleScript and screen capture.

    Also in 10 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 8 projects that use this

  • math-incSkill

    jupyter-live-kernel

    Use a live Jupyter kernel for stateful, iterative Python execution via hamelnb. Load this skill when the task involves exploration, iteration, or inspecting intermediate results — data science, ML experimentation, API exploration, or building up complex code step-by-step. Uses terminal to run CLI commands against a live Jupyter kernel. No new tools required.

    Also in 5 projects that use this

  • +1 more from math-inc

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default is headless pin via the Pin Coding Note shortcut (no focus steal).

    line 33
  2. Distinctive:

    No date in the title. No word "session".

    line 43
  3. Very specific:

    Prefer --html for anything longer than a few lines.

    line 76
  4. Very specific:

    After the type line: <div><br></div>

    line 79
  5. Very specific:

    After every heading: <div><br></div>

    line 80
  6. Very specific:

    After every paragraph: <div><br></div>

    line 81
  7. Very specific:

    After a list, before the next heading: <div><br></div>

    line 83
  8. Distinctive:

    Do not pass a packed markdown blob.

    line 85
  9. Distinctive:

    Do Notes: plans, design docs, reviews, handoffs, rollouts, Completion / work-complete for anything the owner might ask about.

    line 89
  10. Distinctive:

    When generating a handoff report for a peer agent to take over (e.g.

    line 103

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Apple Notes (MONET)

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

  • Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
  • Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
  • Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

Mac only. Cloud sessions: skip Notes, say so, leave the handoff in the PR.

Notes.app does not render raw Markdown. The helper converts MD → HTML. Pass --html only when you already have Notes-safe HTML.

Helper

/Users/jay/apps/apple-notes-coding.sh "Title" "plain body"
/Users/jay/apps/apple-notes-coding.sh "Title" --html /path/to/body.html
/Users/jay/apps/apple-notes-coding.sh --update "Title" "body"
/Users/jay/apps/apple-notes-coding.sh --update "Title" --html /path/to/body.html
/Users/jay/apps/apple-notes-coding.sh --pin-only "Exact Title"
/Users/jay/apps/apple-notes-coding.sh --unpin-only "Exact Title"

Also: --notify / --pushover, --needs-owner / --action-required, --summary "one sentence", --pr "18".

Default is headless pin via the Pin Coding Note shortcut (no focus steal). Do not APPLE_NOTES_ACTIVATE=1 unless the owner is sitting at the Mac.

Title

[APP, Monet] short topic
  • Acronyms first, then Monet (Title Case, not all-caps Slack tags).
  • Multi-app: [ST, CT, Monet] … (impact order).
  • No date in the title. No word "session". Do not repeat the title as an H1 in the body.
AcronymApp
UMUsage-Monitor
STSocratic.Trade
CTCongress.Trade
CTScongress-trading-shared
DDDealDex
PSPersonal-Site
AFLai-fleet-coordinator (this repo / Mac collab / skill pack)
OPSfleet-ops (sibling identity; do not invent a checkout here)

Second body row

The helper injects/refreshes:

Sun, Aug 9, 3:52pm · PR #18

Local Mac time, no leading zeros, lowercase am/pm. Refresh on every --update.

Then: type line (Completion / Plan / Review / Design / Handoff / Rollout / Incident / Fleet change / Work log), then content.

Order: Needs owner first when applicable, then Problem → What was done → Decisions → Next steps.

A real U+00A0 plus a normal space between sentences in the body file you pass the helper (owner ruling 2026-10-23).  Never write the &nbsp; entity yourself.

Layout (owner 2026-08-21 — binding)

Notes.app collapses adjacent blocks. A wall of text with no air is a bug. The owner reads these on iPhone.

Prefer --html for anything longer than a few lines. In that HTML:

  • <h2> never <h1> (the helper already wraps the title as h1)
  • After the type line: <div><br></div>
  • After every heading: <div><br></div>
  • After every paragraph: <div><br></div>
  • Between every bullet in the same list: <div><br></div>
  • After a list, before the next heading: <div><br></div>

Do not pass a packed markdown blob. If you use the plain-body MD path, put a blank line between every section and every bullet — the helper turns those blanks (and consecutive list items) into spacers. --html with explicit spacers is still the owner-readable path.

When

Do Notes: plans, design docs, reviews, handoffs, rollouts, Completion / work-complete for anything the owner might ask about.

Skip: pure #Work-In-Progress chatter, effort-board row edits, routine commit messages, peer-only PR nits.

Open a living work note when substantial work starts. Always Completion at the end. Update in place; unpin stale Completion notes when the lane closes (--unpin-only).

Background-jobs inventory note is ⭐️ Background Jobs Master List — refresh that title exactly when MAC-LOCAL-PROCESSES.md changes.

Canon

  • /Users/jay/apps/FLEET-PROTOCOL.md § Apple Notes
  • Skills: closeout, owner-copy

Handoff Reports (Immediate & Living)

When generating a handoff report for a peer agent to take over (e.g. before hitting quota or upon owner stop request):

  • Title Format: ⭐️ [APP, Agent] HANDOFF REPORT: Short topic (or *** [APP, Agent] HANDOFF REPORT: Short topic)
  • 6-Section Body:
    1. Executive Summary & Objective
    2. Current Work State & Artifacts (worktree path, branch, commit SHA, PR status, dirty/stashed files)
    3. What Was Completed
    4. What Remains to Be Done (actionable numbered list for substitute agent)
    5. Gotchas, Blockers & Open Decisions
    6. Reproduction & Verification Commands

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.