Skip to content
Skills Library
Programming · Testing

forge-verify-loop

/forge-verify-loop

Use after building or changing anything in Roblox Studio via MCP, and whenever debugging a Roblox runtime error, broken import, floating/grey/mis-scaled model, or "it doesn't work". Replaces eyeballing with structured probes (Probe.scan/compare/shots, Log.digest, Check.run) and a measure -> diff -> repair loop.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use after building or changing anything in Roblox Studio via MCP, and whenever debugging a Roblox runtime error, broken import, floating/grey/mis-scaled model, or "it doesn't work". Replaces eyeballing with structured probes (Probe.scan/compare/shots, Log.digest, Check.run) and a measure -> diff -> repair loop.

Triggers from the description

it doesn
Original author description

Use after building or changing anything in Roblox Studio via MCP, and whenever debugging a Roblox runtime error, broken import, floating/grey/mis-scaled model, or "it doesn't work". Replaces eyeballing with structured probes (Probe.scan/compare/shots, Log.digest, Check.run) and a measure -> diff -> repair loop.

How it works

SKILL.md has no level-two headings · 26 lines, 182 words

SKILL.md preview
---
name: forge-verify-loop
description: Use after building or changing anything in Roblox Studio via MCP, and whenever debugging a Roblox runtime error, broken import, floating/grey/mis-scaled model, or "it doesn't work". Replaces eyeballing with structured probes (Probe.scan/compare/shots, Log.digest, Check.run) and a measure -> diff -> repair loop.
---

# Forge verify + debug loop

Paths are relative to the repo root (plugin: `${CLAUDE_PLUGIN_ROOT}`). Read `WORKFLOW.md` (Debug protocol,
Studio verification, Safety rules) for detail.

**Before anything:** check Studio state (`studio_status` / `get_studio_state`). If Play mode, don't stop the user's
playtest; use Server/Client DataModels read-only.
**Load tools once per DataModel:** `python forge.py luau bundle` (generates `dist/`), then run `dist/load_forge.luau`
via `execute_luau` -> `shared.Forge.{Probe,Log,Check}`. Nothing is written to the place.
Hot-reload one module with `dist/load_<Module>.luau`.

Build verification:
1. `return shared.Forge.Probe.scan{root="Workspace.X"}`  (refuses > 20k descendants: scope down)
2. With a manifest: `Probe.compare("Workspace.X", manifest)` -> exact `ScaleTo` factor / `Color3.fromHex`.
3. Apply `fix` fields in one `execute_luau`; end with `ChangeHistoryService:SetWaypoint(...)`.
4. Re-scan until no error/warn. Then `Probe.shots(root)` -> `screen_capture` for the visual check.

Runtime debugging:
1. Reproduce with `start_stop_play` + input tools (or the `playtest` subagent).
2. `return shared.Forge.Log.digest{sinceSeconds=120}` in **Server**, then **Client**. Branch on `code`.
3. Hypothesis -> smallest read-only probe -> fix -> **same repro** -> digest must say `clean`.
4. Add `Log.emit` events for state that matters; read with `Log.events(tag)`.

Never claim done from intent: report the probe output that proves it.

Versions

The database has no other skills named forge-verify-loop.

Database snapshot: 13.11.2026 · package version 147a0fc3115d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100roblox-mcp
    Connect an AI client to Roblox Studio through MCP. Use for connection setup, Studio tools, multiple Studio windows, playtesting, or combining MCP with Script Sync.
  • 100roblox-studio-mcp
    Use when working in Roblox Studio through MCP: editing scripts or scenes, generating assets, playtesting, screenshots, or input.
  • 96forge-blender-to-roblox
    Use when a Roblox task needs a custom 3D asset that primitives/generate_mesh can't do well - exact shapes, hero props, budgeted meshes, kit-bashed scenery - or when importing any Blender/GLB/FBX model into Studio. Builds the asset in headless Blender, validates it against Roblox…
  • 90roblox-studio-mcp
    Use the Roblox Studio MCP server (Roblox_Studio) to inspect the open place, read scripts, run Luau, play test, read Output, simulate input and take screenshots. Use whenever Studio MCP tools are available, to verify changes in Studio, or when asked to test or debug in the game.
  • 100roblox-get-started
    Get Roblox Studio connected so you can build Roblox games with the user. Installs Studio if it's missing, opens it, guides the user through signing in and turning on its MCP server, and confirms the connection, automating every step the user doesn't have to do by hand. Use when…
  • 95roblox-game-forge
    Turn Roblox game ideas or design briefs into playable Roblox Studio prototypes, then refine them through design feedback and actual playtesting. Use for designing and building a Roblox game, implementing a brief in Studio, or continuing a project made through this workflow. Skip…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.