skills/bash-install/SKILL.md
Use this skill when the user needs to install a CLI tool, library, runtime, or dependency on their machine or CI environment — handles package manager selection, auto-retry with fallback strategies, and post-install verification. Use it even when the user just says "I need X set up" or "get me Y installed" without specifying how. Do not use for npm/pip install of project dependencies managed by a package file — those are standard tool calls.
npx skillsauth add cuozg/oh-my-skills bash-installInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Install a tool or dependency using the appropriate package manager, with retry logic, fallback strategies, and post-install verification.
which {tool}, {tool} --version, or smoke testInstallation report: tool name, method used, version installed, verification result (pass/fail), and any fallback steps taken.
references/install-strategies.md — retry patterns, fallback chains, verification commandsLoad references on demand via read_skill_file("bash-install", "references/{file}").
tools
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
tools
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
tools
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
development
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.