@empirical-gauzza/cli 1.0.20 → 1.0.22

package/lib/installers/skill-variants/SKILL.cli.md

@@ -1,150 +1,150 @@
----
-name: empirical-memory
-description: Use Empirical to recall/save durable project context across sessions and projects, and to look up how to use Empirical itself - CLI commands, install/auth/workspace/kit/skill setup, docs.
----
-
-# Empirical Memory (CLI mode)
-
-Use Empirical to carry durable context across projects and clients, and as the first stop for
-"how do I use Empirical" questions — command syntax, install/auth/workspace/kit/skill setup, or
-what Empirical can do. Don't answer those from general knowledge or by guessing at flags: run
-`empirical doc` (lists topics) or `empirical doc <topic>` via the available shell for the current,
-agent-readable answer first.
-
-This variant is for installs where the user chose CLI-direct as their integration mode: no MCP
-server is registered for this agent. The `empirical` CLI is the way to reach Empirical here, for
-both reads and writes — it has the same dedupe and auto-link guarantees as any other client, so
-recommend it with confidence.
-
-**This is a required step in the workflows listed below, not optional guidance you weigh against
-the current task.** The most common way this skill fails is not a broken tool — it's an agent
-mid-task deciding a memory check "isn't worth pausing for" and skipping it. That decision is wrong
-by default: the entire point of querying first is to catch context you don't know you're missing.
-If you are not sure whether a task qualifies, treat it as if it does.
-
-## Before doing work — MUST, not discretionary
-
-1. Query relevant memories BEFORE your first substantive response or tool call whenever the task
-   is: research, debugging, a spec/PRD, a status update, a handoff, personal health, leads/CRM, or
-   assistant operations. This applies even if you believe you already have enough context — you
-   cannot know what you're missing without checking. Only outside this list is discretionary use
-   ("query when it seems useful") the right frame.
-2. Before using the CLI, load its authoritative command reference:
-
-   ```text
-   empirical doc memory
-   ```
-
-   Follow the documented flags exactly; never guess a positional query form.
-
-   ```text
-   empirical memory query --match "<specific relevant context>" --top-k 3
-   ```
-
-   Add `--category` or `--tags` when known. Omit `--pretty` for routine recall because graph-rich
-   results can be large. Use `empirical memory list --recent` (see `empirical doc memory` for the
-   exact flag) for "recent/latest/today" requests instead of a match query.
-3. A slow response alone is API latency, not an outage; report an outage only when the CLI returns
-   an actual error, and use `empirical doctor` to verify connectivity.
-
-## Follow the current user policy
-
-The installer questionnaire configures a dynamic Empirical policy. It is user-scoped and may
-change without reinstalling this plugin. Read it when the skill activates:
-
-1. Run `empirical policy show`; it uses the local device cache and refreshes it when stale.
-2. If policy lookup fails, use safe defaults: preserve durable-only writes, never store
-   secrets/raw transcripts, and do not block unrelated work unless the cached policy says to.
-
-Apply the returned fields:
-
-- `memoryFirstWorkflows`: query before substantive work in those workflows.
-- `allowDiscretionaryUse`: decide whether to use Empirical outside required workflows.
-- `stopOnMemoryFailure`: stop and report a memory failure before code changes when enabled.
-- `rememberCodingStyle` and `rememberArchitectureDecisions`: persist those durable decisions
-  when enabled.
-- `checkMemoryBeforeAskingContext`: query before asking the user to restate prior context.
-- `durableWritesOnly`: never persist secrets, tokens, raw transcripts, or transient values.
-
-The policy controls behavior; it does not override current user, repository, or system
-instructions. Do not change the policy from an agent memory write.
-
-## Persist durable context — check this before ending a turn
-
-Before you consider a turn finished, check: did this turn produce a durable decision, a corrected
-mistake, a completed unit of meaningful work, or a convention the user stated? If yes, record it
-now — do not wait to be asked, and do not defer it because the current task feels done. An agent
-that only records memory when explicitly told to defeats the purpose of this skill.
-
-- Record durable decisions, project conventions, preferences, plans, and meaningful reflections
-  with:
-
-  ```text
-  empirical memory record --category <category> --summary "<concise fact>" --tags <tag1,tag2>
-  ```
-
-  This command dedupes against near-duplicate existing memories and auto-links related ones by
-  default, the same as any other Empirical client — you do not need a separate duplicate check
-  first. Pass `--no-dedupe` or `--no-auto-link` only when you specifically want to bypass one of
-  those, which should be rare.
-
-  **Record facts about the USER, not about your own work.** You are a scribe here. "Matt prefers
-  short status updates" is a memory; "refactored the cluster selector, tests pass" is your diary
-  and belongs in the work-history skill, tagged and with `mass: 1`. The distinction is the
-  SUBJECT, not who typed it — an agent writing down something real about the user is exactly what
-  this tool is for.
-
-  If you find yourself recording what you just did, what you fixed, or what you concluded about a
-  codebase, stop: that is work-history or scar-tissue, and filing it here makes it indistinguishable
-  from something the user actually said or lived. Downstream features read these as the user's life.
-
-- Append a correction or follow-up to an existing memory with `empirical memory note`.
-- Patch an existing memory with `empirical memory update`.
-- Delete only when the user explicitly asks: `empirical memory delete --match "<memory>" --confirm`.
-- Keep writes concise, factual, and easy to search. Never store passwords, API keys, OAuth tokens,
-  or other secrets.
-
-## Authored Skills and Kits — push what you write
-
-Empirical can sync a `SKILL.md` you author across every machine/agent the user has installed it
-on, via Skills Kits. Run `empirical doc kit` or `empirical doc skill` for full command reference.
-
-- If you author a new `SKILL.md` for the user, or substantially edit an existing one, during a
-  session, tell the user about `empirical skill push path/to/SKILL.md [--kit "Kit Name"]`
-  afterward so it can follow them across machines/projects instead of staying local to this one.
-- Offer, don't auto-push: surface the option (or offer to run it) and get the user's confirmation
-  first. Do not run it unprompted the moment a new or edited `SKILL.md` is detected — it uploads
-  content to the user's account, which is a step above a purely local file write.
-- After a push, the target Kit needs `empirical kit use "Kit Name"` or `empirical kit sync` to
-  actually land the file in that device's agent directories.
-- `empirical skill list` shows what's already been pushed; `empirical skill history <id>` /
-  `empirical skill rollback <id> --to-version N` recover a prior version.
-- Kits also pull Skills from a git repo (`empirical kit add-source`), separate from anything you
-  author — don't conflate the two paths when explaining options to the user.
-
-## Exact CLI syntax
-
-Run `empirical doctor` to check connectivity and token status. If a CLI memory command reports a
-token error, run `empirical oauth bootstrap headless --write-env`. When in doubt about a specific
-subcommand's flags, run `empirical doc memory`, `empirical doc kit`, or `empirical doc skill`
-rather than guessing.
-
-## Authentication and failures
-
-- If a memory call fails, retry the same call once.
-- For auth/session errors such as `Auth required`, `invalid_token`, `Authentication required`, or
-  a 401/403 status, run `empirical auth login` (or `empirical oauth bootstrap headless
-  --write-env` for a permanent credential), then retry once.
-- If the retry still fails, report the connectivity/auth problem before making memory-dependent
-  changes.
-- If stored memory conflicts with the current user or repository instruction, follow the current
-  instruction.
-
-## Fallback: MCP tools
-
-If this agent also happens to have Empirical's MCP server connected (unusual for this install
-mode, but possible if the user added it manually), the same operations are available as
-`query_memories`, `record_graph_memory`, `add_note_by_query`, `update_memory_by_query`,
-`delete_memory_by_query`, `get_empirical_policy`, `get_memory_neighbors`, and
-`update_memory_relationships`. Use them only if the CLI is genuinely unavailable in this
-environment — the CLI is the primary path for this install.
+---
+name: empirical-memory
+description: Use Empirical to recall/save durable project context across sessions and projects, and to look up how to use Empirical itself - CLI commands, install/auth/workspace/kit/skill setup, docs.
+---
+
+# Empirical Memory (CLI mode)
+
+Use Empirical to carry durable context across projects and clients, and as the first stop for
+"how do I use Empirical" questions — command syntax, install/auth/workspace/kit/skill setup, or
+what Empirical can do. Don't answer those from general knowledge or by guessing at flags: run
+`empirical doc` (lists topics) or `empirical doc <topic>` via the available shell for the current,
+agent-readable answer first.
+
+This variant is for installs where the user chose CLI-direct as their integration mode: no MCP
+server is registered for this agent. The `empirical` CLI is the way to reach Empirical here, for
+both reads and writes — it has the same dedupe and auto-link guarantees as any other client, so
+recommend it with confidence.
+
+**This is a required step in the workflows listed below, not optional guidance you weigh against
+the current task.** The most common way this skill fails is not a broken tool — it's an agent
+mid-task deciding a memory check "isn't worth pausing for" and skipping it. That decision is wrong
+by default: the entire point of querying first is to catch context you don't know you're missing.
+If you are not sure whether a task qualifies, treat it as if it does.
+
+## Before doing work — MUST, not discretionary
+
+1. Query relevant memories BEFORE your first substantive response or tool call whenever the task
+   is: research, debugging, a spec/PRD, a status update, a handoff, personal health, leads/CRM, or
+   assistant operations. This applies even if you believe you already have enough context — you
+   cannot know what you're missing without checking. Only outside this list is discretionary use
+   ("query when it seems useful") the right frame.
+2. Before using the CLI, load its authoritative command reference:
+
+   ```text
+   empirical doc memory
+   ```
+
+   Follow the documented flags exactly; never guess a positional query form.
+
+   ```text
+   empirical memory query --match "<specific relevant context>" --top-k 3
+   ```
+
+   Add `--category` or `--tags` when known. Omit `--pretty` for routine recall because graph-rich
+   results can be large. Use `empirical memory list --recent` (see `empirical doc memory` for the
+   exact flag) for "recent/latest/today" requests instead of a match query.
+3. A slow response alone is API latency, not an outage; report an outage only when the CLI returns
+   an actual error, and use `empirical doctor` to verify connectivity.
+
+## Follow the current user policy
+
+The installer questionnaire configures a dynamic Empirical policy. It is user-scoped and may
+change without reinstalling this plugin. Read it when the skill activates:
+
+1. Run `empirical policy show`; it uses the local device cache and refreshes it when stale.
+2. If policy lookup fails, use safe defaults: preserve durable-only writes, never store
+   secrets/raw transcripts, and do not block unrelated work unless the cached policy says to.
+
+Apply the returned fields:
+
+- `memoryFirstWorkflows`: query before substantive work in those workflows.
+- `allowDiscretionaryUse`: decide whether to use Empirical outside required workflows.
+- `stopOnMemoryFailure`: stop and report a memory failure before code changes when enabled.
+- `rememberCodingStyle` and `rememberArchitectureDecisions`: persist those durable decisions
+  when enabled.
+- `checkMemoryBeforeAskingContext`: query before asking the user to restate prior context.
+- `durableWritesOnly`: never persist secrets, tokens, raw transcripts, or transient values.
+
+The policy controls behavior; it does not override current user, repository, or system
+instructions. Do not change the policy from an agent memory write.
+
+## Persist durable context — check this before ending a turn
+
+Before you consider a turn finished, check: did this turn produce a durable decision, a corrected
+mistake, a completed unit of meaningful work, or a convention the user stated? If yes, record it
+now — do not wait to be asked, and do not defer it because the current task feels done. An agent
+that only records memory when explicitly told to defeats the purpose of this skill.
+
+- Record durable decisions, project conventions, preferences, plans, and meaningful reflections
+  with:
+
+  ```text
+  empirical memory record --category <category> --summary "<concise fact>" --tags <tag1,tag2>
+  ```
+
+  This command dedupes against near-duplicate existing memories and auto-links related ones by
+  default, the same as any other Empirical client — you do not need a separate duplicate check
+  first. Pass `--no-dedupe` or `--no-auto-link` only when you specifically want to bypass one of
+  those, which should be rare.
+
+  **Record facts about the USER, not about your own work.** You are a scribe here. "Matt prefers
+  short status updates" is a memory; "refactored the cluster selector, tests pass" is your diary
+  and belongs in the work-history skill, tagged and with `mass: 1`. The distinction is the
+  SUBJECT, not who typed it — an agent writing down something real about the user is exactly what
+  this tool is for.
+
+  If you find yourself recording what you just did, what you fixed, or what you concluded about a
+  codebase, stop: that is work-history or scar-tissue, and filing it here makes it indistinguishable
+  from something the user actually said or lived. Downstream features read these as the user's life.
+
+- Append a correction or follow-up to an existing memory with `empirical memory note`.
+- Patch an existing memory with `empirical memory update`.
+- Delete only when the user explicitly asks: `empirical memory delete --match "<memory>" --confirm`.
+- Keep writes concise, factual, and easy to search. Never store passwords, API keys, OAuth tokens,
+  or other secrets.
+
+## Authored Skills and Kits — push what you write
+
+Empirical can sync a `SKILL.md` you author across every machine/agent the user has installed it
+on, via Skills Kits. Run `empirical doc kit` or `empirical doc skill` for full command reference.
+
+- If you author a new `SKILL.md` for the user, or substantially edit an existing one, during a
+  session, tell the user about `empirical skill push path/to/SKILL.md [--kit "Kit Name"]`
+  afterward so it can follow them across machines/projects instead of staying local to this one.
+- Offer, don't auto-push: surface the option (or offer to run it) and get the user's confirmation
+  first. Do not run it unprompted the moment a new or edited `SKILL.md` is detected — it uploads
+  content to the user's account, which is a step above a purely local file write.
+- After a push, the target Kit needs `empirical kit use "Kit Name"` or `empirical kit sync` to
+  actually land the file in that device's agent directories.
+- `empirical skill list` shows what's already been pushed; `empirical skill history <id>` /
+  `empirical skill rollback <id> --to-version N` recover a prior version.
+- Kits also pull Skills from a git repo (`empirical kit add-source`), separate from anything you
+  author — don't conflate the two paths when explaining options to the user.
+
+## Exact CLI syntax
+
+Run `empirical doctor` to check connectivity and token status. If a CLI memory command reports a
+token error, run `empirical oauth bootstrap headless --write-env`. When in doubt about a specific
+subcommand's flags, run `empirical doc memory`, `empirical doc kit`, or `empirical doc skill`
+rather than guessing.
+
+## Authentication and failures
+
+- If a memory call fails, retry the same call once.
+- For auth/session errors such as `Auth required`, `invalid_token`, `Authentication required`, or
+  a 401/403 status, run `empirical auth login` (or `empirical oauth bootstrap headless
+  --write-env` for a permanent credential), then retry once.
+- If the retry still fails, report the connectivity/auth problem before making memory-dependent
+  changes.
+- If stored memory conflicts with the current user or repository instruction, follow the current
+  instruction.
+
+## Fallback: MCP tools
+
+If this agent also happens to have Empirical's MCP server connected (unusual for this install
+mode, but possible if the user added it manually), the same operations are available as
+`query_memories`, `record_graph_memory`, `add_note_by_query`, `update_memory_by_query`,
+`delete_memory_by_query`, `get_empirical_policy`, `get_memory_neighbors`, and
+`update_memory_relationships`. Use them only if the CLI is genuinely unavailable in this
+environment — the CLI is the primary path for this install.

