unity-component

Add, remove, list, copy, and configure Unity components on GameObjects.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mufengbufeng/EF --skill unity-component-mufengbufeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-component
Source: https://github.com/mufengbufeng/EF/tree/main/UnityProject/.claude/skills/unity-skills/skills/component
Command: npx skills add https://github.com/mufengbufeng/EF --skill unity-component-mufengbufeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity developers need a reliable, repeatable way to add, remove, list, copy, and configure components on GameObjects without writing repetitive code for each object.

Core Features & Use Cases

  • Add, remove, list, copy, and configure components on single GameObjects
  • Batch operations to modify multiple GameObjects efficiently
  • Ability to target by name, instanceId, or path, with at least one identifier required
  • Supports common component types such as Rigidbody, Collider, AudioSource, and custom scripts

Quick Start

Add a Rigidbody component to a GameObject named Player and ensure it is enabled.

Frequently Asked Questions about unity-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch add Unity components to multiple GameObjects at once?

Batch add Unity components to multiple GameObjects using component_add_batch operations. This function targets objects by name, instanceId, or path to apply Rigidbody, Collider, or custom scripts efficiently without repetitive manual code.

Can I configure Unity Rigidbody properties across several GameObjects simultaneously?

Configure Unity Rigidbody properties simultaneously using component_set_property_batch. It updates multiple GameObjects efficiently by targeting them via name, instanceId, or path, ensuring consistent component configuration without manual repetition.

What is the best way to copy a Unity component configuration to another GameObject?

Copy Unity component configurations using the component_copy operation. It duplicates component settings to another GameObject by targeting the source and destination objects via name, instanceId, or path for reliable configuration replication.

Does Unity component automation require an identifier for every object operation?

Unity component automation requires at least one identifier per operation. You must target GameObjects strictly by name, instanceId, or path, and use exact componentType names to successfully execute component add, remove, or list actions.

Why should I use component_get_properties before modifying Unity components?

Use component_get_properties to inspect Unity components before modifying them. This ensures you verify existing component configurations and exact property names, preventing errors before executing component_set_property or component_remove operations.

When should I not use batch operations for Unity component management?

Avoid Unity component batch operations when managing a single object. For individual GameObjects, use standard component_add, component_remove, or component_set_property actions instead of batch variants to prevent unintended multi-object modifications.