npx skills add smithery/hatayama --skill uloop-get-logs
hatayama/unity-cli-loop
uloop-get-logs
Read current Unity Console entries from a running Editor. Use during bug investigation after compile, tests, PlayMode, dynamic code, or immediately after `uloop-pause-point`.
Installation
npx skills add hatayama/unity-cli-loop --skill uloop-get-logs
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…
566.3K installsAzure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
510K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsAlso in this package
Other skills from hatayama/unity-cli-loop · top by installs.
npx skills add hatayama/unity-cli-loop
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,372 B -
docs
SUMMARY.md196 B
History
- First seen on skills.sh
- First recorded snapshot · 39 installs
SKILL.md
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 |
flag | - | Include stack trace in output |
--use-regex |
flag | - | Use regex for search |
--search-in-stack-trace |
flag | - | Search within stack trace |
Output
Returns JSON with:
TotalCount(number): Total logs available before max-count clippingDisplayedCount(number): Logs returned in this response (≤--max-count)- Input filters (
LogType,MaxCount,SearchText,IncludeStackTrace) are echoed back in the response Logs(array): Each entry has:
- Type (string): "Error", "Warning", or "Log" - Message (string): Log message body - StackTrace (string): Stack trace text. Empty when --include-stack-trace is false.