Guides
Roblox Claude skills: give Claude Code Roblox know-how
Use Roblox skills with Claude Code: Studio's built-in skills over MCP, the official Roblox Studio plugin, and writing your own SKILL.md for your game.
3 min read

Quick answer
What are Roblox skills for Claude?
Skills are packaged instructions that Claude loads when a task needs them. For Roblox there are two kinds: the skills built into Roblox Studio, which Claude reads through Studio's MCP server and the official Roblox Studio plugin, and your own Claude Code skills, written as SKILL.md files, that teach Claude your project's rules.
What a skill is
In Claude Code, a skill is a folder with a SKILL.md file: instructions, and optionally scripts or reference files, that Claude loads only when they're relevant. That keeps Claude's context small until it needs, say, your UI conventions or Roblox's DataStore rules.
Skill source 1: Roblox Studio's built-in skills
Roblox ships Roblox-specific skills inside Studio itself. With Studio's MCP server switched on, an assistant can use tools named skill and list_skills to read them, and create_skill and edit_skill to manage your own. These names come from the tool list in Roblox's official plugin README. The README says: "For Roblox-specific know-how, your assistant uses the skills built into your version of Studio."
Setting it up with Claude Code:
- Install Roblox Studio, sign in and open a place.
- In Studio: Assistant ⟩ … ⟩ Manage MCP Servers (Settings ⟩ MCP Servers in newer versions) and turn on Enable Studio as MCP server (Studio MCP).
- In Claude Code, run
/plugin, search for Roblox Studio, and install it. - Ask Claude: "list my open Roblox Studio windows." It should name your place.
Full walkthrough: build Roblox games with Claude.

Skill source 2: your own project skills
Built-in skills know Roblox. They don't know your game. Write project skills for things like:
- Folder layout: "Server code lives in ServerScriptService/Systems; one ModuleScript per system."
- Code style: naming, typed Luau, how you handle errors.
- Networking rules: "All purchases go through the Shop RemoteFunction; never trust client prices."
- Data: your DataStore keys and schema, and how to migrate.
- Asset rules: "Every imported mesh: CollisionFidelity Box unless walkable; CastShadow off under 2 studs."
Put them in .claude/skills/<skill-name>/SKILL.md in your project, with a short description at the top so Claude knows when to use each one. Keep each skill focused on one job.
Community skills on GitHub
People share Roblox skill packs, for UI, Luau patterns or specific frameworks. Before using one:
- Read it. A skill is instructions plus possibly scripts Claude may run.
- Check it's current. Roblox APIs change; old advice causes bugs.
- Prefer the built-in Studio skills for core Roblox knowledge, and add community skills only for gaps.
Tips
- One skill, one job. "Roblox UI" and "Roblox data saving" should be separate.
- Show examples. A short code example beats a page of rules.
- Update skills when Claude gets something wrong twice. That's a missing rule.
- Save or publish before big agent runs. The plugin README warns that not every change can be undone from Studio.
A skill for asset imports
If you import models from outside Studio, a skill can tell Claude how to set them up every time: collision fidelity, anchoring, folder placement, naming. Pair it with a generator for the models themselves. Vi3W turns prompts, photos or sketches into textured, retopologised meshes exported as GLB, FBX or OBJ. Import them, and let Claude apply your rules. Make models in Vi3W.
Last reviewed

