Files

835 lines
52 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Documentation | OpenCode Power Pack</title>
<meta
name="description"
content="Install and use OpenCode Power Pack Agent Skills and its opt-in native sandbox runner with Claude Code, Codex, OpenCode, and Pi."
>
<meta name="robots" content="index, follow, max-snippet:-1">
<meta name="theme-color" content="#0b0f14">
<link rel="canonical" href="https://skills.waybarrios.com/docs/">
<link rel="icon" href="../assets/favicon.svg" type="image/svg+xml">
<link rel="sitemap" type="application/xml" href="../sitemap.xml">
<link rel="describedby" type="text/markdown" href="../llms.txt" title="LLM project summary">
<link rel="alternate" type="text/markdown" href="index.md" title="Markdown version">
<meta property="og:type" content="article">
<meta property="og:locale" content="en_US">
<meta property="og:site_name" content="OpenCode Power Pack">
<meta property="og:title" content="OpenCode Power Pack Documentation">
<meta
property="og:description"
content="Installation and usage guides for 55 Agent Skills across Claude Code, Codex, OpenCode, and Pi."
>
<meta property="og:url" content="https://skills.waybarrios.com/docs/">
<meta
property="og:image"
content="https://skills.waybarrios.com/assets/social-card.png"
>
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:type" content="image/png">
<meta property="og:image:alt" content="OpenCode Power Pack installation and operations documentation">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="OpenCode Power Pack Documentation">
<meta name="twitter:description" content="Install and use 55 Agent Skills across Claude Code, Codex, OpenCode, and Pi.">
<meta name="twitter:image" content="https://skills.waybarrios.com/assets/social-card.png">
<meta name="twitter:image:alt" content="OpenCode Power Pack installation and operations documentation">
<meta name="twitter:image:width" content="1200">
<meta name="twitter:image:height" content="630">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link
href="https://fonts.googleapis.com/css2?family=Barlow+Condensed:wght@600;700;800&amp;family=IBM+Plex+Mono:wght@400;500;600;700&amp;display=swap"
rel="stylesheet"
>
<link rel="stylesheet" href="../styles.css?v=2026-10-19-opencode-2">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "OpenCode Power Pack Documentation",
"description": "Installation, usage, and native sandbox documentation for OpenCode Power Pack Agent Skills.",
"url": "https://skills.waybarrios.com/docs/",
"dateModified": "2026-10-27",
"author": {
"@type": "Person",
"name": "Wayner Barrios",
"url": "https://github.com/waybarrios"
},
"about": {
"@type": "SoftwareSourceCode",
"name": "OpenCode Power Pack",
"codeRepository": "https://github.com/waybarrios/opencode-power-pack",
"softwareVersion": "0.6.0",
"runtimePlatform": [
"Claude Code",
"Codex",
"OpenCode 1 and 2",
"Pi"
]
},
"breadcrumb": {
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "OpenCode Power Pack",
"item": "https://skills.waybarrios.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Documentation",
"item": "https://skills.waybarrios.com/docs/"
}
]
}
}
</script>
</head>
<body class="docs-body">
<a class="skip-link" href="#docs-main">Skip to documentation</a>
<div class="status-rail" aria-hidden="true">
<span>DOCUMENTATION // MAIN</span>
<span>55 MODULES</span>
<span>LAST UPDATED 2026-10-27</span>
</div>
<div class="docs-shell">
<aside class="docs-sidebar">
<a class="brand" href="../" aria-label="OpenCode Power Pack home">
<svg class="brand-bolt" viewBox="0 0 38 48" aria-hidden="true">
<path d="M22 1 3 27h14l-3 20 21-29H21z" />
</svg>
<span><b>POWER PACK</b> DOCS</span>
</a>
<nav aria-label="Documentation sections">
<a href="#opencode-2">OpenCode 2.0 + updates</a>
<a href="#quick-start">Choose an install</a>
<a href="#npm">Selective npm</a>
<a href="#agent-install">Agent-assisted install</a>
<a href="#cli">CLI reference</a>
<a href="#sandbox">Sandbox runner</a>
<a href="#how-skills-work">How skills work</a>
<a href="#hosts">Full host installs</a>
<a href="#profiles">Profiles + contents</a>
<a href="skills/">All 55 skills</a>
<a href="#reviews">Review skills</a>
<a href="#maintenance">Update and remove</a>
<a href="#troubleshooting">Troubleshooting</a>
</nav>
<a class="back-link" href="../">← Back to overview</a>
</aside>
<main class="docs-content" id="docs-main">
<header>
<nav class="breadcrumbs" aria-label="Breadcrumb">
<a href="../">OpenCode Power Pack</a>
<span aria-hidden="true">/</span>
<span aria-current="page">Documentation</span>
</nav>
<p class="eyebrow">[ INSTALLATION + OPERATIONS ]</p>
<h1>Documentation</h1>
<p>
Start with the installation model, then choose a profile or individual workflow. This guide
explains destinations, dependency resolution, host activation, contained command execution,
verification, updates, removal, and the purpose of every bundled skill.
</p>
</header>
<section class="docs-section" id="opencode-2">
<h2>OpenCode 2.0 and current source</h2>
<p>Release v0.6.0 adds OpenCode 2.0 support on npm and Git. Tag v0.5.0 and npm 0.5.0 contain the earlier V1-only plugin.</p>
<p>The npm installer can also copy skills for OpenCode 2. Copying skills does not register the three named specialists.</p>
<p>Smoke tests cover OpenCode 1.18.7, 2.0.14, and 2.0.32. The current suite has 419 tests; the latest local run passed 418 and skipped the optional native sandbox integration.</p>
<p>For the host commands and permission checks, see <a href="#host-opencode">OpenCode setup</a>. For the new writing workflow, see <a href="skills/#humanizer">humanizer</a>.</p>
</section>
<section class="docs-section" id="quick-start">
<h2>Choose an installation path</h2>
<p>Choose selected skills from npm or the full plugin. Both sources ship v0.6.0.</p>
<div class="install-choice-grid">
<article>
<span>SELECTIVE</span>
<h3>npm installer</h3>
<p>Best when Codex, OpenCode, or Pi should load only the workflows you select.</p>
<ul>
<li>Install one skill, several skills, a profile, or the released catalog.</li>
<li>Choose user-level or repository-local scope.</li>
<li>Requires Node.js 20.11.0 or newer.</li>
</ul>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile recommended</code></div>
<a href="#npm">Follow the selective guide →</a>
</article>
<article>
<span>COMPLETE CATALOG</span>
<h3>Native host plugin</h3>
<p>Best when you want all 55 workflows through the host's normal package manager.</p>
<ul>
<li>Claude Code receives collision-safe namespaced skills.</li>
<li>Codex, OpenCode, and Pi receive native package integration.</li>
<li>Updates are managed by the host.</li>
</ul>
<div class="docs-code"><code># Choose your host below
/plugin install ...
codex plugin add ...
opencode plugin ...
pi install ...</code></div>
<a href="#hosts">Choose a host →</a>
</article>
</div>
<p class="note">
Installing the full native plugin and copying the same skills with npm does not make the
catalog smaller. Prefer one activation path for a given host and scope.
</p>
</section>
<section class="docs-section" id="npm">
<h2>Selective npm installer</h2>
<ol class="installation-steps">
<li>
<h3>Inspect the catalog</h3>
<p>This prints the profiles and skill IDs in the published npm package. It does not modify files.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack list</code></div>
</li>
<li>
<h3>Select skills or a profile</h3>
<p>Pass any number of skill IDs, or use one or more repeatable <code>--profile</code> flags.</p>
<div class="docs-code"><code># One skill
npx @waybarrios/opencode-power-pack install code-review
# Several skills
npx @waybarrios/opencode-power-pack install code-review security-review
# A curated profile
npx @waybarrios/opencode-power-pack install --profile review
# Combine a profile with another skill
npx @waybarrios/opencode-power-pack install --profile frontend code-quality</code></div>
<p><a href="skills/">Compare all 55 skills and copy individual commands →</a></p>
</li>
<li>
<h3>Choose the destination</h3>
<p>
The default <code>--global</code> scope writes to <code>~/.agents/skills</code> for your
user. <code>--project</code> finds the current Git root and writes to
<code>&lt;repo&gt;/.agents/skills</code> so the selection travels with one repository.
</p>
<div class="docs-code"><code># User-level, the default
npx @waybarrios/opencode-power-pack install code-review --global
# Current Git repository only
npx @waybarrios/opencode-power-pack install --profile review --project</code></div>
</li>
<li>
<h3>Preview, install, and restart</h3>
<p>Use <code>--dry-run</code> first when you want to inspect the resolved selection.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile security --dry-run
npx @waybarrios/opencode-power-pack install --profile security</code></div>
<p>Start a new Codex, OpenCode, or Pi session if the newly copied skills do not appear automatically.</p>
</li>
</ol>
<h3>What the installer copies</h3>
<p>
Each selected directory is copied intact, including its <code>SKILL.md</code>, references,
scripts, or assets. The installer also attaches <code>UPSTREAMS.json</code>, third-party
notices, and license texts to every copied skill. Declared companion skills are resolved
recursively and added automatically.
</p>
<p class="note">
Existing directories are skipped by default. <code>--force</code> stages the replacement,
locks the skill, preserves a rollback copy during promotion, and restores it if promotion fails.
</p>
</section>
<section class="docs-section" id="github-packages">
<h2>GitHub Packages mirror</h2>
<p>npmjs is the public install source and does not require GitHub authentication. The released package is also available through GitHub Packages.</p>
<p>For the mirror, use a GitHub personal access token (classic) with <code>read:packages</code>:</p>
<div class="docs-code"><code>npm login --scope=@waybarrios --auth-type=legacy --registry=https://npm.pkg.github.com
npm install --global @waybarrios/opencode-power-pack --registry=https://npm.pkg.github.com</code></div>
<p>The mirror follows release tags. It does not include additions that are only on main.</p>
</section>
<section class="docs-section" id="agent-install">
<h2>Let your agent install it</h2>
<p>
Paste the prompt below into a terminal-capable Codex, OpenCode, or Pi session. It makes the
agent ask what you need, recommend the smallest useful selection, and preview the exact destination
and dependency closure before writing project-local skills.
It does not modify <code>package.json</code> or add an application runtime dependency.
</p>
<article class="agent-install-panel">
<header><span>AGENT PROMPT</span><b>SAFE PROJECT INSTALL</b></header>
<div class="docs-code"><code id="agent-install-prompt">Help me choose and install the right OpenCode Power Pack skills safely and project-locally in the current Git repository.
Your goal is to understand what I need, recommend the smallest useful profile or set of individual skills, obtain my explicit selection, install it for the active coding-agent host, preserve all existing project work, and leave a reproducible verification report.
The npm procedure below copies skills from the published catalog. It does not register the native OpenCode plugin or its three specialists. If I need the plugin, show the OpenCode install guide and wait for my choice before continuing.
Safety rules:
1. Do not modify package.json, package-lock.json, npm-shrinkwrap.json, pnpm-lock.yaml, yarn.lock, bun.lock, or application dependencies.
2. Do not use --force, --global, --all, sudo, destructive Git commands, or manual deletion/replacement of existing skill directories. Do not choose a profile or skill for me, and do not install anything before I explicitly approve the selection.
3. Do not clean, reset, stash, commit, or push the user's worktree. Existing changes belong to the user.
4. Do not create or modify repository files outside the resolved project-local .agents/skills directory. npm/npx may use its normal user cache, but must not add the package to this project's dependencies.
5. Stop and report the exact command, exit code, and error if a prerequisite, network request, permission check, or installer step fails. Do not bypass a failure with broader permissions or different flags.
Phase 1: detect the host and choose one installation path.
- If the active host is Claude Code, do not run the portable npm installer. Explain that Claude Code should use the collision-safe native plugin, then show these commands exactly:
/plugin marketplace add waybarrios/opencode-power-pack
/plugin install opencode-power-pack@opencode-power-pack
After the user runs them, tell them to run /reload-plugins if prompted, verify the plugin with /plugin, and test /opencode-power-pack:code-review. Report this Claude-specific plan and stop.
- If the active host is Codex, OpenCode, or Pi, continue with the portable project-local selection procedure below.
- If the host cannot be determined confidently, stop and ask which host is active. Do not guess from repository files alone.
Phase 2: preflight without changing repository files.
1. Print the current directory with pwd.
2. Run git rev-parse --show-toplevel. Stop if this is not a Git repository. Save the absolute Git root.
3. Run node --version. Parse the full version and require Node.js 20.11.0 or newer. If it is older or unavailable, stop and explain how to satisfy the prerequisite without changing this project.
4. Run npm --version and stop if npm or npx is unavailable.
5. Capture git status --short before installation. Use it only as a baseline; do not alter any listed file.
6. State that the only permitted destination is &lt;git-root&gt;/.agents/skills.
Phase 3: discover my needs and obtain an explicit selection.
1. Run npx @waybarrios/opencode-power-pack list to read the current profiles and skill IDs from the published package. Treat that output as authoritative; do not invent names.
2. Ask what I want to accomplish, what kind of repository I am working in, and whether I prefer a broad workflow pack or only the minimum individual skills. Wait for my answer.
3. Map my answer to at most three clear options. Consider these curated profiles when relevant: `recommended` for a balanced starter set, `review` for PR and bug review, `feature-dev` for structured feature delivery, `frontend` for interface work, `security` for application-security workflows, `huggingface` for Hugging Face and ML work, `authoring` for creating skills and MCP servers, and `project-memory` for improving agent instruction files. Individual skill IDs may be selected instead of a profile, and profiles may be combined only when the need clearly requires both.
4. For each option, state the exact profile flags or skill IDs, what it enables, important companion skills it may resolve, and the tradeoff in installed scope. Recommend the smallest option that fully addresses my stated goal.
5. Ask me to choose or modify the proposed selection. Wait for explicit approval. Do not treat silence or a vague acknowledgement as approval.
6. Convert the approved choice into `&lt;approved-selection&gt;`, using one or more `--profile &lt;name&gt;` flags and/or exact individual skill IDs. Never substitute `--all` unless I explicitly request the complete catalog.
Phase 4: preview the exact dependency closure.
Run exactly:
npx @waybarrios/opencode-power-pack install &lt;approved-selection&gt; --project --dry-run
Require a successful exit code. Before writing anything, report:
- the detected host, my stated goal, the approved selection, Git root, and resolved destination;
- the number and complete list of resolved skills, including automatically included companion skills;
- every planned status printed by the installer;
- which entries are new and which already exist;
- any warning, conflict, unexpected path, or permission problem.
Interpret `would-update` as an existing destination conflict. Do not claim it will be overwritten: without --force, the real installation will skip that entry. If the resolved destination is not exactly &lt;git-root&gt;/.agents/skills, or the preview proposes anything outside it, stop. If existing entries are present, explain that they will be preserved and that the result may be a partial update. Never add --force on your own.
Phase 5: install only after the preview satisfies every safety rule.
Run exactly:
npx @waybarrios/opencode-power-pack install &lt;approved-selection&gt; --project
Use the exact same approved selection as the successful dry-run and remove only `--dry-run`. If it fails, stop and report the failure. Do not retry with sudo, --global, --force, or manual copying.
Phase 6: verify and report.
1. Compare the install output with the dry-run selection. Record every `installed`, `skipped`, and warning result.
2. Confirm that every newly installed skill directory exists under &lt;git-root&gt;/.agents/skills and contains a SKILL.md file.
3. Run git status --short again and compare it with the saved baseline. Confirm that installation introduced no changes outside .agents/skills and did not change dependency manifests or lockfiles. Do not revert unrelated differences.
4. Tell the user to start a new agent session if the skills do not appear automatically.
5. Give the host-specific verification command:
- Codex: invoke an installed skill such as $code-review in a new session. Use /plugins only for a native plugin installation.
- OpenCode 1: run opencode debug skill, then invoke /code-review.
- OpenCode 2: check the skill picker, then invoke /code-review.
- Pi: run pi list, then request a task that matches an installed workflow.
6. Finish with a concise structured report containing: stated need, approved selection and rationale, alternatives not chosen, host, Node/npm versions, Git root, destination, exact commands run, resolved skill count and names, installed entries, preserved/skipped entries, warnings or failures, worktree comparison, verification result, and any user action still required.</code></div>
<button
type="button"
class="small-copy"
data-copy-label="Agent prompt"
data-copy-target="agent-install-prompt"
>
Copy agent prompt
</button>
</article>
<h3>Direct command for terminal-capable agents</h3>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile recommended --project --dry-run
npx @waybarrios/opencode-power-pack install --profile recommended --project</code></div>
<p>
Remove <code>--project</code> for a user-level install. Replace <code>recommended</code> with
<code>review</code>, <code>feature-dev</code>, <code>frontend</code>, <code>security</code>,
<code>huggingface</code>, <code>authoring</code>, or <code>project-memory</code>.
</p>
<h3>Claude Code native commands</h3>
<p>Run these inside Claude Code because its native plugin supplies the complete namespaced catalog.</p>
<div class="docs-code"><code>/plugin marketplace add waybarrios/opencode-power-pack
/plugin install opencode-power-pack@opencode-power-pack</code></div>
<p class="note">
Agent-assisted installation still follows the current host's approval and sandbox rules. The
prompt authorizes only the scoped installation described above, not forced replacement or other
project changes.
</p>
</section>
<section class="docs-section" id="cli">
<h2>CLI command reference</h2>
<section class="docs-table-wrap" aria-label="npm installer commands" tabindex="0">
<table class="docs-table command-reference-table">
<thead><tr><th>Command or option</th><th>Behavior</th></tr></thead>
<tbody>
<tr><td><code>list</code></td><td>Print all profiles and skill IDs from the installed package.</td></tr>
<tr><td><code>install &lt;skill...&gt;</code></td><td>Install one or more explicit skill IDs.</td></tr>
<tr><td><code>--profile &lt;name&gt;</code></td><td>Add a curated profile. Repeat the option to combine profiles.</td></tr>
<tr><td><code>--all</code></td><td>Select every skill in the installed package.</td></tr>
<tr><td><code>--global</code></td><td>Write to <code>~/.agents/skills</code>. This is the default.</td></tr>
<tr><td><code>--project</code></td><td>Find the current Git root and write to <code>.agents/skills</code> inside it.</td></tr>
<tr><td><code>--dry-run</code></td><td>Show the resolved destination and changes without writing files.</td></tr>
<tr><td><code>--force</code></td><td>Replace existing copies using locking, staging, and rollback.</td></tr>
<tr><td><code>-h</code> or <code>--help</code></td><td>Print installer syntax and options.</td></tr>
</tbody>
</table>
</section>
<h3>Run without a global install</h3>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack@latest --help</code></div>
<h3>Keep the CLI globally</h3>
<div class="docs-code"><code>npm install --global @waybarrios/opencode-power-pack
opencode-power-pack list
opencode-power-pack install code-review</code></div>
</section>
<section class="docs-section" id="sandbox">
<h2>Run commands in the native sandbox</h2>
<p>
Version 0.5.0 adds an opt-in, fail-closed runner for one command and its complete process tree.
It uses native Seatbelt isolation on macOS and Bubblewrap on Linux. It starts no persistent
container or daemon, and it removes its private temporary directory after the command exits.
</p>
<h3>Install and check readiness</h3>
<p>
The sandbox runtime is part of the npm package. Node.js 20.11.0 or newer is required. Linux
also needs trusted system installations of <code>bubblewrap</code>, <code>socat</code>, and
<code>rg</code>. macOS uses the built-in Seatbelt backend.
</p>
<div class="docs-code"><code># Install the v0.6.0 CLI
npm install --global @waybarrios/opencode-power-pack@0.6.0
# Verify the actual operating-system boundary
opencode-power-pack sandbox doctor
# Inspect the policy assigned to one skill
opencode-power-pack sandbox resolve --skill code-review</code></div>
<p class="note">
Continue only when <code>sandbox doctor</code> exits successfully and reports
<code>runnerReady: true</code> in JSON mode. A failed doctor never authorizes an unsandboxed retry.
</p>
<h3>Run a contained command</h3>
<div class="docs-code"><code># code-review defaults to the read-only observe profile
opencode-power-pack sandbox exec --skill code-review -- git status --short
# The literal -- ends runner options and starts the child command
opencode-power-pack sandbox exec --skill code-review -- rg TODO .</code></div>
<p>
The runner resolves the trusted profile packaged for the selected skill. It preserves the child
exit code, hides unrelated host files and credentials, restricts workspace writes according to
the profile, and never falls back to ordinary execution when setup or cleanup fails.
</p>
<h3>Allow a narrow network read</h3>
<div class="docs-code"><code>opencode-power-pack sandbox exec \
--skill code-review \
--sandbox-profile network-read \
--allow-domain api.github.com \
-- curl https://api.github.com/repos/waybarrios/opencode-power-pack</code></div>
<p>
<code>network-read</code> permits only GET, HEAD, and OPTIONS through the filtered proxy. It is
a method-level best effort, because a poorly designed GET endpoint can still have side effects.
Approve the narrowest destination and expose no credential unless the retrieval requires it.
</p>
<h3>Confirm an external write</h3>
<div class="docs-code"><code>opencode-power-pack sandbox exec \
--skill hf-cli \
--sandbox-profile publish \
--allow-domain huggingface.co \
--allow-env HF_TOKEN \
--confirm-external-side-effects \
-- hf upload owner/repository ./artifact.bin artifact.bin</code></div>
<p>
A publish-capable skill still requires the exact domain, each credential environment variable,
and <code>--confirm-external-side-effects</code>. The runner rejects undeclared escalations.
</p>
<h3>Profiles</h3>
<section class="docs-table-wrap" aria-label="Sandbox profile capabilities" tabindex="0">
<table class="docs-table">
<thead><tr><th>Profile</th><th>Workspace</th><th>Network and credentials</th><th>External writes</th></tr></thead>
<tbody>
<tr><td><code>observe</code></td><td>Read only</td><td>Denied</td><td>Denied</td></tr>
<tr><td><code>develop</code></td><td>Read and write</td><td>Denied</td><td>Denied</td></tr>
<tr><td><code>network-read</code></td><td>Read and write</td><td>Explicit grants</td><td>Denied</td></tr>
<tr><td><code>publish</code></td><td>Read and write</td><td>Explicit grants</td><td>Explicit confirmation</td></tr>
</tbody>
</table>
</section>
<h3>Codex, OpenCode, Claude Code, and Pi compatibility</h3>
<section class="docs-table-wrap" aria-label="Sandbox coding-agent compatibility" tabindex="0">
<table class="docs-table">
<thead><tr><th>Host</th><th>Manual runner</th><th>Automatic routing</th><th>Current boundary</th></tr></thead>
<tbody>
<tr><td>Codex</td><td>Supported</td><td>Not yet implemented</td><td>Explicit sandbox CLI command and descendants</td></tr>
<tr><td>OpenCode</td><td>Supported</td><td>Not yet implemented</td><td>Explicit sandbox CLI command and descendants</td></tr>
<tr><td>Claude Code</td><td>Supported</td><td>Not yet implemented</td><td>Explicit sandbox CLI command and descendants</td></tr>
<tr><td>Pi</td><td>Supported</td><td>Not yet implemented</td><td>Explicit sandbox CLI command and descendants</td></tr>
</tbody>
</table>
</section>
<h3>Run it from each host</h3>
<p>
Native skill or plugin installation does not place the sandbox CLI on <code>PATH</code>. Install
the npm CLI once in the operating-system environment used by the agent, then run the doctor from
that same agent session. A doctor that succeeds in another terminal does not prove that a more
restricted agent session can start the backend.
</p>
<div class="docs-code"><code>npm install --global @waybarrios/opencode-power-pack@0.6.0</code></div>
<article class="host-doc">
<header><span>01</span><h3>Codex</h3><b>MANUAL RUNNER</b></header>
<p>Paste this request into Codex while the session is open in the target repository:</p>
<div class="docs-code"><code>Use the shell tool to run `opencode-power-pack sandbox doctor`.
If it succeeds, run `opencode-power-pack sandbox exec --skill code-review -- git status --short`.
Do not run the child command separately and do not retry without the sandbox.</code></div>
<p>Codex invokes the shared CLI through its shell tool. Its other tools are not automatically routed through this runner.</p>
</article>
<article class="host-doc">
<header><span>02</span><h3>OpenCode</h3><b>MANUAL RUNNER</b></header>
<p>Paste this request into OpenCode while the session is open in the target repository:</p>
<div class="docs-code"><code>Use the shell tool to run `opencode-power-pack sandbox doctor`.
If it succeeds, run `opencode-power-pack sandbox exec --skill code-review -- git status --short`.
Do not run the child command separately and do not retry without the sandbox.</code></div>
<p>OpenCode invokes the same CLI through its shell tool. A future custom-tool adapter is required for automatic enforcement.</p>
</article>
<article class="host-doc">
<header><span>03</span><h3>Claude Code</h3><b>MANUAL RUNNER</b></header>
<p>Paste this request into Claude Code while the session is open in the target repository:</p>
<div class="docs-code"><code>Use Bash to run `opencode-power-pack sandbox doctor`.
If it succeeds, run `opencode-power-pack sandbox exec --skill code-review -- git status --short`.
Do not run the child command separately and do not retry without the sandbox.</code></div>
<p>Claude Code invokes the shared CLI through Bash. Read, Edit, Write, WebFetch, MCP, and computer-use tools remain separate host surfaces.</p>
</article>
<article class="host-doc">
<header><span>04</span><h3>Pi</h3><b>MANUAL RUNNER</b></header>
<p>Paste this request into Pi while the session is open in the target repository:</p>
<div class="docs-code"><code>Use the shell tool to run `opencode-power-pack sandbox doctor`.
If it succeeds, run `opencode-power-pack sandbox exec --skill code-review -- git status --short`.
Do not run the child command separately and do not retry without the sandbox.</code></div>
<p>Pi invokes the shared CLI through its shell tool. A future extension must replace or intercept built-in tools for automatic enforcement.</p>
</article>
<p class="note">
Yes, it works from Codex and OpenCode when either agent explicitly invokes the CLI. A skill file
cannot silently change the host session's sandbox. Ordinary shell, file, browser, MCP, and connector
tools remain outside this command boundary until host-specific adapters block those bypass paths.
The project therefore claims <code>shell-contained</code>, not whole-agent isolation.
</p>
<h3>Platform status</h3>
<ul>
<li><strong>macOS:</strong> supported with the built-in Seatbelt backend.</li>
<li><strong>Linux:</strong> supported when Bubblewrap namespaces and the required trusted helpers are available.</li>
<li><strong>WSL2:</strong> expected to use the Linux backend, but dedicated CI is still pending.</li>
<li><strong>Windows native and WSL1:</strong> unsupported and intentionally fail closed.</li>
</ul>
<p>
For the complete threat boundary, Git worktree handling, network limitations, native dependency
checks, and adapter roadmap, read the
<a href="https://github.com/waybarrios/opencode-power-pack/blob/main/docs/sandbox-compatibility.md">sandbox compatibility specification</a>.
</p>
</section>
<section class="docs-section" id="how-skills-work">
<h2>How skills work</h2>
<p>
A skill is an instruction package centered on a <code>SKILL.md</code> file. It is not a
background service and does not add a runtime dependency to your application. Your coding
agent reads the skill's trigger description, then follows its workflow when the task matches
or when you invoke the skill explicitly.
</p>
<div class="skill-lifecycle">
<article><span>01</span><h3>Discover</h3><p>The host loads installed skill IDs and their trigger descriptions.</p></article>
<article><span>02</span><h3>Select</h3><p>You name a skill explicitly, or the host matches one to the current task.</p></article>
<article><span>03</span><h3>Execute</h3><p>The agent follows the workflow and uses only tools and permissions available in that host.</p></article>
<article><span>04</span><h3>Coordinate</h3><p>Coordinator skills may call companion workflows for exploration, architecture, review, or deployment.</p></article>
</div>
<p class="note">
Installing a skill does not grant extra operating-system or cloud permissions. Authentication,
tool access, approvals, and sandbox rules remain controlled by Claude Code, Codex, OpenCode,
Pi, and your local environment.
</p>
</section>
<section class="docs-section" id="hosts">
<h2>Full native host installs</h2>
<p>
Each method below installs all 55 workflows. Use the npm path above when you want a smaller
set for Codex, OpenCode, or Pi.
</p>
<article class="host-doc" id="host-claude">
<header><span>01</span><h3>Claude Code</h3><b>FULL CATALOG</b></header>
<p>Run both commands inside Claude Code. The first registers the repository marketplace; the second activates its plugin.</p>
<div class="docs-code"><code>/plugin marketplace add waybarrios/opencode-power-pack
/plugin install opencode-power-pack@opencode-power-pack</code></div>
<dl>
<div><dt>Reload</dt><dd>Run <code>/reload-plugins</code> only if the installation result requests it.</dd></div>
<div><dt>Verify</dt><dd>Open <code>/plugin</code> and confirm <code>opencode-power-pack</code> is enabled.</dd></div>
<div><dt>Invoke</dt><dd>Use the collision-safe namespace, for example <code>/opencode-power-pack:code-review</code>.</dd></div>
</dl>
</article>
<article class="host-doc" id="host-codex">
<header><span>02</span><h3>Codex CLI and desktop</h3><b>FULL CATALOG</b></header>
<p>Register the marketplace snapshot, install its plugin, then start a new Codex session.</p>
<div class="docs-code"><code>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</code></div>
<dl>
<div><dt>Verify</dt><dd>The list command and <code>/plugins</code> should show the installed package.</dd></div>
<div><dt>Invoke</dt><dd>Mention a skill explicitly with <code>$code-review</code>, <code>$feature-dev</code>, or another ID.</dd></div>
<div><dt>Selective alternative</dt><dd>Use npm to copy only chosen skills into <code>.agents/skills</code>.</dd></div>
</dl>
</article>
<article class="host-doc" id="host-opencode">
<header><span>03</span><h3>OpenCode 1 and 2</h3><b>FULL CATALOG</b></header>
<p>OpenCode 2.0 needs v0.6.0 or Git main. The v0.5.0 tag predates the V2 plugin port.</p>
<div class="docs-code"><code># OpenCode 2
opencode plugin add "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
# OpenCode 1
opencode plugin --global "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"</code></div>
<dl>
<div><dt>Restart</dt><dd>Start a new OpenCode session after installation.</dd></div>
<div><dt>Verify V2</dt><dd>Run <code>opencode debug agents</code> and check the skill picker for all 55 workflows.</dd></div>
<div><dt>Verify V1</dt><dd>Run <code>opencode debug skill</code> and <code>opencode debug agent code-explorer</code>.</dd></div>
<div><dt>Invoke</dt><dd>Use a slash command such as <code>/code-review</code>, <code>/feature-dev</code>, or <code>/humanizer</code>.</dd></div>
</dl>
<p>V2 evaluates the bundled specialists' read-only policy after global rules. The agent listing can show the host's base permissions. A custom system prompt or primary mode replaces the bundled role and keeps the host's permission defaults.</p>
</article>
<article class="host-doc" id="host-pi">
<header><span>04</span><h3>Pi</h3><b>FULL CATALOG</b></header>
<p>Choose user-level installation or save the package to the current project's Pi settings with <code>-l</code>.</p>
<div class="docs-code"><code># User-level package
pi install git:github.com/waybarrios/opencode-power-pack
# Project-local package
pi install git:github.com/waybarrios/opencode-power-pack -l</code></div>
<dl>
<div><dt>Restart</dt><dd>Start a new Pi session so it loads the package's declared <code>skills/</code> directory.</dd></div>
<div><dt>Verify</dt><dd>Run <code>pi list</code> and confirm the Git source is present.</dd></div>
<div><dt>Invoke</dt><dd>Ask for the task directly; Pi routes to installed skills from their trigger descriptions.</dd></div>
</dl>
</article>
</section>
<section class="docs-section" id="profiles">
<h2>Profiles and contents</h2>
<p>
Profiles are curated selections, not separate packages. The command resolves the listed
workflows and any required companions before it writes files.
</p>
<div class="profile-doc-list">
<details open>
<summary><span><code>recommended</code> Balanced development toolkit</span><b>11 resolved skills</b></summary>
<div>
<p>Use this as the default software-development set without the specialized security and ML catalogs.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile recommended</code></div>
<p><strong>Selected:</strong> <code>agents-md-improver</code>, <code>agents-md-revise</code>, <code>code-quality</code>, <code>code-review</code>, <code>feature-dev</code>, <code>frontend-design</code>, <code>mcp-builder</code>, and <code>skill-creator</code>.</p>
<p><strong>Added through feature-dev:</strong> <code>code-architect</code>, <code>code-explorer</code>, and <code>code-reviewer</code>.</p>
</div>
</details>
<details>
<summary><span><code>review</code> General and security-aware review</span><b>4 skills</b></summary>
<div>
<p>Combines broad PR review, focused implementation critique, quality checks, and security differential analysis.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile review</code></div>
<p><code>code-quality</code>, <code>code-review</code>, <code>code-reviewer</code>, and <code>differential-review</code>.</p>
</div>
</details>
<details>
<summary><span><code>feature-dev</code> End-to-end feature delivery</span><b>4 resolved skills</b></summary>
<div>
<p>Installs the seven-phase coordinator and its exploration, architecture, and focused-review specialists.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile feature-dev</code></div>
<p><code>feature-dev</code> plus automatic companions <code>code-explorer</code>, <code>code-architect</code>, and <code>code-reviewer</code>.</p>
</div>
</details>
<details>
<summary><span><code>frontend</code> Interface implementation and critique</span><b>2 skills</b></summary>
<div>
<p>Pairs production frontend implementation with a measurable anti-generic quality rubric.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile frontend</code></div>
<p><code>frontend-design</code> and <code>ai-slop</code>.</p>
</div>
</details>
<details>
<summary><span><code>security</code> Application-security toolkit</span><b>15 skills</b></summary>
<div>
<p>Covers threat modeling, manual and differential review, static analysis, finding validation, variant hunting, secure API design, dependency risk, and reporting.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile security</code></div>
<p><code>agentic-actions-auditor</code>, <code>codeql</code>, <code>differential-review</code>, <code>fp-check</code>, <code>insecure-defaults</code>, <code>sarif-parsing</code>, <code>security-review</code>, <code>security-threat-model</code>, <code>semgrep</code>, <code>semgrep-rule-creator</code>, <code>semgrep-rule-variant-creator</code>, <code>sharp-edges</code>, <code>supply-chain-risk-auditor</code>, <code>variant-analysis</code>, and <code>vuln-report</code>.</p>
</div>
</details>
<details>
<summary><span><code>huggingface</code> Model and deployment workflows</span><b>25 skills</b></summary>
<div>
<p>Covers Hub operations, model and dataset discovery, local inference, training, evaluation, Gradio, Spaces, tracking, ZeroGPU, and production SageMaker deployment.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile huggingface</code></div>
<p><code>hf-cli</code>, <code>hf-cloud-aws-context-discovery</code>, <code>hf-cloud-python-env-setup</code>, <code>hf-cloud-sagemaker-deployment-planner</code>, <code>hf-cloud-sagemaker-iam-preflight</code>, <code>hf-cloud-sagemaker-production-defaults</code>, <code>hf-cloud-serving-image-selection</code>, <code>hf-mem</code>, <code>huggingface-best</code>, <code>huggingface-community-evals</code>, <code>huggingface-datasets</code>, <code>huggingface-gradio</code>, <code>huggingface-llm-trainer</code>, <code>huggingface-local-models</code>, <code>huggingface-lora-space-builder</code>, <code>huggingface-paper-publisher</code>, <code>huggingface-papers</code>, <code>huggingface-spaces</code>, <code>huggingface-tool-builder</code>, <code>huggingface-trackio</code>, <code>huggingface-vision-trainer</code>, <code>huggingface-zerogpu</code>, <code>train-sentence-transformers</code>, <code>transformers-js</code>, and <code>trl-training</code>.</p>
</div>
</details>
<details>
<summary><span><code>authoring</code> Reusable workflow creation</span><b>4 skills</b></summary>
<div>
<p>Create Agent Skills and MCP servers, or turn technical papers into engineering-ready summaries.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile authoring</code></div>
<p>Includes <code>humanizer</code>, <code>mcp-builder</code>, <code>paper-summarizer</code>, and <code>skill-creator</code>. <a href="skills/#humanizer">Read the humanizer reference.</a></p>
</div>
</details>
<details>
<summary><span><code>project-memory</code> Durable agent guidance</span><b>2 skills</b></summary>
<div>
<p>Audit existing AGENTS.md and CLAUDE.md files, then capture durable lessons from completed work.</p>
<div class="docs-code"><code>npx @waybarrios/opencode-power-pack install --profile project-memory</code></div>
<p><code>agents-md-improver</code> and <code>agents-md-revise</code>.</p>
</div>
</details>
</div>
<p><a href="skills/">Open the complete 55-skill reference for individual installation commands →</a></p>
</section>
<section class="docs-section" id="reviews">
<h2>Which review skill?</h2>
<section class="docs-table-wrap" aria-label="Code review skill comparison" tabindex="0">
<table class="docs-table">
<thead><tr><th>Situation</th><th>Skill</th><th>Reason</th></tr></thead>
<tbody>
<tr>
<td>Pull request, branch, commit range, or complete pending diff</td>
<td><code>code-review</code></td>
<td>Freezes the scope, runs multiple review lenses, and cross-checks candidates.</td>
</tr>
<tr>
<td>One file, function, or focused implementation change</td>
<td><code>code-reviewer</code></td>
<td>Uses a lighter two-pass review with caller and full-file context.</td>
</tr>
<tr>
<td>Feature development quality phase</td>
<td><code>code-reviewer</code></td>
<td>Acts as the focused specialist dispatched by <code>feature-dev</code>.</td>
</tr>
</tbody>
</table>
</section>
</section>
<section class="docs-section" id="maintenance">
<h2>Update and remove</h2>
<h3>Skills copied by npm</h3>
<p>Run the latest installer with the same selection and <code>--force</code> to replace copied workflows safely.</p>
<div class="docs-code"><code># Update a user-level profile
npx @waybarrios/opencode-power-pack@latest install --profile review --force
# Update one project-local skill
npx @waybarrios/opencode-power-pack@latest install code-review --project --force</code></div>
<p>
The selective CLI has no remove command in v0.6.0. To remove a copied workflow, verify the
destination printed by the installer and delete only its exact skill directory, such as
<code>~/.agents/skills/code-review</code> or <code>&lt;repo&gt;/.agents/skills/code-review</code>.
</p>
<h3>Globally installed npm CLI</h3>
<div class="docs-code"><code>npm update --global @waybarrios/opencode-power-pack
npm uninstall --global @waybarrios/opencode-power-pack</code></div>
<p>Removing the global CLI does not remove skill directories that were already copied.</p>
<h3>Claude Code</h3>
<div class="docs-code"><code>/plugin marketplace update opencode-power-pack
/plugin update opencode-power-pack@opencode-power-pack
/plugin uninstall opencode-power-pack@opencode-power-pack</code></div>
<h3>Codex</h3>
<div class="docs-code"><code>codex plugin marketplace upgrade opencode-power-pack
codex plugin add opencode-power-pack@opencode-power-pack
codex plugin remove opencode-power-pack@opencode-power-pack</code></div>
<h3>OpenCode 2</h3>
<div class="docs-code"><code>opencode plugin update "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
opencode plugin remove "opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"</code></div>
<p>Use the exact configured specification, including a tag or local Git URL. On OpenCode 1, update by reinstalling with <code>plugin --global</code>; remove its entry from the <code>plugin</code> config array to uninstall. For local clones, pull the source and then update or reinstall.</p>
<h3>Pi</h3>
<div class="docs-code"><code>pi update git:github.com/waybarrios/opencode-power-pack
pi remove git:github.com/waybarrios/opencode-power-pack</code></div>
</section>
<section class="docs-section" id="evaluations">
<h2>Contributor checks and live evaluations</h2>
<p>The behavioral runner uses the OpenCode 2 session API. It rejects partial text from failed or interrupted turns and accepts optional <code>provider/model#variant</code> model references.</p>
<p>Live runs need provider environment credentials. The isolated runtime does not copy OpenCode 2's credential database. See the <a href="https://github.com/waybarrios/opencode-power-pack/blob/main/evals/behavioral/README.md">evaluation guide</a> for setup and evidence review.</p>
<p>The <a href="https://github.com/waybarrios/opencode-power-pack/blob/main/docs/opencode-compatibility.md">OpenCode compatibility guide</a> covers version checks, source selection, updates, and specialist permissions.</p>
</section>
<section class="docs-section" id="troubleshooting">
<h2>Troubleshooting</h2>
<h3>Node rejects the package</h3>
<p>The selective installer requires Node.js 20.11.0 or newer. Check with <code>node --version</code>, upgrade Node, and run the same <code>npx</code> command again.</p>
<h3>Unknown skill or profile</h3>
<p>Run <code>npx @waybarrios/opencode-power-pack list</code> and copy the lowercase hyphenated ID exactly. Profile names and skill IDs are case-sensitive.</p>
<h3><code>--project</code> cannot find a repository</h3>
<p>Run the installer from inside a Git working tree. The option walks upward until it finds the repository's <code>.git</code> entry.</p>
<h3>A copied skill is not visible</h3>
<p>Start a new host session and confirm that the skill exists under the expected user or project <code>.agents/skills</code> directory.</p>
<h3>A Claude skill name conflicts</h3>
<p>Use the namespaced form, such as <code>/opencode-power-pack:code-review</code>.</p>
<h3>The installer will not overwrite a skill</h3>
<p>This is deliberate. Preview the update with <code>--dry-run</code>, then repeat it with <code>--force</code>.</p>
<h3>An <code>.opp-lock</code> directory remains</h3>
<p>
First confirm that no installer process is running. The lock prevents concurrent replacement
of the same skill. If a terminated process left it behind, remove only the exact lock path
reported in the error and repeat the install.
</p>
<h3>The same skill appears from two sources</h3>
<p>
A full native plugin and an npm-copied skill can overlap. Disable one activation path for that
host and scope. In Claude Code, prefer the namespaced plugin form to avoid name collisions.
</p>
<h3>Need more detail?</h3>
<p>
Read the <a href="https://github.com/waybarrios/opencode-power-pack#installation">complete repository guide</a>
or <a href="https://github.com/waybarrios/opencode-power-pack/issues">open an issue</a> with the host,
version, command, and error output.
</p>
</section>
</main>
</div>
<script src="../app.js?v=2026-10-19-opencode-2" defer></script>
</body>
</html>