agentleFS
Sign inStart free
AshExplainedAshExplained/roblox-skills/roblox-release-operations/SKILL.md

roblox-release-operations

Skill5 starsChanged 5 months agoMITView on GitHub

Run Roblox release operations. Use for pre-publish checklists, smoke tests, release notes, staged rollout thinking, rollback plans, live issue response, release gates, version readiness, and post-release monitoring.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    Update notes and player-facing promise match the build.

    line 22
  2. Distinctive:

    Avoid irreversible migrations without fallback.

    line 37
  3. Distinctive:

    Keep manual admin recovery steps for grant/data issues.

    line 39
  4. Very specific:

    After release, watch metrics with roblox-analytics-instrumentation and player sentiment with roblox-community-ops.

    line 64

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roblox Release Operations

Goal

Ship updates with confidence and a clear recovery path.

Pre-Release Gate

Verify:

  • Core loop smoke test passes.
  • Mobile layout and controls are usable.
  • Save/load and valuable grants are checked.
  • Purchases are server-authoritative.
  • Console has no new errors.
  • Performance risks are known.
  • Update notes and player-facing promise match the build.

Release Notes

Include:

  • New content.
  • Balance changes.
  • Bug fixes.
  • Known issues when necessary.
  • Return hook or event deadline.

Rollback Thinking

  • Know which changes are data-schema-sensitive.
  • Avoid irreversible migrations without fallback.
  • Stage risky economy or persistence changes behind server flags where possible.
  • Keep manual admin recovery steps for grant/data issues.

Post-Release Watch

Track:

  • Error spikes.
  • Purchase/grant failures.
  • Save/load failures.
  • Funnel drop-offs.
  • Economy inflation.
  • Community reports.

Output

Return:

  • Release readiness status.
  • Blocking issues.
  • Smoke test plan.
  • Rollback or mitigation plan.
  • Post-release watchlist.

Next

After release, watch metrics with roblox-analytics-instrumentation and player sentiment with roblox-community-ops; hand any live bug to roblox-debugging-bugfix.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free