unity-console
Skill7 starsChanged 7 months agoMITView on GitHub
Use when users want to capture, filter, or clear console logs.
In this repository34 other files it gives its agents.
- unity-mcp-skillsSkill
- unity-animatorSkill
- unity-assetSkill
- unity-cameraSkill
- unity-cinemachineSkill
- unity-cleanerSkill
- unity-componentSkill
- unity-editorSkill
- unity-eventSkill
- unity-gameobjectSkill
- unity-importerSkill
- unity-lightSkill
- unity-materialSkill
- unity-navmeshSkill
- unity-optimizationSkill
- unity-packageSkill
- unity-perceptionSkill
- unity-physicsSkill
- unity-prefabSkill
- unity-probuilderSkill
- unity-projectSkill
- unity-sceneSkill
- unity-scriptableobjectSkill
- unity-scriptSkill
- unity-shaderSkill
- unity-smartSkill
- unity-terrainSkill
- unity-testSkill
- unity-timelineSkill
- unity-toolingSkill
- unity-uiSkill
- unity-uitoolkitSkill
- unity-validationSkill
- unity-xrSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read console entries / stack traces / errors → Unity_GetConsoleLogs or Unity_ReadConsole (native MCP)
- Distinctive: line 61
Start capturing Unity console logs.
- Distinctive: line 71
Write a custom log message.
- Distinctive: line 129
Start capture before play mode for runtime logs
- Distinctive: line 131
Use custom logs to mark AI agent actions
- Distinctive: line 133
Stop capture when done to free resources
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unity Console Skills
IMPORTANT: Do NOT use
Unity_RunCommandfor this module natively. Use the dedicated MCP tool for console. Seemcp-tools.md.
Work with the Unity console - capture logs, write messages, and debug your project.
Recipe path rule: ../../recipes/console/<command>.md
Common Mistakes
DO NOT (common hallucinations):
console_writedoes not exist → useconsole_log- For reading, filtering, or clearing console logs, use the native
Unity_GetConsoleLogsorUnity_ReadConsole— not a custom recipe.
Routing:
- Read console entries / stack traces / errors →
Unity_GetConsoleLogsorUnity_ReadConsole(native MCP) - Clear the console →
Unity_ReadConsole(clear action) - Compilation-status check →
editor_get_state(isCompilingfield) - Console settings (collapse, clear-on-play) →
console_set_collapse/console_set_clear_on_play(this module) - Scripting defines or forced recompile →
debug_get_defines,debug_set_defines,debug_force_recompile(this module)
Retained Debug Commands
The standalone debug module is gone. Three debug commands relevant to compilation and build configuration are retained here:
| Command | Description |
debug_force_recompile | Force script recompilation via AssetDatabase.Refresh + CompilationPipeline.RequestScriptCompilation |
debug_get_defines | Get scripting define symbols for the current build target group |
debug_set_defines | Set scripting define symbols for the current build target group |
Recipes: see ../../recipes/console/debug_force_recompile.md, debug_get_defines.md, debug_set_defines.md.
Skills Overview
| Skill | Description |
console_start_capture | Start capturing logs |
console_stop_capture | Stop capturing logs |
console_log | Write log message |
console_set_pause_on_error | Enable or disable Error Pause in Play mode |
console_export | Export console logs to a file |
console_get_stats | Get log statistics (count by type) |
console_set_collapse | Set console log collapse mode |
console_set_clear_on_play | Set clear on play mode |
debug_force_recompile | Force script recompilation |
debug_get_defines | Get scripting define symbols for current platform |
debug_set_defines | Set scripting define symbols for current platform |
Skills
console_start_capture
Start capturing Unity console logs.
No parameters.
console_stop_capture
Stop capturing logs.
No parameters.
console_log
Write a custom log message.
| Parameter | Type | Required | Default | Description |
message | string | Yes | - | Log message |
type | string | No | "Log" | Log/Warning/Error |
console_set_pause_on_error
Enable or disable Error Pause in Play mode.
| Parameter | Type | Required | Default | Description |
enabled | bool | No | true | Enable or disable error pause |
Returns: { success, enabled }
console_export
Export console logs to a file. Uses captured buffer when console_start_capture is active; otherwise reads directly from Unity Console history (no setup needed).
| Parameter | Type | Required | Default | Description |
savePath | string | No | "Assets/console_log.txt" | File path to save logs |
Returns: { success, path, count, source }
console_get_stats
Get log statistics (count by type). Uses captured buffer when console_start_capture is active; otherwise reads directly from Unity Console history.
No parameters.
Returns: { success, total, source, logs, warnings, errors, exceptions, asserts }
console_set_collapse
Set console log collapse mode.
| Parameter | Type | Required | Default | Description |
enabled | bool | Yes | - | Enable or disable collapse mode |
Returns: { success, setting, enabled }
console_set_clear_on_play
Set clear on play mode.
| Parameter | Type | Required | Default | Description |
enabled | bool | Yes | - | Enable or disable clear on play |
Returns: { success, setting, enabled }
Example Usage
See ../../recipes/console/<command>.md for per-command C# templates.
Best Practices
- Start capture before play mode for runtime logs
- Filter by Error to quickly find problems
- Use custom logs to mark AI agent actions
- Clear console before starting new capture session
- Stop capture when done to free resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

