agentleFS
Sign inStart free
Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/substrate/notion-operating-system/SKILL.md

notion-operating-system

Skill1 starsChanged 4 months agoMITView on GitHub

Design safe, private-first Notion operating systems, estate audits, parallel rebuilds, template systems, and public mirrors. Use when asked to map a Notion workspace, clean or restructure Notion, create business/personal Notion dashboards, build reusable Notion templates, or turn private Notion content into sanitized public docs. Portable and brand-neutral. Trigger phrases: map my Notion, Notion estate audit, restructure Notion, Notion operating system, Notion dashboard, Notion template system, publish Notion docs.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start read-only. Search, fetch, team lookup, and aggregate data-source queries are safe for audits.

    line 11
  2. Distinctive:

    Create an estate map with source citations, privacy class, health signal, database health, and migration action.

    line 16
  3. Distinctive:

    Use a small set of canonical databases: Projects, Areas, Actions, Knowledge, People/CRM, Content, Assets/Templates, Systems/Agents, …

    line 19
  4. Distinctive:

    Add advanced modules only when justified: Source Registry, Quality Checklists, Public Staging, Repurpose Queue, Metrics Loop, and Migration …

    line 20
  5. Distinctive:

    Keep an approval log for every write action.

    line 23
  6. Very specific:

    Use references/notion-os-patterns.md for schema and patterns.

    line 27
  7. Very specific:

    Use a parallel parent page named Notion OS v2 Draft unless the user gives a specific name.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Notion Operating System

Policy

Start read-only. Search, fetch, team lookup, and aggregate data-source queries are safe for audits. Do not create, update, move, duplicate, publish, apply templates to, create databases/views, alter schemas, or delete Notion content until the user approves exact targets and changes in the current thread.

Workflow

  1. Audit current state with search/fetch before designing a rebuild.
  2. Create an estate map with source citations, privacy class, health signal, database health, and migration action. When a local compiler exists, generate deterministic CSV, Markdown, summary JSON, and red-team artifacts from inventory-level evidence.
  3. Identify existing canonical systems before designing anything new. Preserve hubs/databases with clear source-of-truth rules, active operating views, public/private staging, source registries, quality gates, and metrics loops.
  4. Design a parallel v2 hub instead of mutating the old workspace in place.
  5. Use a small set of canonical databases: Projects, Areas, Actions, Knowledge, People/CRM, Content, Assets/Templates, Systems/Agents, Decisions/Policies, and Archive.
  6. Add advanced modules only when justified: Source Registry, Quality Checklists, Public Staging, Repurpose Queue, Metrics Loop, and Migration Control.
  7. Make templates sparse, useful, and reviewable; every template needs a clear job and privacy class.
  8. Publish only curated mirrors or sanitized templates by default.
  9. Keep an approval log for every write action.

Estate Map Fields

Use references/notion-os-patterns.md for schema and patterns. At minimum capture: title, URL/ID, object type, domain, current role, privacy class, health signal, migration action, confidence, and notes.

Default Architecture

Use a parallel parent page named Notion OS v2 Draft unless the user gives a specific name. Build dashboards as operating views, not decorative homepages.

Public Boundary

Classify content as private-only, internal, shareable, public-candidate, or public-approved. Public outputs must be sanitized and approved before publication.

Output Contract

Return:

  • Estate summary.
  • Sitemap or database map.
  • Duplicate/stale clusters.
  • Database health and aggregate counts where safe.
  • V2 architecture.
  • Template plan.
  • Public/private matrix.
  • Migration waves and approval gates.
  • Red-team findings and low-confidence rows.

Built on SIP — Starlight Intelligence Protocol Substrate: starlightintelligence.org/protocol v1.1.0 Layers used: [file-contract, attestation, sovereignty] Vertical: starlight-agent-skills · portable capability layer

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.

Check your setup, free