Analyze — Read-Only Deep Analysis

Use this skill to answer the user’s question through read-only repository analysis. In this repo, that usually means Roblox Studio, Luau, plugin, creator-runtime, or workflow evidence, not generic software diagnosis detached from the actual creator surface.

Use $analyze when

• the user wants a grounded explanation, not code changes
• the answer requires reading multiple files or tracing behavior across boundaries
• there are several plausible explanations and they need to be ranked
• confidence should reflect the strength of the available evidence
• the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything

Examples:

• why a remote validation path behaves a certain way
• how a creator HUD or plugin surface is wired across modules
• what likely explains a trade, datastore, or workflow regression
• what would be impacted by changing a provider contract, remote schema, or creator-runtime boundary
• which interpretation of the current Roblox-facing codebase is best supported