Menu
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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-capy-process-check |
| description | Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel. |
Use this skill when the task asks to observe Capy in real time through Brave, Computer Use, or a Capy PR/thread panel.
docs/capy-process-check-lane.mdAlways report:
CAPY_PROCESS_CHECK
target:
browser_app:
capy_surface:
observed_state:
ui_evidence:
cli_evidence:
repo_evidence:
source_of_truth:
action_taken:
residual_risk:
verdict: PASS | FLAG | BLOCK
PASS requires UI state and primary evidence to agree. FLAG means the lane is
usable but evidence is incomplete or stale. BLOCK means a permission, secret,
wrong target, or evidence mismatch prevents action.