Menu
Use when designing, reviewing, or updating Sanity as the shared context registry for workbench agents and CLIs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Strict parser and validator for Workbench closeout comments, verdict/status discipline, PR reference types, and cross-issue REMAINING sync.
Scout, pilot, or review Mirage virtual-filesystem tool use for Workbench agents while preserving source-of-truth and public-safety boundaries.
Source-first, self-loop resistant guardrails for Capy GitHub dialogue responders before any write-capable PR, issue, or review action.
Disk, swap, VM, agent workspace, and stale session hygiene for Multica workbench runtimes.
Advisory-only algorithm and data-structure review gate between Technical Design and Task List.
Durable memory, session summaries, decision logs, issue closeout synthesis, and compact handoffs.
| name | workbench-sanity-context |
| description | Use when designing, reviewing, or updating Sanity as the shared context registry for workbench agents and CLIs. |
Use this skill when a task touches Sanity schemas, Sanity Studio, Sanity MCP, or the cross-CLI context registry.
agentProfileruntimeSurfaceskillContractevidenceEventdecisionRecordhandoffcapyProcessCheckSANITY_CONTEXT_REPORT
project:
dataset:
schema_types:
data_policy:
files_changed:
validation:
residual_risk:
VERDICT: PASS | FLAG | BLOCK
PASS requires schema/build validation and a clean data policy. FLAG is
correct when MCP/OAuth or live dataset writes still need separate approval.
BLOCK is correct when the target project is unknown or the requested data is
unsafe to store.