菜单
OpenGantry iii worker. Use when an iii project needs deterministic promote gates: gantry::verify runs the repo gate command, gantry::middleware blocks promote-class calls until a verdict token matches the current mission.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/iii-hq/workers --skill opengantry命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Build, structure, and validate polished responsive worker UI (React pages, function-trigger and trigger-activity renderers, configuration forms, and stylesheets) injected into the running iii console. Use when adding or changing a worker's console UI, especially when it must match the visual quality of database, console functions/triggers, iii-directory, and state; retain the shared header and visual system; work in narrow/mobile-sized panes; preserve state safely; hot reload; and ship without rebuilding the console.
Discovery entry point for the engine — search the live function catalog, read the skills, system prompts, and agent profiles that installed workers ship off local disk, browse the public iii workers registry over HTTP, and install new worker bundles. Reach for it first to find out which workers exist and how to call them.
Connect this engine to another iii engine over a long-lived WebSocket so functions call across the boundary. Wire stable ids with `forward:`/`expose:`; `bridge.invoke` is the ad-hoc escape hatch.
正在显示 SKILL.md
| name | opengantry |
| description | OpenGantry iii worker. Use when an iii project needs deterministic promote gates: gantry::verify runs the repo gate command, gantry::middleware blocks promote-class calls until a verdict token matches the current mission. |
Call gantry::verify with an absolute repo_root and active mission. The worker runs the repo's declared gate command via the OpenGantry kernel and mints a verdict token bound to that mission revision.
git push — pair with approval-gate for human-held judgement calls.Install and use these ecosystem workers instead of writing custom equivalents:
| Need | Use | Do not |
|---|---|---|
| Machine promote gate | gantry::verify + gantry::middleware | Custom ::verify / ::promote functions |
| Human judgement on ship | approval-gate (approval::gate) | Inline hold logic in your app worker |
| Git land / merge | worktree::land (+ shell for test gates) | Custom myapp::deploy / ::merge |
| GitHub operations | github::* | Raw gh shell from agent code |
| Public governed port | rbac-proxy with gantry::middleware | Rolling your own auth middleware |
| Verify completion events | Subscribe to gantry::verdict | Polling verify JSON for side effects |
Canonical pipeline: worktree::create → agent work → gantry::verify → worktree::land (with verdict_token in context). Promote-class suffixes (::deploy, ::merge, ::publish, ::apply, ::push, ::promote) require a token whose claims match the mission on disk.
session::auth) — that is the adopter's IdP worker..gitagent/ law — Planner commits missions. The worker process does not.<repo>/.gitagent/leases.json (0600), not in state:: KV.gantry::verify — run verifyMission for the active mission; a pass binds the mission to the lease and mints the verdict tokengantry::middleware — governed-port gate; promote-class calls need a token whose claims are recomputed at promote timegantry::on-function-registration — block gantry:: / opengantry:: namespace squatting and reserved suffixesgantry::on-trigger-registration — block triggers bound into the gantry:: namespacegantry::on-trigger-type-registration — always deniedgantry::verdict — trigger type; fires after every verify (pass or fail) for audit/notificationsIf .gitagent is missing in the target repo, run gantry init on the host (not from the sandboxed worker), then commit a mission via the Planner workflow.