gameobject-component-list-all
A utility to browse and search Unity UnityEngine.Component classes.
Install
mkdir -p .claude/skills/gameobject-component-list-all && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15882" && unzip -o skill.zip -d .claude/skills/gameobject-component-list-all && rm skill.zipInstalls to .claude/skills/gameobject-component-list-all
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
List C# class names extended from UnityEngine.Component. Use this to find component type names for 'gameobject-component-add' tool. Results are paginated to avoid overwhelming responses.Key capabilities
- →List C# class names extended from UnityEngine.Component
- →Search for specific component class names
- →Paginate results for component listings
How it works
The skill lists C# class names that extend from UnityEngine.Component, with options for searching and pagination.
Inputs & outputs
When to use gameobject-component-list-all
- →Find component class names
- →Search Unity components
- →List available components
About this skill
GameObject / Component / List All
How to Call
unity-mcp-cli run-tool gameobject-component-list-all --input '{
"search": "string_value",
"page": 0,
"pageSize": 0
}'
For complex input (multi-line strings, code), save the JSON to a file and use:
unity-mcp-cli run-tool gameobject-component-list-all --input-file args.jsonOr pipe via stdin (recommended):
unity-mcp-cli run-tool gameobject-component-list-all --input-file - <<'EOF' {"param": "value"} EOF
Troubleshooting
If unity-mcp-cli is not found, either install it globally (npm install -g unity-mcp-cli) or use npx unity-mcp-cli instead.
Read the /unity-initial-setup skill for detailed installation instructions.
Input
| Name | Type | Required | Description |
|---|---|---|---|
search | string | No | Substring for searching components. Could be empty. |
page | integer | No | Page number (0-based). Default is 0. |
pageSize | integer | No | Number of items per page. Default is 5. Max is 500. |
Input JSON Schema
{
"type": "object",
"properties": {
"search": {
"type": "string"
},
"page": {
"type": "integer"
},
"pageSize": {
"type": "integer"
}
}
}
Output
Output JSON Schema
{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/com.IvanMurzak.Unity.MCP.Editor.API.Tool_GameObject+ComponentListResult"
}
},
"$defs": {
"System.String[]": {
"type": "array",
"items": {
"type": "string"
}
},
"com.IvanMurzak.Unity.MCP.Editor.API.Tool_GameObject+ComponentListResult": {
"type": "object",
"properties": {
"Items": {
"$ref": "#/$defs/System.String[]",
"description": "Array of component type names for the current page."
},
"Page": {
"type": "integer",
"description": "Current page number (0-based)."
},
"PageSize": {
"type": "integer",
"description": "Number of items per page."
},
"TotalCount": {
"type": "integer",
"description": "Total number of matching components."
},
"TotalPages": {
"type": "integer",
"description": "Total number of pages available."
}
},
"required": [
"Page",
"PageSize",
"TotalCount",
"TotalPages"
]
}
},
"required": [
"result"
]
}
When not to use it
- →When looking for C# classes not extended from UnityEngine.Component
- →When the user is not trying to find component type names for 'gameobject-component-add' tool
Limitations
- →Only lists C# class names extended from UnityEngine.Component
- →Results are paginated with a maximum page size of 500
How it compares
This skill provides a structured, paginated list of component names, which is more efficient than manually browsing or guessing component types.
Compared to similar skills
gameobject-component-list-all side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gameobject-component-list-all (this skill) | 0 | 3mo | Review | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| dev-browser | 53 | 4mo | Review | Intermediate |
| playwright-browser-automation | 29 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
dev-browser
SawyerHood
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
windows-ui-automation
martinholovsky
Expert in Windows UI Automation (UIA) and Win32 APIs for desktop automation. Specializes in accessible, secure automation of Windows applications including element discovery, input simulation, and process interaction. HIGH-RISK skill requiring strict security controls for system access.
unity-mcp-orchestrator
CoplayDev
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
agent-browser
vercel-labs
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.