Hi Creators,
Today, we’re launching creator-authored Skills: guides for Assistant that you can define to automate specific conventions you want to follow or tedious workflows you don’t want to repeat — like how you name modules or the checks you run before you ship.
When we introduced Skills, every Skill was Roblox-authored and built into Assistant. Now, you can make your own Skills for Assistant to help you with your workflows. You can also edit or delete Skills at any time. Skills also work in third-party MCP clients like Claude Desktop, Claude Code and Cursor so the conventions you capture follow you wherever you use Assistant.
Create Your Own Skills
A Skill is a Markdown document that teaches Assistant how to perform a task, including a short description of what it does and when to apply it, plus a body of instructions. The description is what Assistant matches your request against and decides when the Skill is used.
Your Skills live in the new Skills tab in Assistant Settings, reachable from the “…” menu in the top-right of the Assistant panel. You can manage everything about your Skills from this tab, including:
- Create a new Skill from scratch
- Edit your Skills inline
- Enable or disable a Skill with a single toggle
- Duplicate a Roblox-authored Skill to customize it
- Delete Skills you no longer need
For the full walkthrough, see the Assistant skills documentation.
Here are a few example use cases:
-
Coding conventions: Capture your naming, formatting, and module structure once for Assistant to follow every time it writes or edits code.
-
Team workflows: Encode the steps your team always runs, like how you structure a feature or the checks you do before shipping.
-
Repeatable tasks: Turn any workflow you’d rather not re-explain into a Skill you can trigger on demand.
Using a Skill in a Conversation
There are two ways a Skill gets applied:
-
Automatically: Assistant compares your request against your Skills’ descriptions and loads whatever matches.
-
On demand: type / in the composer to open the slash menu and pick a Skill by name. It attaches as a chip, and you can attach more than one.
When a Skill loads, Assistant shows an inline indicator, styled like a tool call, so you can see exactly what was added to the context. That record stays with the chat, making Assistant easier to trust and debug. Skills work in third-party MCP clients too, like Cursor and Claude Code, so they follow you wherever you use Assistant. See the Studio MCP server documentation for setup.
Skills You Can Build On
Every Roblox-authored Skill is a starting point you can customize. Click Duplicate to get a fully editable copy, then change anything: rewrite the instructions, add your own steps, or swap in your team’s conventions. When you duplicate a Skill, the original switches off automatically so Assistant uses your copy from then on, while the original keeps updating independently in the background. If you ever want it back, just toggle your copy off and switch the original back on.
Let Assistant Write and Update Skills for You
You can ask Assistant to create a starting point for you to build on. There are two ways to prompt Assistant to make a Skill:
- /rbx-create-skill: describe the workflow you want to capture, and Assistant asks a few clarifying questions, then writes a properly formatted Skill for you, frontmatter and all. It appears in your Skills tab, ready to use.
- Just ask: tell Assistant in plain language to update a Skill you already have. Something like “update my luau-style skill to always use PascalCase for module names” works, and it edits the Skill for you.
You can directly iterate on and edit Skills at any time; it’s up to you what Assistant handles, and how it operates.
New Roblox Skill: Unit Testing
A new Roblox-authored Skill we’re shipping is unit-test, a Skill for writing, running, and debugging Luau unit tests for ModuleScripts. When you ask Assistant to add tests or improve coverage, it:
-
Detects your setup first. If your place already uses a framework like Jest-Lua or TestEZ, the Skill conforms to it, matching its idioms, naming, and file locations. If it finds nothing, it falls back to a lightweight built-in test harness.
-
Writes focused, honest tests. It structures cases as Arrange-Act-Assert, tests observable behavior through the public API rather than private internals, and covers normal paths, boundaries, and error cases.
-
Runs them and reports back. It runs the suite in Play, reads the results, and gives you a summary, isolating and diagnosing failures instead of weakening assertions to force a pass.
We’d love your feedback on this one. Try it on a module and tell us: does it write tests the way you would? Does it detect your framework correctly? What’s missing? And since it’s just a Skill, you can duplicate it and reshape it to your team’s conventions. We want to fold what you learn back into the default Skill.
What’s Next
This is the first release of creator-authored Skills, and we’ll plan to add additional functionality based on your feedback. We’re currently looking at place-scoped Skills that live with a specific place, richer Skills that can bundle supporting files like scripts and examples, easy sharing with other creators through the Creator Store, and improved editing support. As always, we’ll keep the updates coming.
Share Your Feedback
Skills are meant to give you more control, so your feedback shapes where this goes next. Let us know:
- What workflows or conventions you’d want to capture as a Skill
- How the /rbx-create-skill flow feels, and whether Assistant gets your Skills right
- Anything about the unit-test Skill: what works, what doesn’t, and what it should do differently
Happy creating!
The Roblox Studio Team
FAQS
Click to view
Where can I learn more?
- See the Assistant Skills documentation for how to create, manage, and customize Skills.
How is a Skill different from just telling Assistant what I want in chat?
- A Skill is reusable. Instead of re-explaining a convention or workflow in every conversation, you write it once and Assistant applies it whenever it’s relevant.
Can I use Skills outside of Studio?
- Yes. Any MCP client connected to the Roblox Studio MCP server, like Cursor or Claude Code, can use your Skills. See the Studio MCP server documentation for setup.
How does Assistant decide when to use a Skill?
- It matches your request against each enabled Skill’s description, so a clear description is what makes a Skill trigger at the right time. You can also invoke a Skill directly from the slash menu when you want to be explicit.
Can I turn a Skill off?
- Yes. Every Skill has an enable/disable toggle in the Skills tab, and disabled Skills won’t load or appear in the slash menu. You stay in control of exactly which Skills are active.
Are Skills available across all my projects?
- Yes. Skills are tied to you, not to a single project, so a Skill you create or enable is available in every place you open in Studio. Place-scoped Skills, which live with one specific place, are on our roadmap.
Do I have to use the Roblox-authored Skills?
- No. You can disable any of them, or duplicate one and change it to fit your project. They’re a starting point, not a requirement.
If I duplicate a Roblox-authored Skill, will my copy get future Roblox updates?
- No. Once you duplicate a Skill, your copy is fully yours to edit, and the original keeps updating independently. That’s the trade-off for making it your own: you keep your changes, and you can always duplicate the original again later if you want the newest version.
Can I see which Skills shaped a given response?
- Yes. A loaded skill indicator appears inline with each response and stays in your chat history, so you can always check what was applied and debug Assistant’s behavior.