check-unity
Monitors Unity console logs, recompiles scripts, and runs tests via MCP.
Install
mkdir -p .claude/skills/check-unity && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16786" && unzip -o skill.zip -d .claude/skills/check-unity && rm skill.zipInstalls to .claude/skills/check-unity
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.
Check Unity console for errors and warnings via MCPKey capabilities
- →Retrieve Unity console errors and warnings
- →Recompile Unity scripts and report results
- →Run Unity tests and summarize pass/fail status
- →Provide code snippets for errors referencing specific files
- →Report overall Unity status
How it works
The skill calls MCP functions to get console logs, recompile scripts, or run tests in Unity. It then processes the results, summarizes them, and provides relevant code snippets for errors.
Inputs & outputs
When to use check-unity
- →Check unity console
- →Recompile scripts
- →Run tests
About this skill
/check-unity — Unity Console Check
Check Unity console: $ARGUMENTS
Before Starting
Try calling get_console_logs first. If the MCP call fails or returns a connection error:
- Tell the user: "Unity MCP is not connected. Make sure Unity is open and the MCP server is running."
- Stop — do not attempt further MCP calls
Modes
Default (no argument) — errors + warnings
- Get errors:
get_console_logswith logType "error" - Get warnings:
get_console_logswith logType "warning" - Summarize: total count, grouped by type
recompile — recompile + check
- Call
recompile_scriptswith returnWithLogs true - Report compilation result
- If errors — show them grouped by file
tests — run tests
- Call
run_testswith testMode "EditMode" and returnOnlyFailures true - Report pass/fail summary
- For failures — show test name and reason
all — everything
- Recompile
- Check errors/warnings
- Run tests
After Reporting Errors
If errors reference specific files (e.g. NullReferenceException in PlayerController.cs:42):
- Read the file and show the relevant code snippet around the error line
- This helps the user understand the problem without switching to the editor
Output Format
Unity Console:
Errors: N
Warnings: N
[Details if any]
[Code snippets for errors, if file paths are available]
Status: ALL CLEAR / ACTION REQUIRED
When not to use it
- →If Unity MCP is not connected
- →If Unity is not open or the MCP server is not running
Limitations
- →Requires Unity MCP to be connected and running
- →Cannot directly fix errors, only report them
- →Relies on MCP for all Unity interactions
How it compares
This skill automates the process of checking Unity console logs, recompiling, and running tests via MCP, providing structured output and code snippets, unlike manual interaction with the Unity editor.
Compared to similar skills
check-unity side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| check-unity (this skill) | 0 | 3mo | No flags | Beginner |
| python-testing-patterns | 77 | 3mo | Review | Intermediate |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| bats | 9 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
performance-profiling
davila7
Performance profiling principles. Measurement, analysis, and optimization techniques.
obsidian-local-dev-loop
jeremylongshore
Configure Obsidian plugin development with hot-reload and fast iteration. Use when setting up development workflow, configuring test vaults, or establishing a rapid development cycle. Trigger with phrases like "obsidian dev loop", "obsidian hot reload", "obsidian development workflow", "develop obsidian plugin".