studio-inspect
Skill9 starsChanged 7 months agoMITView on GitHub
Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 16
Search for and inspect each expected service:
≈ “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
/studio-inspect — Studio State Inspection
Delegate to: studio-mcp-operator
Steps
1. Connect
mcp__roblox-studio__list_roblox_studios→mcp__roblox-studio__set_active_studio
2. Verify Service Structure
Search for and inspect each expected service:
- ServerScriptService — should contain server scripts
- ServerStorage — should contain modules and data
- ReplicatedStorage — should contain Shared/ and remotes
- StarterGui — should contain UI
- StarterPlayer — should contain client scripts
- ReplicatedFirst — loading screen (if used)
- Workspace — game world
3. Check for Common Issues
- Scripts in wrong services (LocalScript in ServerScriptService, Script in StarterGui)
- Missing remotes (search for RemoteEvent/RemoteFunction instances)
- Orphan instances (parts not in a model or folder)
- Unanchored parts that should be anchored
- Scripts with errors (grep for common patterns)
4. Report
# Studio Inspection Report
## Service Structure
- [✅/❌] ServerScriptService: X scripts
- [✅/❌] ReplicatedStorage: X modules, Y remotes
- ...
## Issues Found
1. [Issue with location and recommendation]
## Instance Counts
- Parts: X
- Scripts: X
- RemoteEvents: X
- UI elements: XDoes 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.

