How do I install the Weppy Roblox MCP Guide skill?

Run npx skillmds@latest add hope1026/weppy-roblox-mcp-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Weppy Roblox MCP Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Weppy Roblox MCP Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Weppy Roblox MCP Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Weppy Roblox MCP Guide?

hope1026 (@hope1026) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Weppy Roblox MCP Guide by hope1026 — Agent Skill

Name: Weppy Roblox MCP Guide
Author: hope1026

Weppy Roblox MCP Guide

Use when controlling Roblox Studio through WEPPY Roblox MCP, choosing MCP tool actions, selecting among multiple connected Studio targets, creating or checking UI Studio interfaces, running playtests, inspecting logs, or verifying direct Studio workflows.

hope1026 Updated Sep 17, 2026

File contents

WEPPY Roblox MCP Guide

Overview

Use this skill to operate Roblox Studio through WEPPY Roblox MCP with the right tool/action sequence. Keep exact action and parameter lookup in references so the main workflow stays small.

Workflow

Check connection, tier, and connected Studio targets before mutating Studio. Use Basic-safe status actions first when available.
If more than one Studio target is connected, read references/multi-studio-routing.md, select one target, and keep its selector on related calls.
Choose the narrowest MCP action that matches the request. Read references/mcp-actions.md for exact action names, params, tier, route, and aliases.
For UI work, run the UI Studio loop in references/ui-studio.md instead of ad hoc GUI mutation.
For play mode, test scripts, logs, or dashboard reports, use references/playtest.md.
Prefer purpose-built tools over execute_luau. Use arbitrary Luau only when no typed action covers the request.
After mutating Studio, verify with a readback action, preview/check, logs, or playtest output depending on the workflow.

References

references/mcp-actions.md: generated MCP tool/action/parameter reference.
references/multi-studio-routing.md: deterministic target selection and selector precedence.
references/ui-studio.md: UI Studio design brief, create/update, preview, and Design Check loop.
references/playtest.md: playtest controls, automated test runner, logs, and screenshot limitations.

Guardrails

Do not invent Roblox asset IDs. Use user-provided IDs or an explicit accepted asset search result.
Do not call Edit-mode screenshot capture while a playtest is active.
Do not present Design Check suggestions as mandatory failures.
Do not expose raw action counts in user-facing marketing copy.

---name: weppy-roblox-mcp-guidedescription: Use when controlling Roblox Studio through WEPPY Roblox MCP, choosing MCP tool actions, selecting among multiple connected Studio targets, creating or checking UI Studio interfaces, running playtests, inspecting logs, or verifying direct Studio workflows.---# WEPPY Roblox MCP Guide## OverviewUse this skill to operate Roblox Studio through WEPPY Roblox MCP with the right tool/action sequence. Keep exact action and parameter lookup in references so the main workflow stays small.## Workflow1. Check connection, tier, and connected Studio targets before mutating Studio. Use Basic-safe status actions first when available.2. If more than one Studio target is connected, read `references/multi-studio-routing.md`, select one target, and keep its selector on related calls.3. Choose the narrowest MCP action that matches the request. Read `references/mcp-actions.md` for exact action names, params, tier, route, and aliases.4. For UI work, run the UI Studio loop in `references/ui-studio.md` instead of ad hoc GUI mutation.5. For play mode, test scripts, logs, or dashboard reports, use `references/playtest.md`.6. Prefer purpose-built tools over `execute_luau`. Use arbitrary Luau only when no typed action covers the request.7. After mutating Studio, verify with a readback action, preview/check, logs, or playtest output depending on the workflow.## References- `references/mcp-actions.md`: generated MCP tool/action/parameter reference.- `references/multi-studio-routing.md`: deterministic target selection and selector precedence.- `references/ui-studio.md`: UI Studio design brief, create/update, preview, and Design Check loop.- `references/playtest.md`: playtest controls, automated test runner, logs, and screenshot limitations.## Guardrails- Do not invent Roblox asset IDs. Use user-provided IDs or an explicit accepted asset search result.- Do not call Edit-mode screenshot capture while a playtest is active.- Do not present Design Check suggestions as mandatory failures.- Do not expose raw action counts in user-facing marketing copy.

Frequently asked questions