Agent-Skills.md

Agent Skills: uloop get-logs

Check Unity Console logs. Use when: checking logs, debugging errors, investigating failures, or when user asks about console output. Key options: --log-type (Error/Warning/Log/All), --max-count, --search-text. Retrieves errors, warnings, and Debug.Log messages.

UncategorizedID: hatayama/uLoopMCP/uloop-get-logs

Repository

hatayama/uLoopMCP
hatayamaLicense: MIT
13613

Install this agent skill to your local

pnpm dlx add-skill https://github.com/hatayama/uLoopMCP/tree/HEAD/.claude/skills/uloop-get-logs

Skill Files

Browse the full folder contents for uloop-get-logs.

Download Skill

Loading file tree…

.claude/skills/uloop-get-logs/SKILL.md

Skill Metadata

Name
uloop-get-logs
Description
"Check Unity Console logs. Use when: checking logs, debugging errors, investigating failures, or when user asks about console output. Key options: --log-type (Error/Warning/Log/All), --max-count, --search-text. Retrieves errors, warnings, and Debug.Log messages."

uloop get-logs

Retrieve logs from Unity Console.

Usage

uloop get-logs [options]

Parameters

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | --log-type | string | All | Log type filter: Error, Warning, Log, All | | --max-count | integer | 100 | Maximum number of logs to retrieve | | --search-text | string | - | Text to search within logs | | --include-stack-trace | boolean | false | Include stack trace in output | | --use-regex | boolean | false | Use regex for search | | --search-in-stack-trace | boolean | false | Search within stack trace |

Global Options

| Option | Description | |--------|-------------| | --project-path <path> | Target a specific Unity project (mutually exclusive with --port). Path resolution follows the same rules as cd — absolute paths are used as-is, relative paths are resolved from cwd. | | -p, --port <port> | Specify Unity TCP port directly (mutually exclusive with --project-path). |

Examples

# Get all logs
uloop get-logs

# Get only errors
uloop get-logs --log-type Error

# Search for specific text
uloop get-logs --search-text "NullReference"

# Regex search
uloop get-logs --search-text "Missing.*Component" --use-regex

Output

Returns JSON array of log entries with message, type, and optional stack trace.