一键导入
workbench-sanity-context
Use when designing, reviewing, or updating Sanity as the shared context registry for workbench agents and CLIs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when designing, reviewing, or updating Sanity as the shared context registry for workbench agents and CLIs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.