Develop, test, and improve Unity MCP Lens tools, packs, bridge behavior, package UI, and Unity editor automation workflows. Use when working on Lens itself, adding or debugging Lens MCP tools, changing tool packs, validating bridge behavior, or making Unity editor-authored persistent changes for Lens projects.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "unity-mcp-lens-development" with this command: npx skills add becool3000/skillsmp-becool3000-becool3000-unity-mcp-lens-development
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Use when Codex is working in a Unity project and needs the full Unity development workflow: beacon-first status checks, Lens bridge-authoritative editor access, explicit tool-pack selection, compile-idle gating, play-mode verification, runtime probes, autoplay smoke tests, screenshot-assisted validation, or edit-mode versus play-mode ownership-drift diagnosis.
Use when Codex is working in a Unity project and needs to verify, diagnose, or recover the local Unity MCP bridge before touching Unity editor state. Prefer the owned unity-mcp-lens stdio server, beacon-first status checks, event-driven manifest awareness, and explicit user escalation only when Unity or the bridge really needs intervention.
Design a shared family calendar system that actually works. Platform-agnostic, color-coded, with entry standards and sync rituals.
Detailed history, economy, and cultural insights of Budapest, Hungary, highlighting its thermal baths, tech innovation, and role in Eastern European developm...