agentleFS
szlayszlay/roblox-base/.claude/skills/roblox-publish-checklist/SKILL.md

roblox-publish-checklist

Skill1 starsChanged 4 months agoMITView on GitHub

Use before publishing or updating a Roblox game to check data, security, performance, monetization, mobile, metadata, social, and analytics.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All remotes validated server-side (types, ranges, ownership) ✓ · No secrets in ReplicatedStorage/StarterPlayer ✓ · Rate limiting on remotes …

    line 21
  2. Distinctive:

    When Studio MCP is available, attach evidence for each claimed pass: inspection/readback, runtime console, screenshot, or an explicit …

    line 47

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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

When to Load

Load when preparing to publish or update a Roblox game. Provides a structured checklist covering data persistence, security, performance, monetization, mobile, gameplay, metadata, social, and analytics. Use to catch blockers before going live.

Quick Reference

1. Data & Persistence

DataStore save/load ✓ · Session locking (ProfileStore) ✓ · BindToClose ✓ · Data migration plan ✓ · Disconnect-during-save edge case ✓ · No parallel save race conditions ✓

2. Security

All remotes validated server-side (types, ranges, ownership) ✓ · No secrets in ReplicatedStorage/StarterPlayer ✓ · Rate limiting on remotes ✓ · Logic server-side only (currency, inventory, damage) ✓ · ProcessReceipt: grant THEN PurchaseGranted ✓ · Anti-cheat basics (speed, teleport, inventory) ✓

3. Performance

Mobile tested ✓ · Part count reasonable ✓ · No memory leaks (events disconnected) ✓ · MicroProfiler: no scripts >1ms/frame ✓ · StreamingEnabled if large map ✓ · Signal cleanup ✓

4. Monetization

GamePasses idempotent on rejoin ✓ · DevProducts deliver correctly ✓ · Creator Rewards decision and eligibility reviewed if relevant ✓ · Prices competitive ✓ · No pay-to-win ✓

5. Mobile

Touch controls work ✓ · UI uses Scale not Offset ✓ · ContextActionService ✓ · Small screen tested ✓ · Orientation handled ✓ · Low-end device tested ✓

6. Gameplay

Core loop 10+ min test ✓ · Edge cases: disconnect during trade, death during cutscene, rapid pressing, rejoin mid-game ✓ · Tutorial/FTUE ✓ · Difficulty curve ✓ · Fun check ✓

7. Metadata

Icon 512x512 ✓ · 3+ thumbnails ✓ · Description ✓ · Genre ✓ · Max players ✓ · Badges ✓ · Rating ✓

8. Social

Private servers ✓ · Party/chat/friend ✓ · Report/block safe ✓ · Tags correct ✓ · Team assignment ✓

9. Analytics

Events: join/leave, purchases, completions, session length, errors ✓ · Funnel tracking ✓ · Dashboard configured ✓

Output Format

  1. READY / NOT READY 2. Critical blockers 3. Warnings 4. Pass count/% 5. Failed items + fixes

When Studio MCP is available, attach evidence for each claimed pass: inspection/readback, runtime console, screenshot, or an explicit unavailable-capability note.

📖 Full reference: references/full.md

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.