roblox-publish-checklist
Skill150 starsChanged 52 days agoMITView on GitHub
Use before publishing or updating a Roblox experience to run evidence-backed release gates and a pre-release audit.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rodrigo-guerraa/roblox-hubedited, first seen Oct 17, 2026
- szlay/roblox-basetheir own version, first seen Jul 24, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- rodrigo-guerraa/roblox-hub★ 235% same
Wrote their own version · 1
- szlay/roblox-base★ 1same name
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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- roblox-architectureSkill
- roblox-collaboration-modeSkill
- roblox-dataSkill
- roblox-luau-coreSkill
- roblox-luau-patternsSkill
- roblox-luau-typesSkill
- roblox-networkingSkill
- roblox-performanceSkill
- roblox-securitySkill
- roblox-server-dataSkill
- roblox-analyticsSkill
- roblox-game-designSkill
- roblox-growth-designSkill
- roblox-monetizationSkill
- roblox-player-psychologySkill
- roblox-animation-vfxSkill
- roblox-audioSkill
- roblox-buildingSkill
- roblox-cameraSkill
- roblox-guiSkill
- roblox-inputSkill
- roblox-lightingSkill
- roblox-localizationSkill
- roblox-npc-aiSkill
- roblox-physicsSkill
- roblox-cloudSkill
- roblox-studio-mcpSkill
- roblox-toolingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Purchases changed: test durable, idempotent receipt grants and retries.
- Very specific: line 32
Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication.
- Distinctive: line 38
Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
- Distinctive: line 39
Test every supported input mode and representative viewport/device tier.
- Distinctive: line 41
Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
- Distinctive: line 46
Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Roblox Publish Checklist
When to Load
Load before publishing or updating a live experience. Test the surfaces and risks the change introduces.
Quick Reference
1. Define the release
Record the changed places, scripts, assets, configuration, schemas, products, supported devices, and rollback path. Classify each gate as required, conditional, or not applicable before testing.
2. Block on high-consequence failures
- Persistence changed: load, save, migration, duplicate-session, disconnect, and shutdown behavior. Load
roblox-dataorroblox-server-data. - Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load
roblox-networkingandroblox-security. - Purchases changed: test durable, idempotent receipt grants and retries. Load
roblox-monetization. - Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication. Load
roblox-cloud.
A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.
3. Exercise the shipped surface
- Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
- Test every supported input mode and representative viewport/device tier.
- Measure errors, memory, frame/network cost and streaming.
- Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
- Confirm Dashboard metadata, permissions and policy; after publishing, verify the version actually serving players.
4. Require evidence
Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.
Output
READY, NOT READY, or READY WITH ACCEPTED RISK; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.
Details: references/full.md
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.