Individual skill
roblox-publish-checklist
Use before publishing or updating a Roblox experience to run evidence-backed release gates and a pre-release audit.
skills/tools/roblox-publish-checklist/SKILL.md
Source commit ceee4aaa5004502e2a51d78b3c33bba44d84742b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 177
- Repository last updated
- Oct 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-skills Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- game-development Repository topic
- luau Repository topic
- roblox Repository topic
- roblox-studio Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,110 bytesreferences/full.mddoc · 10,262 bytes
Read excerpt
# 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