oc-setup

Install the oc-browser plugin globally with Docker checks and CLI symlinks.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill oc-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oc-setup
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/oc-browser/skills/oc-setup
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill oc-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature provides a one-time global installation workflow for the oc-browser plugin, including Docker prerequisite checks, image building, and CLI tool setup, so users can reliably enable oc-browser across projects.

Core Features & Use Cases

  • Idempotent global install that validates Docker readiness and creates symlinks for oc-as, oc-list, oc-rm, and oc.
  • Phase-driven workflow (preflight, install, smoke test) to ensure a consistent setup and quick verification.
  • Use Case: An engineer wants to enable oc-browser in their environment and prepare per-project state for on-demand deployments via oc-as.

Quick Start

Run the preflight checks, execute the install script, and perform the smoke test to verify oc-browser is installed and on PATH.

Frequently Asked Questions about oc-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the oc-browser plugin globally for CLI automation?▼

Setting up oc-browser requires Docker to be running, as the installation process validates Docker prerequisites before building the container image and symlinking the oc-as, oc-list, oc-rm, and oc CLI tools globally.

Can I run oc-setup if Docker is not installed or running?▼

No, the oc-browser installation cannot proceed without Docker, because the setup workflow executes preflight checks to validate Docker readiness before attempting to build the required image and create CLI symlinks.

What happens if I run the oc-browser installation script more than once?▼

Running the oc-browser installation script multiple times is safe because it implements an idempotent workflow, meaning preflight checks, image building, and symlink creation can be repeated without causing errors or duplicate configurations.

How do I verify that the oc-browser CLI setup completed successfully?▼

You can verify the oc-browser CLI setup by checking the post-install report and confirming the automated smoke test passed, which ensures the oc-as, oc-list, oc-rm, and oc commands are correctly installed and available on your PATH.

When do I need to set up oc-browser for per-project deployments?▼

You need to set up oc-browser when you want to enable on-demand deployments via oc-as, which creates per-project state lazily after the one-time global installation and CLI symlinking is complete.