ashexplained/roblox-skills

roblox-playtest-qa

Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-playtest-qa

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

  1. Run list_roblox_studios.
  2. Use set_active_studio if needed.
  3. Run get_studio_state.
  4. Start play mode with start_stop_play when 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_output has no new errors.

MCP Tools To Use

  • character_navigation for movement and route checks.
  • user_keyboard_input and user_mouse_input for controls and UI.
  • screen_capture for visual verification.
  • get_console_output for errors and warnings.
  • inspect_instance or execute_luau for 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.

aus demselben Repository

Weitere Skills

Alle Skills
ashexplained
Community

roblox-animation-audio-feedback

Improve Roblox feel through animation, audio, VFX, haptics-like feedback, reward juice, movement feel, combat feedback, UI transitions, emotes, and satisfying loop feedback without hurting mobile performance.

Installationen / 1h
3
GitHub Stars
63
Aktualisiert
1. Juli
ashexplained
Community

roblox-combat-systems

Design, implement, and review Roblox combat systems. Use for melee, ranged, abilities, cooldowns, hit detection, damage validation, status effects, enemy AI hooks, combat UI, balance knobs, VFX/SFX, and exploit-resistant remotes.

Installationen / 1h
3
GitHub Stars
63
Aktualisiert
1. Juli
ashexplained
Community

roblox-creator-store-security-audit

Audit Roblox Creator Store, Toolbox, inventory, group, universe, package, model, UI, gameplay, plugin-like, and other third-party imported assets for malicious or risky scripts. Use whenever Claude imports, inserts, reviews, or trusts Creator Store assets, especially assets with Scripts, LocalScripts, ModuleScripts, hidden descendants, require calls, HTTP, DataStore, remote creation, obfuscated code, or suspicious names.

Installationen / 1h
3
GitHub Stars
63
Aktualisiert
1. Juli
ashexplained
Community

roblox-debugging-bugfix

Debug and fix Roblox bugs through Studio MCP. Use for repro steps, console errors, script search/read/edit flow, broken UI, failed gameplay systems, data issues, remotes, regressions, root-cause reports, and post-fix verification.

Installationen / 1h
3
GitHub Stars
63
Aktualisiert
1. Juli