Agent skill
research-highrise-studio-lua-api
Dive into the Highrise Studio Lua API docs and answer questions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/product/research-highrise-studio-lua-api
SKILL.md
Research the Highrise Studio Lua API
Parse and synthesize the Highrise Studio API docs, which describe the Lua API available to Highrise Studio projects. The docs are contained in YAML files cloned from a public repo. The YAML files are formatted like:
name:
type:
summary:
code_samples:
inherits:
tags:
constructors:
- name:
summary:
is_static:
code_samples:
tags:
parameters:
- name:
type:
tags:
default:
summary:
returns:
- type:
summary:
properties:
- name:
summary:
is_static:
code_samples:
tags:
type:
methods:
- name:
summary:
is_static:
code_samples:
tags:
parameters:
- name:
type:
tags:
default:
summary:
returns:
- type:
summary:
math_operations:
- operation:
summary:
type_a:
type_b:
return_type:
code_samples:
tags:
Instructions
1. Find the Studio API docs locally
The Highrise Studio docs exist in a public repo, and should be downloaded locally to the active project under .claude/creator-docs. If not, alert the user that something has gone wrong and abort.
2. Understand the question
Identify classes and keywords that might be relevant to the incoming question. Does it refer to a specific type? Is it about a Lua script? Is it about a specific property or method?
3. Read relevant file(s)
Peruse potentially-useful YAML files in creator-docs/pages/learn/studio-api and its subfolders. Use built-in tools like Read and command-line tools like grep, ls, find, tree, etc. to discover potentially-relevant content and read files as needed.
4. Succinctly respond to the question
Synthesize the relevant files into a terse, precise answer to the incoming question. Provide summaries, parameters, return types, overloads, and code examples. Correct any misunderstandings that may be present in the question. If you cannot find an answer, tell the asker and briefly list any related topics that might be helpful to them.
Examples
Example 1: Player Position
User: "How do I get a player's position?"
- Check if
creator-docshas already downloaded locally. If not, inform and abort. - Identify relevant searches:
- "Player"
- "position"
- Search the codebase and read any relevant results, continuing to search any connected files if needed:
ls **/Player*.yamlgrep -r "position" pages/learn/studio-apicat pages/learn/studio-api/classes/Character.yaml
- Provide a concise answer:
Each
Playerobject is associated with aCharacter.Characteris a Unity component, so its position can be read via.transform.position.lua-- Assuming there is a Player instance named player local playerPosition = player.character.transform.position
Example 2: Networked Values
User: "What types of networked values are available?"
- Check if
creator-docshas already downloaded locally. If not, inform and abort. - Identify relevant searches:
- "network*value"
- "inherits: *Network*Value"
- Search the codebase and read any relevant results, continuing to search any connected files if needed:
grep -r "Network*Value" pages/learn/studio-apigrep -r "inherits" -A 1 pages/learn/studio-api | grep "Class.NetworkValue"
- Provide a concise answer:
There are 9 networked value types:
- IntValue
- NumberValue
- StringValue
- BoolValue
- TableValue
- Vector2Value
- Vector3Value
- QuaternionValue
- NetworkObjectValue
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?