agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/studio-test/SKILL.md

studio-test

Skill9 starsChanged 7 months agoMITView on GitHub

Run a play test in Roblox Studio via MCP and verify the game works. Starts play mode, checks console for errors, captures a screenshot, executes verification Luau, stops play mode, and reports results.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Wait 3-5 seconds for game initialization

    line 22
  2. Distinctive:

    Do expected RemoteEvents exist in ReplicatedStorage?

    line 27

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

/studio-test — Automated Play Test

Delegate to: studio-mcp-operator

Steps

1. Connect to Studio

  • mcp__roblox-studio__list_roblox_studios — verify Studio is open
  • mcp__roblox-studio__set_active_studio — select the correct instance

2. Pre-Test Check

  • mcp__roblox-studio__search_game_tree — verify key services exist (ServerScriptService, ReplicatedStorage)
  • mcp__roblox-studio__get_console_output — clear/note any pre-existing errors

3. Start Play Test

  • mcp__roblox-studio__start_stop_play — start play mode
  • Wait 3-5 seconds for game initialization

4. Verify Runtime State

  • mcp__roblox-studio__execute_luau — run verification checks:
    • Are core services initialized?
    • Do expected RemoteEvents exist in ReplicatedStorage?
    • Is player data loading without errors?
    • Are any scripts erroring?

5. Capture Visual State

  • mcp__roblox-studio__screen_capture — screenshot the game
  • Analyze: Is the UI rendering? Is the world visible? Any obvious visual issues?

6. Check Console

  • mcp__roblox-studio__get_console_output — read all output since play started
  • Flag: errors (red), warnings (yellow), unexpected prints
  • Categorize: script errors, DataStore errors, remote errors, asset loading errors

7. Stop Play Test

  • mcp__roblox-studio__start_stop_play — stop play mode

8. Report Results

# Play Test Report

**Status**: [PASS / FAIL / WARNINGS]
**Duration**: X seconds
**Studio**: [instance name]

## Console Output
- Errors: [count]
- Warnings: [count]
- [List each error with source script and message]

## Runtime Verification
- [x] Core services loaded
- [x] Remotes exist
- [ ] Player data initialized (FAILED: DataStore timeout)

## Visual Check
- [Screenshot attached]
- [Any visual issues noted]

## Recommendations
1. [Fix needed]
2. [Investigation needed]

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.