gate-check
Skill4 starsChanged 8 months agoMITView on GitHub
Validates phase readiness — checks required deliverables, permits, quality standards, and budget tolerance. Outputs PASS / CONCERNS / FAIL.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- supernovae-st/nikatheir own version, first seen Oct 28, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Oct 19, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- nuncaeslupus/literary-critictheir own version, first seen Oct 13, 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
- CoralGameSkill
team-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
- lilangMaxSkill
create-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 versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 118same name
- microsoft/cat-agent-skills★ 101same name
- supernovae-st/nika★ 96same 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
10 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 repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- budget-checkSkill
- change-orderSkill
- deficiency-reportSkill
- design-decisionSkill
- design-reviewSkill
- design-systemSkill
- drawing-reviewSkill
- estimateSkill
- feasibility-studySkill
- handover-checklistSkill
- map-systemsSkill
- material-auditSkill
- milestone-reviewSkill
- occupancy-checklistSkill
- onboardSkill
- phase-planSkill
- project-stage-detectSkill
- punch-listSkill
- regulatory-adaptSkill
- retrospectiveSkill
- reverse-documentSkill
- revision-logSkill
- schedule-analysisSkill
- scope-checkSkill
- setup-project-typeSkill
- site-bulletinSkill
- site-inspectionSkill
- startSkill
- team-envelopeSkill
- team-handoverSkill
- team-interiorSkill
- team-mepSkill
- team-safetySkill
- team-siteSkill
- team-structuralSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When invoked: Check all phase gate criteria — required documents exist, permits obtained, quality standards met, budget within tolerance.
“Common” is measured: kept by at least 6 in 10 of the 19 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
When invoked: Check all phase gate criteria — required documents exist, permits obtained, quality standards met, budget within tolerance. Output structured gate check with PASS/CONCERNS/FAIL verdict and list of blocking items.
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.