gate-check
Skill4 starsChanged 6 days agoMITView on GitHub
Runs a phase gate: checks exit criteria for the current stage and returns PASS / CONCERNS / FAIL / NOT ASSESSED.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- supernovae-st/nikatheir own version, first seen Nov 12, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
Used with
Projects with it also use setup-engine, team-level and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 10 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 10 projects that use this
- +2 more from CoralGame
- +5 more from lilangMax
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- microsoft/cat-agent-skills★ 108same name
- supernovae-st/nika★ 100same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- phj128/autoworker★ 18same name
- dawn840705/codex-code-studios★ 17same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-abmSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Very specific: line 39
Read the gate definition in .claude/docs/phase-gates.md
- Distinctive: line 40
Check every criterion against actual files.
- Distinctive: line 42
Ask the economic-reasoning, methodology and model-risk specialists for a verdict on their criteria
- Distinctive: line 46
Before the verdict is recorded: review blockers and owners
- Distinctive: line 60
Every FOUND criterion cites a file
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from .claude/skills/gate-check/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/gate-check — Gate Check
Category: Governance · Primary agent: project-planning-specialist
Runs a phase gate: checks exit criteria for the current stage and returns PASS / CONCERNS / FAIL / NOT ASSESSED.
Arguments: whatever the user wrote after the command name.
Purpose
Run a phase gate: check, criterion by criterion, whether the evidence for leaving the current stage exists in the project's files, collect specialist verdicts, and return an overall verdict with blockers, owners and next actions. A gate never passes by default; missing evidence means NOT ASSESSED.
Use it when a project wants to move from one stage to the next (concept, design, build, estimate, validate, operate), or before a milestone review.
Do not use it when the question is release approval for a model (/model-risk-review, /model-release).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Stage artifacts
- studio-config.yaml
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
project-planning-specialist— primary agent; coordinates the work and integrates resultseconomic-reasoning-specialist— Frames the economic question and tests whether results make economic sensemodeling-methodology-specialist— Chooses methods and architecture across model families, sets code and data standards, and resolves technical trade-offs between traditional, structural and AI approachesmodel-risk-governance-specialist— Defines model risk levels and validation depth, enforces builder-validator independence, governs AI/LLM use and recommends release or block
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Workflow
- Read the gate definition in
.claude/docs/phase-gates.md - Check every criterion against actual files; mark FOUND or ABSENT
- Cite the file path for each FOUND item; for lego models include the manifest check status
- Ask the economic-reasoning, methodology and model-risk specialists for a verdict on their criteria
- Return an overall verdict with blockers, owners and next actions
Checkpoints with the user
- Before the verdict is recorded: review blockers and owners
Common pitfalls
- Passing on promises rather than files
- Criteria marked FOUND without a file reference
- Blockers without owners
Output
production/gates/<stage>-<date>.md
The gate record lists each criterion with FOUND or ABSENT and its evidence path, specialist verdicts, the overall verdict, blockers, owners and next actions.
Gate / verdict
- Verdict 'NOT ASSESSED' if required evidence is absent — never a pass by default
- Every FOUND criterion cites a file
Suggested next steps
/milestone-review
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

