Install any skill in seconds. Free to start, no credit card required.
Get Started Free →besty0728/unity-sample
Sample and demo skills for API connectivity testing — minimal echo/ping-style calls to verify the REST server is reachable.
Passed 17 of 20 test cases with the skill, and 5 of 20 without it.
and 10 more in the full report
14 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
What parameter name is used to identify the target item in delete_object?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies objectName as the parameter. | Missed | Passed |
The instructions your model reads when the skill loads.
Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via
GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.
Basic examples for testing the API.
Operating Mode (v1.9 three-tier):
get_scene_info, find_objects_by_name) run directly. Creators/mutators (create_cube, create_sphere, set_object_position, set_object_rotation, set_object_scale) are FullAuto — on MODE_RESTRICTED, run the grant protocol.delete_object (SkillOperation.Delete). It is reachable only under Bypass or via a user-managed Allowlist entry; the grant flow returns MODE_FORBIDDEN.Surface profile: this module's write skills count as GameObject authoring under another name, so both the guide and noSceneAuthoring profiles hide them and answer SURFACE_EXCLUDED — the exclusion cannot be bypassed by mode or Allowlist. Under guide, details.manualDoc points at manual-gameobject, which teaches these same primitive/transform steps by hand. The query skills stay available in every profile.
SURFACE_EXCLUDED has a second source beyond a hidden skill name: visible shell skills that replay a payload — batch_execute / batch_retry_failed (batch module) and the workflow undo/redo/revert skills (workflow module) — return the same code at execution time when the payload they are about to apply lands in a category the active profile withdraws, even though those shell skills are never themselves hidden.
DO NOT (common hallucinations):
sample_create is a simplified version of gameobject_create — prefer the full gameobject modulesample_hello / sample_ping are connectivity test skills onlyRouting:
gameobject moduleunity_skills.health()Create a cube primitive.
Parameters: x, y, z, name
Create a sphere primitive.
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.