plugins/cache/omc/oh-my-claudecode/4.8.2/skills/setup/SKILL.md
Unified setup entrypoint for install, diagnostics, and MCP configuration
npx skillsauth add moliboy5000/.claude setupInstall 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.
Use /oh-my-claudecode:setup as the unified setup/configuration entrypoint.
/oh-my-claudecode:setup # full setup wizard
/oh-my-claudecode:setup doctor # installation diagnostics
/oh-my-claudecode:setup mcp # MCP server configuration
/oh-my-claudecode:setup wizard --local # explicit wizard path
Route by the first argument:
wizard, local, global, or --force -> run /oh-my-claudecode:omc-setup {{ARGUMENTS}}doctor -> run /oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}mcp -> run /oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}Examples:
/oh-my-claudecode:omc-setup {{ARGUMENTS}}
/oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}
/oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}
/oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup remain valid compatibility entrypoints./oh-my-claudecode:setup in new documentation and user guidance.Task: {{ARGUMENTS}}
development
Configure Claude Octopus providers and preferences. Use when: Use this skill when the user wants to "configure Claude Octopus", "setup octopus",. "configure providers", "set up API keys for octopus", or mentions octopus configuration.
tools
Zero-context implementation plans with bite-sized tasks. Use when: Use when you have a spec or requirements for a multi-step task.. Auto-invoke when user says "plan how to implement X", "create implementation plan", . "break down this feature into tasks".
content-media
Process screenshot-based UI/UX feedback to fix visual issues. Use when: AUTOMATICALLY ACTIVATE when user provides visual feedback:. "[Image X] The /settings should be Y". "[Image X] these button styles need to be fixed"
testing
Verify claims with actual evidence before declaring success — use to prevent false completion. Use when: Use when about to claim work is complete, fixed, or passing.. Auto-invoke before: commits, PRs, task completion, moving to next task.. ALWAYS use before expressing satisfaction ("Done!", "Fixed!", "All passing!").