使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-playtest-qa開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Roblox Playtest QA
Purpose
Use this skill to verify that a Roblox change works in Studio and supports player-facing quality. A playtest should prove both behavior and feel.
Setup
- Run
list_roblox_studios. - Use
set_active_studioif needed. - Run
get_studio_state. - Start play mode with
start_stop_playwhen verification requires live behavior.
Test Checklist
- First action is reachable within 10-30 seconds.
- Controls work without keyboard-only assumptions.
- HUD text is readable and not blocking gameplay.
- Rewards, currency, XP, or progress update correctly.
- The next objective is visible after each loop.
- Social features are visible early when relevant.
- Monetization prompts are optional and do not interrupt first-session flow.
- Server-side systems own valuable state.
- No obvious frame drops or runaway instance/script growth.
get_console_outputhas no new errors.
MCP Tools To Use
character_navigationfor movement and route checks.user_keyboard_inputanduser_mouse_inputfor controls and UI.screen_capturefor visual verification.get_console_outputfor errors and warnings.inspect_instanceorexecute_luaufor state checks after interaction.
Report Format
Return:
- What was tested.
- Evidence gathered, including screenshots or console results when available.
- Pass/fail by area.
- Bugs or risks ranked by player impact.
- Recommended next verification step.
Do not mark roadmap items complete without human approval, even after a passing playtest.
Next
Send any bug to roblox-debugging-bugfix and any performance issue to roblox-performance-optimization. If the slice passes, mark it in roblox-triage / ROADMAP.md and prepare the build with roblox-release-operations.