unity-light
Create and configure Unity lights
Install / Use
npx skills add Besty0728/Unity-Skills --skill lightInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of unity-light
unity-light scores 86/100 on our quality scale, 2395th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 11 KB long, well organised into 24 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 1,781 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so unity-light is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
unity-light compared with similar skills
All 4 of these similar skills score higher than unity-light; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| unity-light (this skill)by Besty0728 | 86 | 1.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install unity-light?
- Run
npx skills add Besty0728/Unity-Skills --skill unity-light. The install tabs above show the steps for each supported agent. - Which AI agents does unity-light work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is unity-light safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is unity-light still maintained?
- The repository was last updated about 2 months ago, so unity-light is actively maintained.
Skill content
View source on GitHubname: unity-light description: Create and configure Unity lights
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.
Triggers
- Adding or tuning lights
- Setting up scene lighting
- Batch-enabling/disabling lights
- 添加或调校灯光、布置场景照明、批量开关灯光
Unity Light Skills
BATCH-FIRST: Use
*_batchskills when operating on 2+ lights.
Operating Mode
- Approval (default): mutating skills (
light_create,light_set_properties,light_set_properties_batch,light_set_enabled,light_set_enabled_batch,light_add_probe_group,light_add_reflection_probe) need user grant; grant triggers a single server-side execution that returns the result. - Auto / Bypass: those skills execute directly.
- Query skills (
light_get_info,light_get_properties,light_find_all,light_get_lightmap_settings) areSkillMode.SemiAuto— they run in all three modes without grant. - This module contains no Delete / PlayMode / Reload / high-risk skills (no NeverInSemi); to remove a Light, call
gameobject_deletefrom thegameobjectmodule.
Guardrails
DO NOT (common hallucinations):
light_adddoes not exist → uselight_create(creates a new light GameObject)light_set_color/light_set_intensitydo not exist → uselight_set_properties(sets color, intensity, range, shadows together)light_deletedoes not exist → usegameobject_deleteon the light's GameObjectlight_set_shadowdoes not exist → uselight_set_propertieswith theshadowsparametershadowsvalues are the Unity enum membersNone/Hard/Soft. Input is matched case-insensitively ("soft"still works) but responses always echo the capitalised form, so compare againstSoft, notsoft, when verifying
Routing:
- For lightmap baking settings →
light_get_lightmap_settings(this module) - For reflection probes →
light_add_reflection_probe(this module) - For light probe groups →
light_add_probe_group(this module)
Object Targeting: All single-object skills accept
name(string) andinstanceId(int, preferred). Provide at least one.path(hierarchy path) is also accepted where noted.
Skills Overview
| Single Object | Batch Version | Use Batch When |
|---------------|---------------|----------------|
| light_set_properties | light_set_properties_batch | Configuring 2+ lights |
| light_set_enabled | light_set_enabled_batch | Toggling 2+ lights |
No batch needed:
light_create- Create a lightlight_get_info- Get light information (light_get_propertiesis an alias of it)light_find_all- Find all lights (returns list)light_add_probe_group- Add a Light Probe Group with optional grid layoutlight_add_reflection_probe- Create a Reflection Probe at a positionlight_get_lightmap_settings- Inspect Lightmap baking settings
Light Types
| Type | Description | Use Case |
|------|-------------|----------|
| Directional | Parallel rays, no position | Sun, moon |
| Point | Omnidirectional from a point | Torches, bulbs |
| Spot | Cone-shaped beam | Flashlights, spotlights |
| Area | Rectangle/disc (baked only) | Windows, soft lights |
Skills
light_create
Create a new light.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| name | string | No | "New Light" | Light name |
| lightType | string | No | "Point" | Directional/Point/Spot/Area |
| x, y, z | float | No | 0,3,0 | Position |
| r, g, b | float | No | 1,1,1 | Color (0-1) |
| intensity | float | No | 1 | Light intensity |
| range | float | No | 10 | Range (Point/Spot) |
| spotAngle | float | No | 30 | Cone angle (Spot only) |
| shadows | string | No | "Soft" | None / Hard / Soft |
Returns: {success, name, instanceId, lightType, position, color, intensity, shadows}
light_set_properties
Configure light properties. Every parameter is optional and omitted ones keep their current value.
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| name | string | No* | Light object name |
| instanceId | int | No* | Instance ID (preferred) |
| path | string | No* | Hierarchy path |
| r, g, b | float | No | Color (0-1); each channel defaults to the light's current value |
| a | float | No | Colour alpha (0-1) |
| intensity | float | No | Light intensity |
| range | float | No | Range (Point/Spot only) |
| spotAngle | float | No | Cone angle (Spot only) |
| shadows | string | No | None / Hard / Soft |
Returns: {success, name, applied, skipped, lightType, color, intensity, range, spotAngle, shadows} — applied lists the parameters that took effect, named exactly as you passed them (the colour channels appear individually as r, g, b, a, not lumped under color), and skipped the ones the light type cannot carry (a range on a Directional light, a spotAngle on anything but a Spot), each with the reason. A parameter in neither list was not supplied.
An unrecognised shadows value rejects the whole call with SEMANTIC_INVALID + validValues and applies nothing, so a typo can no longer leave a half-configured light behind.
light_set_properties_batch
Configure multiple lights. Each item accepts: name/instanceId/path (identifier) + r, g, b, a, intensity, range, shadows (all optional). A bad shadows value fails that item with SEMANTIC_INVALID + validValues and names the object in target; the other items still run.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| items | json string | Yes | - | JSON array of per-item objects (see example below) |
Returns: {success, totalItems, successCount, failCount, results: [{success, name}]}
unity_skills.call_skill("light_set_properties_batch", items=[
{"name": "Light1", "intensity": 2.0, "r": 1, "g": 0.9, "b": 0.8},
{"instanceId": 12345, "intensity": 1.5, "shadows": "soft"},
{"name": "Light3", "intensity": 2.0}
])
light_set_enabled
Enable or disable a light.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| name | string | No* | - | Light object name |
| instanceId | int | No* | - | Instance ID |
| path | string | No* | - | Hierarchy path |
| enabled | bool | No | true | Enable state |
Returns: {success, name, enabled}
light_set_enabled_batch
Enable or disable multiple lights.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| items | json string | Yes | - | JSON array of per-item objects (see example below) |
Returns: {success, totalItems, successCount, failCount, results: [{success, name, enabled}]}
unity_skills.call_skill("light_set_enabled_batch", items=[
{"name": "Torch1", "enabled": False},
{"name": "Torch2", "enabled": False},
{"name": "Torch3", "enabled": False}
])
light_get_info
Get detailed light information.
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| name | string | No* | Light object name |
| instanceId | int | No* | Instance ID |
| path | string | No* | Hierarchy path |
Returns: {name, entityId, instanceId, path, lightType, color, intensity, range, spotAngle, shadows, enabled, cullingMask, bounceIntensity}
light_get_properties
Alias of light_get_info — same parameters, same response. It exists because the setter is light_set_properties, so the matching getter name resolves instead of 404-ing.
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| name | string | No* | Light object name |
| instanceId | int | No* | Instance ID |
| path | string | No* | Hierarchy path |
Returns: identical to light_get_info.
light_find_all
Find all lights in scene.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| lightType | string | No | null | Filter by type |
| limit | int | No | 50 | Max results |
Returns: {count, lights: [{name, instanceId, path, lightType, intensity, enabled}]}
light_add_probe_group
Add a Light Probe Group to a GameObject. Optional grid layout: gridX/gridY/gridZ (count per axis), spacingX/spacingY/spacingZ (meters between probes).
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| name | string | No | null | GameObject name |
| instanceId | int | No | 0 | Instance ID |
| path | string | No | null | Hierarchy path |
| gridX | int | No | 0 | Probe count on X axis |
| gridY | int | No | 0 | Probe count on Y axis |
| gridZ | int | No | 0 | Probe count on Z axis |
| spacingX | float | No | 2 | Meters between probes on X |
| spacingY | float | No | 1.5 | Meters between probes on Y |
| spacingZ | float | No | 2 | Meters between probes on Z |
Returns: { success, gameObject, probeCount, existed, hasGrid }
light_add_reflection_probe
Create a Reflection Probe at a position.
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| probeName | string | No | "ReflectionProbe" | Probe name |
| x, y, z | float | No | 0,1,0 | Position |
| sizeX, sizeY, sizeZ | float | No | 10,10,10 | Probe box size |
| resolution | int | No | 256 | Cubemap resolution |
Returns: { success, name, instanceId, resolution, size }
light_get_lightmap_settings
Get Lightmap baking settings.
No parameters.
Returns: { success, bakedGI, realtimeGI, lightmapSize, lightmapPadding, isRunning, lightmapCount }
Example: Efficient Lighting Setup
import unity_skills
# BAD: 4 API calls
unity_skills.call_skill("light_set_properties", name="Light1", intensity=2.0)
unity_skills.call_skill("light_set_properties", name="Light2", intensity=2.0)
unity_skills.call_skill("light_set_properties", name="Light3", intensity=2.0)
unity_skills.call_skill("light_set_properties", name="Light4", intensity=2.0)
# GOOD: 1 API call
unity_skills.call_skill("light_set_properties_batch", items=[
{"name": "Light1", "intensity": 2.0},
{"name": "Light2", "intensity": 2.0},
{"name": "Light3", "intensity": 2.0},
{"name": "Light4", "intensity": 2.0}
])
Minimal Example
unity_skills.call_skill("light_create",
name="Sun", lightType="Directional",
r=1, g=0.95, b=0.85, intensity=1.2, shadows="soft"
)
Best Practices
- Use Directional light for main scene illumination
- Point lights for localized sources (lamps, fires)
- Spot lights for focused beams (flashlights, stage)
- Limit real-time shadows for performance
- Area lights require baking (not real-time)
- Use intensity > 1 for HDR/bloom effects
Exact Signatures
Exact names, parameters, defaults, and returns are defined by GET /skills/schema or unity_skills.get_skill_schema(), not by this file.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
