sbox

S&Box Grounded Retrieval

Retrieve S&Box APIs and signatures from https://sdocs.suiram.dev and use only grounded results.

Treat this skill as the default path for S&Box game projects.

API Surface

Retrieval Workflow

Start with search_sbox_docs semantics via /api/sbox/search for gameplay/modding questions.
If results are sparse or missing, query /api/search and /api/sdk/search .
For any candidate API to use in code, resolve its id and fetch:
/api/sdk/describe?id=<id>
/api/sdk/get-signature?id=<id>
Preserve returned signatures exactly (displaySignature , signature , sourceSignature ).
If multiple near-matches exist, ask for refinement (namespace, type, method overload, parameter types).
Use /api/sdk/ask only as supporting context, then confirm final APIs with search + signature routes.

Response Rules

Never invent S&Box APIs, types, members, namespaces, or signatures.
Cite grounded identifiers when proposing code (at minimum include API name + signature).
Prefer APIs with clearer member metadata (description , parameters , returnType , exampleUsage ) when available.
Before writing or editing S&Box code, run retrieval first.
If no grounded match is found, say so explicitly and request a narrower query.

Query Quality

Use specific, narrow queries first:

Then broaden only if needed.

Tool Mapping

Use these mappings even when the user does not explicitly name the skill.

Source Transparency