ワンクリックで
sync
Fetches Palette context pages and syncs them into a local PALETTE.md file
メニュー
Fetches Palette context pages and syncs them into a local PALETTE.md file
| name | sync |
| description | Fetches Palette context pages and syncs them into a local PALETTE.md file |
Palette is the organizational context layer. It exposes context pages — living, per-scope documents about the organization, each team the user can see, and the user themselves — plus other resource types over time (agent primitives and more). Context pages can be read live over MCP, or synced into a local PALETTE.md for ambient, folder-scoped context.
updatedAt from palette_list_context_pages. If newer pages exist, inform the
user and offer to re-sync.Context pages are reached through three tools:
palette_search — cross-entity discovery. No args → a per-scope summary
(counts by type). scope/scopeId → narrow the namespace. query → search
across every resource type. Use it for orientation when you're unsure what
exists.palette_list_context_pages({scope?, scopeId?}) — list context pages,
metadata only. Each entry carries a uri, title, optional summary,
scope, and an updatedAt ISO timestamp.palette_read_context_page({uri}) — read one page's markdown by its
palette:// uri.scope is one of org | team | person. Each list entry's uri has the form
palette://{scope}/{scopeId}/context-page/{id}.
Equivalent MCP resources (palette://…) exist for clients that prefer the
protocol-level resource API. The tools above are the portable path and work on
every client — prefer them. If a list/search returns truncated: true, the
result was capped; narrow with scope/scopeId.
/palette:sync → list all context pages → read each → write them all to PALETTE.md
/palette:sync org → only org-scope pages
/palette:sync team → only team-scope pages
/palette:sync me → only the user's person-scope page (me maps to scope person)
org → scope: "org"team → scope: "team"me or person → scope: "person"palette_list_context_pages (with the scope filter, if any) to get the
page refs. If the tool is unavailable but MCP resources are, list palette://
resources instead and keep the context-page ones.palette_read_context_page({ uri }) to get its markdown.##
section per page, titled by the ref's title.<!-- palette:context:start --> / <!-- palette:context:end -->
block exists, replace everything between the markers and update "Last synced".<!-- palette:orgtology:start --> /
<!-- palette:orgtology:end --> block exists, replace the whole legacy
block with the new palette:context block.<!-- palette:context:start -->
# Palette context (synced)
Last synced: {YYYY-MM-DDTHH:mm:ssZ}
Scope: {full | org | team | person}
## {page title}
{page markdown}
## {page title}
{page markdown}
<!-- palette:context:end -->
When this skill loads and PALETTE.md exists with a "Last synced" timestamp, call
palette_list_context_pages and compare the most recent updatedAt across the
returned pages to the synced timestamp. If a page is newer, inform the user and
offer to re-sync. If everything is current, tell the user — don't re-sync
unnecessarily.
<!-- palette:context:start/end --> markers