orgtology

Palette Orgtology Skill

What is the Orgtology?

The Orgtology is a living document generated by Palette that contains context about the user's organization, team, priorities, and direction. It can be accessed via MCP resources (always fresh) or synced to a local PALETTE.md file for folder-scoped context.

When to use this skill

• When the user says "sync palette", "update orgtology", "refresh team context", or runs /palette:sync-orgtology
• When the user asks about team structure, priorities, or direction and no PALETTE.md exists — suggest syncing or reading the MCP resource directly
• When PALETTE.md exists, check its "Last synced" timestamp against get-orgtology-updated-at. If a newer version is available, inform the user and offer to re-sync.

MCP Resources (always-fresh, no file needed)

For quick lookups without syncing, read resources directly:

• orgtology:// — full orgtology (organization + teams + user profile)
• orgtology://organization — organization overview, strategy, priorities, people
• orgtology://teams — team structure, projects, workstreams, working patterns
• orgtology://me — your role, current focus, working style, key relationships

If resource reads fail or are not supported by your client, use the get-orgtology tool instead with the equivalent scope:

• get-orgtology scope="full" (equivalent to orgtology://)
• get-orgtology scope="organization" (equivalent to orgtology://organization)
• get-orgtology scope="teams" (equivalent to orgtology://teams)
• get-orgtology scope="me" (equivalent to orgtology://me)

Syncing to PALETTE.md

Default sync

/palette:sync-orgtology → reads orgtology:// → writes full orgtology to ./PALETTE.md

Granular sync

/palette:sync-orgtology organization → reads orgtology://organization → writes org-only /palette:sync-orgtology teams → reads orgtology://teams → writes teams-only /palette:sync-orgtology me → reads orgtology://me → writes user profile only

How to sync

1. Determine which resource to fetch:
   • No argument: orgtology://
   • With argument (organization, teams, me): orgtology://{argument}
2. Read the resource from the Palette MCP server. If the resource read fails or is unsupported, call the get-orgtology tool with the corresponding scope.
3. Write or update PALETTE.md in the current directory:
   • If PALETTE.md exists with markers: replace everything between markers, update "Last synced" timestamp
   • If PALETTE.md exists without markers: append the marker block at the end of the file
   • If PALETTE.md doesn't exist: create it
4. Ensure exactly one project instruction file references PALETTE.md:
   • Scan all candidates: CLAUDE.md, AGENTS.md, CURSORRULES, .cursorrules
   • If any already references PALETTE.md, do nothing
   • Otherwise, pick the first existing candidate (in that order) and append: "Organizational context is in PALETTE.md — read it for team context."
   • If none exist, create CLAUDE.md with that reference line
5. Summarize what changed (new team members, updated priorities, etc.)

File format

Orgtology (synced from Palette)

Last synced: {YYYY-MM-DDTHH:mm:ssZ}

{content from resource}

Staleness check

When this skill loads and PALETTE.md exists with a "Last synced" timestamp, call get-orgtology-updated-at from the Palette MCP server. If the orgtology has been updated since the last sync, inform the user and offer to re-sync. If already up to date, tell the user — don't re-sync unnecessarily.

Important

• Never overwrite content outside the markers
• Always preserve any manually added content in PALETTE.md
• Write to the current directory, not the global ~/.claude/CLAUDE.md
• The reference line in CLAUDE.md, AGENTS.md, CURSORRULES, or .cursorrules should be added once, not duplicated