Skip to content
Back to skills

Roblox Mobile Playtest

ASecurity

Playtest and QA Roblox experiences for mobile and tablet. Use for device simulator checks, touch controls, safe areas, thumb zones, text readability, orientation, HUD overlap, first-action friction, and mobile performance verification through Studio MCP.

  • 5 stars
  • 0 votes
  • 1 copy
  • 3 views
  • Added September 6, 2026
ai-agentsgodebuggingperformance

Works with

  • mcp

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add AshExplained/roblox-skills --skill roblox-mobile-playtest --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Roblox Mobile Playtest?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Roblox Mobile Playtest
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashexplained-roblox-mobile-playtest/badge)](https://www.skillsdirectory.com/skills/ashexplained-roblox-mobile-playtest)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: roblox-mobile-playtest
description: Playtest and QA Roblox experiences for mobile and tablet. Use for device simulator checks, touch controls, safe areas, thumb zones, text readability, orientation, HUD overlap, first-action friction, and mobile performance verification through Studio MCP.
---

# Roblox Mobile Playtest

## Goal

Verify that the Roblox experience works and feels good for phone-first players.

## Use Device Simulator

When available, invoke `rbx-device-simulator-lua` before device-specific UI checks. Use it to test phone and tablet form factors, orientation, and layout behavior.

## MCP Workflow

1. Confirm Studio state with `get_studio_state`.
2. Start play mode with `start_stop_play`.
3. Use device simulation when relevant.
4. Exercise controls with `user_mouse_input`, `user_keyboard_input`, and direct character movement through `character_navigation`.
5. Capture evidence with `screen_capture`.
6. Check `get_console_output`.

## Mobile Checks

- First core action is reachable in 10-30 seconds.
- Tap targets are large and spaced apart.
- Important buttons avoid thumb conflict and system gesture zones.
- HUD does not block movement, combat, collection, or objectives.
- Text is readable on phone and tablet sizes.
- Objective markers and reward feedback are visible without opening menus.
- No keyboard-only requirement exists for core play.
- Menus scroll cleanly and do not hide primary actions.
- Performance remains smooth in the first playable area.

## Report Format

Return:

- Devices or simulated form factors checked.
- First-action time.
- Control and HUD issues.
- Readability issues.
- Console or performance risks.
- Highest-impact fixes before launch.

## Next

Run the full first-session pass with `roblox-playtest-qa`, and send any defect to `roblox-debugging-bugfix`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.