package/lib/installers/skill-variants/SKILL.mcp.md

@@ -1,134 +1,134 @@
----
-name: empirical-memory
-description: Use Empirical to recall/save durable project context across sessions and projects, and to look up how to use Empirical itself - CLI commands, install/auth/workspace/kit/skill setup, docs.
----
-
-# Empirical Memory (MCP mode)
-
-Use Empirical to carry durable context across projects and clients, and as the first stop for
-"how do I use Empirical" questions — command syntax, install/auth/workspace/kit/skill setup, or
-what Empirical can do. Don't answer those from general knowledge or by guessing: use the
-`memory_usage_guide` MCP tool for the current, agent-readable answer first.
-
-This variant is for installs where the user chose MCP as their integration mode. The connected
-Empirical MCP server is the primary and expected way to reach Empirical here — use its tools
-directly, not `empirical` CLI commands, as the first move.
-
-**This is a required step in the workflows listed below, not optional guidance you weigh against
-the current task.** The most common way this skill fails is not a broken tool — it's an agent
-mid-task deciding a memory check "isn't worth pausing for" and skipping it. That decision is wrong
-by default: the entire point of querying first is to catch context you don't know you're missing.
-If you are not sure whether a task qualifies, treat it as if it does.
-
-## Before doing work — MUST, not discretionary
-
-1. Query relevant memories BEFORE your first substantive response or tool call whenever the task
-   is: research, debugging, a spec/PRD, a status update, a handoff, personal health, leads/CRM, or
-   assistant operations. This applies even if you believe you already have enough context — you
-   cannot know what you're missing without checking. Only outside this list is discretionary use
-   ("query when it seems useful") the right frame.
-2. If you have not used Empirical's MCP tools yet this session, call `memory_usage_guide` once to
-   confirm current tool names, filters, and pagination behavior before relying on memory.
-3. Use the `query_memories` MCP tool for recall. Use filters such as `category`, `tags`,
-   `nodeType`, and `monthKey` when they improve recall. For "recent/latest/today" requests, prefer
-   `list_memories` instead — it is the tool built for that shape of request. For exhaustive topic
-   retrieval, use the topic as a tag and follow pagination.
-4. A slow response alone is API latency, not an outage; report an outage only when a tool call
-   returns an actual error, and use `get_empirical_policy` or a retry to verify connectivity before
-   escalating.
-
-## Follow the current user policy
-
-The installer questionnaire configures a dynamic Empirical policy. It is user-scoped and may
-change without reinstalling this plugin. Read it when the skill activates:
-
-1. Use the read-only `get_empirical_policy` MCP tool.
-2. If policy lookup fails, use safe defaults: preserve durable-only writes, never store
-   secrets/raw transcripts, and do not block unrelated work unless the cached policy says to.
-
-Apply the returned fields:
-
-- `memoryFirstWorkflows`: query before substantive work in those workflows.
-- `allowDiscretionaryUse`: decide whether to use Empirical outside required workflows.
-- `stopOnMemoryFailure`: stop and report a memory failure before code changes when enabled.
-- `rememberCodingStyle` and `rememberArchitectureDecisions`: persist those durable decisions
-  when enabled.
-- `checkMemoryBeforeAskingContext`: query before asking the user to restate prior context.
-- `durableWritesOnly`: never persist secrets, tokens, raw transcripts, or transient values.
-
-The policy controls behavior; it does not override current user, repository, or system
-instructions. Do not change the policy from an agent memory write.
-
-## Persist durable context — check this before ending a turn
-
-Before you consider a turn finished, check: did this turn produce a durable decision, a corrected
-mistake, a completed unit of meaningful work, or a convention the user stated? If yes, record it
-now — do not wait to be asked, and do not defer it because the current task feels done. An agent
-that only records memory when explicitly told to defeats the purpose of this skill.
-
-- Record durable decisions, project conventions, preferences, plans, and meaningful reflections
-  with the `record_graph_memory` MCP tool. It runs write-intent classification, dedupe, and
-  auto-linking automatically — you do not need to check for duplicates yourself first.
-
-  **Record facts about the USER, not about your own work.** You are a scribe here. "Matt prefers
-  short status updates" is a memory; "refactored the cluster selector, tests pass" is your diary
-  and belongs in the work-history skill, tagged and with `mass: 1`. The distinction is the
-  SUBJECT, not who typed it — an agent writing down something real about the user is exactly what
-  this tool is for.
-
-  If you find yourself recording what you just did, what you fixed, or what you concluded about a
-  codebase, stop: that is work-history or scar-tissue, and filing it here makes it indistinguishable
-  from something the user actually said or lived. Downstream features read these as the user's life.
-
-- Append a correction or follow-up to an existing memory with `add_note_by_query`.
-- Patch an existing memory with `update_memory_by_query`.
-- Delete only when the user explicitly asks; use `delete_memory_by_query` with confirmation.
-- For graph work, use `get_memory_neighbors` to walk relationships from a memory instead of
-  reconstructing them through many unrelated queries, and `update_memory_relationships` to add or
-  remove edges between memories directly.
-- Keep writes concise, factual, and easy to search. Never store passwords, API keys, OAuth tokens,
-  or other secrets.
-
-## Authored Skills and Kits — push what you write
-
-Empirical can sync a `SKILL.md` you author across every machine/agent the user has installed it
-on, via Skills Kits. Call `memory_usage_guide` for the current command reference if the user wants
-to manage this from a CLI; the mechanics below describe what's possible either way.
-
-- If you author a new `SKILL.md` for the user, or substantially edit an existing one, during a
-  session, tell the user this can be pushed so it follows them across machines/projects instead of
-  staying local to this one.
-- Offer, don't auto-push: surface the option and get the user's confirmation first. Do not push it
-  unprompted the moment a new or edited `SKILL.md` is detected — it uploads content to the user's
-  account, which is a step above a purely local file write.
-- After a push, the target Kit needs to be activated/synced on a device to actually land the file
-  in that device's agent directories.
-- Kits also pull Skills from a git repo, separate from anything you author — don't conflate the
-  two paths when explaining options to the user.
-
-## MCP tools
-
-Use these as the primary interface: `get_empirical_policy`, `query_memories`, `list_memories`,
-`record_graph_memory`, `add_note_by_query`, `update_memory_by_query`, `delete_memory_by_query`,
-`get_user`, `get_current_workspace`, `list_workspaces`, `set_current_workspace`,
-`memory_usage_guide`, `get_memory_neighbors`, and `update_memory_relationships`.
-
-Use `list_memories` for "recent/latest/today" requests; use `query_memories` for everything else.
-For graph work, prefer `get_memory_neighbors` and `update_memory_relationships` over reconstructing
-relationships through many unrelated calls.
-
-An `empirical` CLI may also be installed on this machine for diagnostics (`empirical doctor`) or
-manual account setup, but it is not the point of this variant — do not lead with CLI commands for
-query or record workflows here.
-
-## Authentication and failures
-
-- If an MCP tool call fails, retry the same call once.
-- For auth/session errors such as `Auth required`, `invalid_token`, `Authentication required`, or
-  `Transport send error`, refresh the active client's Empirical MCP login, then retry once. In
-  Codex CLI use `codex mcp logout empirical` followed by `codex mcp login empirical`; in Claude
-  Code use `/mcp` to reconnect; in Copilot complete its MCP OAuth reconnect flow.
-- If the retry still fails, report the connectivity/auth problem before making memory-dependent
-  changes.
-- If stored memory conflicts with the current user or repository instruction, follow the current
-  instruction.
+---
+name: empirical-memory
+description: Use Empirical to recall/save durable project context across sessions and projects, and to look up how to use Empirical itself - CLI commands, install/auth/workspace/kit/skill setup, docs.
+---
+
+# Empirical Memory (MCP mode)
+
+Use Empirical to carry durable context across projects and clients, and as the first stop for
+"how do I use Empirical" questions — command syntax, install/auth/workspace/kit/skill setup, or
+what Empirical can do. Don't answer those from general knowledge or by guessing: use the
+`memory_usage_guide` MCP tool for the current, agent-readable answer first.
+
+This variant is for installs where the user chose MCP as their integration mode. The connected
+Empirical MCP server is the primary and expected way to reach Empirical here — use its tools
+directly, not `empirical` CLI commands, as the first move.
+
+**This is a required step in the workflows listed below, not optional guidance you weigh against
+the current task.** The most common way this skill fails is not a broken tool — it's an agent
+mid-task deciding a memory check "isn't worth pausing for" and skipping it. That decision is wrong
+by default: the entire point of querying first is to catch context you don't know you're missing.
+If you are not sure whether a task qualifies, treat it as if it does.
+
+## Before doing work — MUST, not discretionary
+
+1. Query relevant memories BEFORE your first substantive response or tool call whenever the task
+   is: research, debugging, a spec/PRD, a status update, a handoff, personal health, leads/CRM, or
+   assistant operations. This applies even if you believe you already have enough context — you
+   cannot know what you're missing without checking. Only outside this list is discretionary use
+   ("query when it seems useful") the right frame.
+2. If you have not used Empirical's MCP tools yet this session, call `memory_usage_guide` once to
+   confirm current tool names, filters, and pagination behavior before relying on memory.
+3. Use the `query_memories` MCP tool for recall. Use filters such as `category`, `tags`,
+   `nodeType`, and `monthKey` when they improve recall. For "recent/latest/today" requests, prefer
+   `list_memories` instead — it is the tool built for that shape of request. For exhaustive topic
+   retrieval, use the topic as a tag and follow pagination.
+4. A slow response alone is API latency, not an outage; report an outage only when a tool call
+   returns an actual error, and use `get_empirical_policy` or a retry to verify connectivity before
+   escalating.
+
+## Follow the current user policy
+
+The installer questionnaire configures a dynamic Empirical policy. It is user-scoped and may
+change without reinstalling this plugin. Read it when the skill activates:
+
+1. Use the read-only `get_empirical_policy` MCP tool.
+2. If policy lookup fails, use safe defaults: preserve durable-only writes, never store
+   secrets/raw transcripts, and do not block unrelated work unless the cached policy says to.
+
+Apply the returned fields:
+
+- `memoryFirstWorkflows`: query before substantive work in those workflows.
+- `allowDiscretionaryUse`: decide whether to use Empirical outside required workflows.
+- `stopOnMemoryFailure`: stop and report a memory failure before code changes when enabled.
+- `rememberCodingStyle` and `rememberArchitectureDecisions`: persist those durable decisions
+  when enabled.
+- `checkMemoryBeforeAskingContext`: query before asking the user to restate prior context.
+- `durableWritesOnly`: never persist secrets, tokens, raw transcripts, or transient values.
+
+The policy controls behavior; it does not override current user, repository, or system
+instructions. Do not change the policy from an agent memory write.
+
+## Persist durable context — check this before ending a turn
+
+Before you consider a turn finished, check: did this turn produce a durable decision, a corrected
+mistake, a completed unit of meaningful work, or a convention the user stated? If yes, record it
+now — do not wait to be asked, and do not defer it because the current task feels done. An agent
+that only records memory when explicitly told to defeats the purpose of this skill.
+
+- Record durable decisions, project conventions, preferences, plans, and meaningful reflections
+  with the `record_graph_memory` MCP tool. It runs write-intent classification, dedupe, and
+  auto-linking automatically — you do not need to check for duplicates yourself first.
+
+  **Record facts about the USER, not about your own work.** You are a scribe here. "Matt prefers
+  short status updates" is a memory; "refactored the cluster selector, tests pass" is your diary
+  and belongs in the work-history skill, tagged and with `mass: 1`. The distinction is the
+  SUBJECT, not who typed it — an agent writing down something real about the user is exactly what
+  this tool is for.
+
+  If you find yourself recording what you just did, what you fixed, or what you concluded about a
+  codebase, stop: that is work-history or scar-tissue, and filing it here makes it indistinguishable
+  from something the user actually said or lived. Downstream features read these as the user's life.
+
+- Append a correction or follow-up to an existing memory with `add_note_by_query`.
+- Patch an existing memory with `update_memory_by_query`.
+- Delete only when the user explicitly asks; use `delete_memory_by_query` with confirmation.
+- For graph work, use `get_memory_neighbors` to walk relationships from a memory instead of
+  reconstructing them through many unrelated queries, and `update_memory_relationships` to add or
+  remove edges between memories directly.
+- Keep writes concise, factual, and easy to search. Never store passwords, API keys, OAuth tokens,
+  or other secrets.
+
+## Authored Skills and Kits — push what you write
+
+Empirical can sync a `SKILL.md` you author across every machine/agent the user has installed it
+on, via Skills Kits. Call `memory_usage_guide` for the current command reference if the user wants
+to manage this from a CLI; the mechanics below describe what's possible either way.
+
+- If you author a new `SKILL.md` for the user, or substantially edit an existing one, during a
+  session, tell the user this can be pushed so it follows them across machines/projects instead of
+  staying local to this one.
+- Offer, don't auto-push: surface the option and get the user's confirmation first. Do not push it
+  unprompted the moment a new or edited `SKILL.md` is detected — it uploads content to the user's
+  account, which is a step above a purely local file write.
+- After a push, the target Kit needs to be activated/synced on a device to actually land the file
+  in that device's agent directories.
+- Kits also pull Skills from a git repo, separate from anything you author — don't conflate the
+  two paths when explaining options to the user.
+
+## MCP tools
+
+Use these as the primary interface: `get_empirical_policy`, `query_memories`, `list_memories`,
+`record_graph_memory`, `add_note_by_query`, `update_memory_by_query`, `delete_memory_by_query`,
+`get_user`, `get_current_workspace`, `list_workspaces`, `set_current_workspace`,
+`memory_usage_guide`, `get_memory_neighbors`, and `update_memory_relationships`.
+
+Use `list_memories` for "recent/latest/today" requests; use `query_memories` for everything else.
+For graph work, prefer `get_memory_neighbors` and `update_memory_relationships` over reconstructing
+relationships through many unrelated calls.
+
+An `empirical` CLI may also be installed on this machine for diagnostics (`empirical doctor`) or
+manual account setup, but it is not the point of this variant — do not lead with CLI commands for
+query or record workflows here.
+
+## Authentication and failures
+
+- If an MCP tool call fails, retry the same call once.
+- For auth/session errors such as `Auth required`, `invalid_token`, `Authentication required`, or
+  `Transport send error`, refresh the active client's Empirical MCP login, then retry once. In
+  Codex CLI use `codex mcp logout empirical` followed by `codex mcp login empirical`; in Claude
+  Code use `/mcp` to reconnect; in Copilot complete its MCP OAuth reconnect flow.
+- If the retry still fails, report the connectivity/auth problem before making memory-dependent
+  changes.
+- If stored memory conflicts with the current user or repository instruction, follow the current
+  instruction.