Public-safe, not repo-internal

Use the public-safe Apple Notes Snapshot guidance pack, not the internal maintainer stack.

These files are the public-safe subset. They are meant for repo-scoped prompt or guidance workflows that need truthful positioning and clean builder-surface contracts without pulling in internal task boards, archive hygiene rules, or machine-specific closeout procedures.

What this pack is

  • A small public subset of the repo's internal skill corpus.
  • Focused on truthful positioning and builder-surface contract maintenance.
  • Designed to be copied into your own repo-scoped instruction flow or host-specific guidance layer.

What this pack is not

  • Not the raw .agents/skills/ directory from this repository.
  • Not a claim that every internal maintainer or archive-validation skill is public-safe.
  • Not an official plugin marketplace artifact or a host-specific install bundle.

Public-safe files carried into tagged truth in v0.1.7

Current-main standalone public skill packet

  • notes-snapshot-control-room/ is a standalone packet with its own SKILL.md.
  • Use it when you want one portable folder that keeps the control-room identity, preflight-before-attach rule, and starter-pack versus official-listing boundary together.
  • It stays public-safe because it does not depend on task boards, machine-private paths, or owner-session-only rituals.

Install path

  1. Start with the public files under examples/public-skills/.
  2. Copy them into the repo-scoped guidance surface that your host or workflow already uses.
  3. Keep the content repo-scoped and reviewable rather than hiding it in a machine-private prompt layer.
  4. Pair the files with your host's current docs for the exact storage path or registration UI.

This page intentionally documents the pack contents and public boundaries. It does not pretend every host uses one universal skill loader path.

Copy recipes by host

Host or workflow How to use the pack What still stays host-owned
Codex Pair these files with the Codex starter pack and keep them in the repo-scoped guidance layer next to your MCP registration. Exact Codex config path, trust settings, and attach verification
Claude Code Pair these files with the Claude Code starter pack so the MCP registration and repo-scoped guidance tell the same story. Exact Claude config layers, permissions, and attach verification
OpenCode Use the files as plain markdown guidance beside the local MCP template. Exact config location, attach flow, and host runtime proof
Generic repo guidance Copy the files into whatever repo-scoped instruction surface your tooling already reads. Where your own tooling stores repo-scoped prompts or instructions

Best-fit use cases

  • Keeping README and docs wording honest when AI, MCP, or builder-language starts expanding.
  • Keeping CLI, Local Web API, AI Diagnose, and MCP contract pages aligned.
  • Keeping browser/profile/tab, Docker/cache, and branch/worktree cleanup discipline visible in repo-scoped guidance instead of hiding it in operator folklore.
  • Teaching collaborators what this repo does not claim before they draft new public copy.

Host fit

Host or workflow Pack fit What still stays host-owned
Codex Good fit for repo-scoped guidance or project instructions Exact host config path, trust settings, and attach verification
Claude Code Good fit for project guidance that complements project-scoped MCP registration Exact Claude config layers, permissions, and attach verification
OpenCode Good fit as plain markdown guidance paired with project config Exact config location, attach flow, and host runtime proof
OpenHands Usable as plain markdown guidance only, paired with the generic MCP launch shape Exact config surface, attach flow, and whether the current host build keeps the same MCP contract
OpenClaw-style front door Not a truthful fit for this pack as a product binding Do not treat these files as an assistant front door, plugin, or hosted runtime contract
Generic repo guidance Best fit Where your own tooling stores repo-scoped prompts or instructions

What stays internal-only

  • Archive target validation and cross-repo leak detection.
  • Task-board-driven closeout ledgers in their current maintainer form.
  • Machine-specific manual validation runbooks and internal evidence files.

The public pack keeps the shareable guidance and leaves the repo-private maintenance rituals out of band.

Public-safe inclusion test

  • Keep it public-safe if the guidance still works without machine-private paths, task-board state, private archives, or owner-session-only steps.
  • Pull it back out if the guidance starts depending on local credential routing, private browser/session state, or maintainer-only closeout rituals.
  • Keep host fit honest: Codex and Claude guidance can travel as repo-scoped markdown, while OpenCode/OpenHands stay lighter-weight and OpenClaw stays comparison-only.

Update story

  • Repo side: this pack follows Apple Notes Snapshot release history and public docs wording.
  • Host side: your host may change faster than this pack does, so keep host-specific storage paths and approval steps in the host docs.
  • Tagged truth: the pack became tagged public truth in v0.1.7, while current main can still tighten the wording between releases.
  • Safe rule: if a public-safe skill starts depending on internal task boards, archive evidence, or machine-specific paths, pull it back out of the public pack.

New public-safe runtime discipline

The pack now includes a public-safe runtime hygiene skill for repo-scoped closeout work. Use it when you want browser/profile/tab cleanup, task-owned Docker restraint, and branch/worktree/PR convergence rules written into the same repo-scoped guidance layer as the builder contract itself.

  • It is public-safe because it teaches cleanup and ownership boundaries, not machine-private secrets.
  • It still does not grant write access to Search Console, registrars, social platforms, or other non-GitHub external accounts.
  • It pairs naturally with Codex, Claude Code, and generic repo guidance when you want a team to leave less residue behind after a task.

What to pair with this pack