Promote
alirezarezvani/claude-skills
Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement.
OpenGantry iii worker. An agent skill from iii-hq/workers.
Apache-2.0Auto-check passed
Install Opengantry
$ npx skills add iii-hq/workers --skill opengantry -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install iii-hq/workers opengantry --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/opengantry/skills .claude/skills/opengantry && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .claude/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/iii-hq/workers/tree/main/opengantry/skillsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add iii-hq/workers --skill opengantry -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install iii-hq/workers opengantry --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/opengantry/skills .agents/skills/opengantry && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .agents/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add iii-hq/workers --skill opengantry -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install iii-hq/workers opengantry --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/opengantry/skills .cursor/skills/opengantry && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .cursor/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/iii-hq/workers.git --path opengantry/skills--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add iii-hq/workers --skill opengantry -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install iii-hq/workers opengantry --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/opengantry/skills .gemini/skills/opengantry && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .gemini/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install iii-hq/workers opengantryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add iii-hq/workers --skill opengantry -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .github/skills && cp -r skills-src/opengantry/skills .github/skills/opengantry && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .github/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add iii-hq/workers --skill opengantry -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install iii-hq/workers opengantry --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/iii-hq/workers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/opengantry/skills .opencode/skills/opengantry && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "opengantry" agent skill from https://github.com/iii-hq/workers/tree/main/opengantry/skills into .opencode/skills/opengantry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opengantry", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
opengantry- GitHub stars
- 113
- Token cost
- ~705 tokens
- SKILL.md length
- 305 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
OpenGantry iii worker. An agent skill from iii-hq/workers.
- An iii project needs deterministic promote gates: gantry::verify runs the repo gate command
- SKILL.md covers When to Use, Preferred stack (do not…, Boundaries and Functions, plus 1 more section
- Calls git
- Gantry::middleware blocks promote-class calls until a verdict token matches the current mission
What it does
Opengantry is an agent skill from iii-hq/workers. 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.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is Apache-2.0.
When your agent uses it
- 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
Example prompts
- “/opengantry”
What it can do on your machine
Read from SKILL.md and the folder at commit ebfe027. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Opengantry loads about 705 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 305 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from iii-hq/workers at commit ebfe027, republished under its Apache-2.0 licence (© iii-hq). 305 words, ~705 tokens.
Download SKILL.mdSave it as
.claude/skills/opengantry/SKILL.md (or your agent's skills folder).- 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.
opengantry
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.
When to Use
- Promote-class functions on a governed port should stay blocked until verify passes.
- You want unattended agents without an unattended
git push— pair withapproval-gatefor human-held judgement calls.
Preferred stack (do not reinvent)
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.
Boundaries
- Session admission (
session::auth) — that is the adopter's IdP worker. - Writing
.gitagent/law — Planner commits missions. The worker process does not. - Leases — durable at
<repo>/.gitagent/leases.json(0600), not instate::KV.
Functions
gantry::verify— runverifyMissionfor 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— blockgantry::/opengantry::namespace squatting and reserved suffixesgantry::on-trigger-registration— block triggers bound into thegantry::namespacegantry::on-trigger-type-registration— always deniedgantry::verdict— trigger type; fires after every verify (pass or fail) for audit/notifications
Bootstrap (host only)
If .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.
© iii-hq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in opengantry/skills of iii-hq/workers.
Open the folder on GitHubat commit ebfe027
Compare with similar skills
Opengantry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Opengantry this skilliii-hq/workers | 113 | — | ~705 | Automated safety check: Pass | Apache-2.0 | |
| Promotealirezarezvani/claude-skills | 28k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Worker Visualizernexu-io/open-design | 100k | — | ~998 | Automated safety check: Pass | Apache-2.0 | |
| Agent Worker Specialistruvnet/ruflo | 74k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Loop Workerruvnet/ruflo | 74k | — | ~297 | Automated safety check: Pass | MIT | |
| Cloudflare Workerssickn33/agentic-awesome-skills | 47k | 2 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Worker Visualizer
nexu-io/open-design
A real-time data/particle/simulation visualizer whose heavy compute runs in a Web Worker (off the main thread), optionally sharing memory with the UI via SharedArrayBuffer, and renders to a canvas…
Agent Worker Specialist
ruvnet/ruflo
Agent skill for worker-specialist - invoke with $agent-worker-specialist
Loop Worker
ruvnet/ruflo
Run Ruflo background workers using Claude Code native /loop scheduling
Cloudflare Workers
sickn33/agentic-awesome-skills
Build and deploy edge functions with Cloudflare Workers and Wrangler.
Deterministic Design
sickn33/agentic-awesome-skills
Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen…
More from iii-hq/workers
All 19 skills in this repoCron
iii-hq/workers
Schedule any registered function on a 6- or 7-field cron expression with the standalone cron worker.
Email
iii-hq/workers
Send and read email from the iii engine — SMTP send, IMAP read, and real-time IDLE push as a subscribable trigger type.
HTTP
iii-hq/workers
Expose registered functions as HTTP endpoints with the standalone http worker.
Kanban
iii-hq/workers
File-backed kanban board: create, read, move and comment on tickets by key or uuid, assign agent profiles, and wake on comments through the kanban:comment trigger instead of polling.
Pubsub
iii-hq/workers
DEPRECATED (will be removed in an upcoming release; migration guide https://iii.dev/docs/upgrading/migrate-from-streams).
Release Sync
iii-hq/workers
Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked.
Questions about Opengantry
What does Opengantry do?
OpenGantry iii worker. An agent skill from iii-hq/workers. Opengantry is an agent skill from iii-hq/workers. OpenGantry iii worker.
When should I use Opengantry?
Opengantry fits situations like: 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.
How do I install Opengantry in Claude Code?
Run `npx skills add iii-hq/workers --skill opengantry -a claude-code`. Or copy the skill folder (opengantry/skills in iii-hq/workers) into .claude/skills/opengantry in your project. Claude Code loads it when a task matches its description.
How do I install Opengantry in Codex?
Run `npx skills add iii-hq/workers --skill opengantry -a codex`. Or copy the skill folder (opengantry/skills in iii-hq/workers) into .agents/skills/opengantry in your project. Codex loads it when a task matches its description.
Can I use Opengantry in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iii-hq/workers --skill opengantry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opengantry, .gemini/skills/opengantry, .github/skills/opengantry and .opencode/skills/opengantry in your project.
What does Opengantry need to run?
Going by SKILL.md and its folder, Opengantry needs the command-line tools its instructions call (git).
Does Opengantry access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Opengantry safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Opengantry use?
Opengantry is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Opengantry use?
About 705 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Opengantry?
Skills that share tags, products or a category with Opengantry: Promote (alirezarezvani/claude-skills, 28k stars), Worker Visualizer (nexu-io/open-design, 100k stars), Agent Worker Specialist (ruvnet/ruflo, 74k stars) and Loop Worker (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Opengantry?
iii-hq (a GitHub organization) maintains it in iii-hq/workers, which has 113 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 10, 2026.
Source: iii-hq/workers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.