Files
opencode-power-pack/docs/index.md
T

4.5 KiB

OpenCode Power Pack Installation and Operations

This guide covers selective npm installation and native host installation for OpenCode Power Pack v0.4.0.

Choose an installation path

Use the selective npm installer when Codex, OpenCode, or Pi should load only chosen skills or a curated profile. It requires Node.js 20 or newer and installs into a portable .agents/skills directory.

Use the host-native plugin or package installation when you want the full catalog and native activation behavior. Claude Code, Codex, OpenCode, and Pi each use their own host mechanism.

Selective npm commands

# List skills and profiles
npx @waybarrios/opencode-power-pack list

# Install one or several skills at user scope
npx @waybarrios/opencode-power-pack install code-review
npx @waybarrios/opencode-power-pack install code-review security-review

# Install at repository scope
npx @waybarrios/opencode-power-pack install code-review --project

# Preview and install a profile
npx @waybarrios/opencode-power-pack install --profile review --dry-run
npx @waybarrios/opencode-power-pack install --profile review

# Install all 54 skills
npx @waybarrios/opencode-power-pack install --all

The installer resolves required companion skills. Existing skills are not overwritten unless --force is supplied. Use --dry-run before any forced update.

Agent-assisted installation

A terminal-capable Codex, OpenCode, or Pi agent can install the recommended profile at project scope with a dry-run-first sequence:

npx @waybarrios/opencode-power-pack install --profile recommended --project --dry-run
npx @waybarrios/opencode-power-pack install --profile recommended --project

The full safe prompt, host routing rules, and verification checklist are available at https://skills.waybarrios.com/agent-install.md. Claude Code should use the native plugin commands below instead of assuming support for the portable .agents/skills path.

Host setup and invocation

Claude Code

/plugin marketplace add waybarrios/opencode-power-pack
/plugin install opencode-power-pack@opencode-power-pack

Invoke a skill with its namespace, for example /opencode-power-pack:code-review.

Codex

codex plugin marketplace add waybarrios/opencode-power-pack --ref main
codex plugin add opencode-power-pack@opencode-power-pack
codex plugin list --marketplace opencode-power-pack

Start a new Codex session and invoke a skill such as $code-review.

OpenCode

opencode plugin --global "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.4.0"

Start a new OpenCode session and invoke a skill such as /code-review.

Pi

pi install git:github.com/waybarrios/opencode-power-pack

Restart Pi after installation so it reloads the package's declared skills directory.

Profiles

  • recommended: balanced software development.
  • review: comprehensive and focused review plus quality and differential review.
  • feature-dev: exploration, architecture, implementation, and review specialists.
  • frontend: frontend implementation plus anti-generic design critique.
  • security: AppSec review, scanning, modeling, validation, and reporting.
  • huggingface: model discovery, inference, training, evaluation, Spaces, and AWS deployment.
  • authoring: skills, MCP servers, and technical-paper summaries.
  • project-memory: durable AGENTS.md and CLAUDE.md maintenance.

Update and remove

Preview an npm-managed skill update, then apply it only if the destination is correct:

npx @waybarrios/opencode-power-pack install code-review --dry-run
npx @waybarrios/opencode-power-pack install code-review --force

For host-native installations, use that host's plugin or package update and removal commands. Avoid activating the same workflow from both a native plugin and an npm copy at the same scope.

Troubleshooting

  • If a new skill is missing, start a new host session and verify the expected .agents/skills destination.
  • If Claude Code reports a name collision, use the namespaced form.
  • If the installer refuses to overwrite a skill, preview with --dry-run and repeat with --force only when intended.
  • If an .opp-lock remains, first confirm no installer process is running, then remove only the exact stale lock path reported by the installer.
  • For reproducible issue reports, include the host, host version, command, destination scope, and complete error output.

Full HTML documentation: https://skills.waybarrios.com/docs/ Complete skill reference: https://skills.waybarrios.com/docs/skills/index.md