Opchain Skills MCP Server

opchain

Opchain 2.0.4 · 36 skills · released September 14–21, 2026.

A coordinated set of Claude skills covering the full software development pipeline — discover, spec, design, build, audit, ship, scale. One skill per phase. A shared JSON checkpoint protocol carries context across sessions and skills, so work resumes where you left off.

Site & docs: https://opchain.dev

---

install

Claude Code — plugin (recommended)

Ships complete skills and plugin hooks for session context and suggestions. Run /oc-enroll in each repository to enable the Git commit gate. Installing the plugin alone does not enroll repositories or enable learning.

/plugin marketplace add asfbay-bit/opchain-skills
/plugin install opchain

Claude Code — zip (skills only, no hooks)

curl -L https://opchain.dev/opchain-skills.zip -o opchain-skills.zip
unzip opchain-skills.zip -d .claude/skills/
claude
> /oc-discover

Claude.ai / Claude Desktop

Download complete skill ZIPs from Install, then use your host's supported skill upload flow. Keep references and runtime files with each skill. Local runtime commands require Node.js 22.13 or newer and a host that can execute them; a hosted chat without local tools cannot run those commands.

Team (check into git)

git add .claude/skills/
git commit -m "chore: add opchain skills"
git push

Upgrade

For an existing repo installation, ask your coding agent to run:

/oc-update check
/oc-update

If you use 1.9 or earlier and the updater is missing, copy the upgrade prompt at the top of Install. It checks the host and published release, then installs the complete package. The updater preserves checkpoints, local tracking consent, usage history and unrelated skills, and backs up replaced Opchain files. Global plugin installations use the host's supported plugin update.

Open a new agent session afterward and run /oc-update check to verify the installed package. Learning remains off until explicitly enabled; provider access and an external reviewer must be configured separately.

ow- planning skills (client work: the fit call to the care month)

The nine ow- skills under skills-work/ plan and run client work: ow-start, ow-build-plan, ow-build, ow-uat, ow-documentation, ow-handoff, ow-draft, ow-research and ow-care. They are text only, work on any host, carry their own versions (the table in skills-work/README.md) and share one protocol, skills-work/ow-protocol.md, which every skill also carries at references/ow-protocol.md. They are not in the opchain plugin or in opchain-skills.zip.

Claude Code. From this repository, copy the skills you want into the project you work in (a client workspace, never this repository):

git clone --depth 1 https://github.com/asfbay-bit/opchain-skills.git
cp -R opchain-skills/skills-work/ow-start opchain-skills/skills-work/ow-build-plan .claude/skills/

Or take every skill from the zip (per-skill zips are at https://opchain.dev/work/<id>.zip):

curl -L https://opchain.dev/opchain-work-skills.zip -o opchain-work-skills.zip
unzip opchain-work-skills.zip -d .claude/skills/

Claude.ai / Claude Desktop. Upload a per-skill zip (https://opchain.dev/work/<id>.zip) through your host's skill upload flow. Each zip is the complete skill folder.

Verify. Each installed skill is a folder .claude/skills/<id>/ holding SKILL.md, references/ow-protocol.md (identical to skills-work/ow-protocol.md) and skill.edges.yaml:

ls .claude/skills/ow-start/SKILL.md .claude/skills/ow-start/references/ow-protocol.md
grep -m1 '^  version:' .claude/skills/ow-start/SKILL.md

Then start a new Claude Code session and run /ow-start. ow-start's first screen asks for the client folder; the skill's version is on its header line. The same check runs at every opchain.dev build from an empty folder (scripts/check-work-install.mjs in the source repository).

ow-tools (Claude Code add-on for the ow- planning skills)

plugins/ow-tools/ runs code on your machine: local call transcription with speaker separation, branded PDF and Word export, date and arithmetic checks, and a session-start list of open workstreams. It comes from its own marketplace, so an administrator can approve it without approving anything else here:

/plugin marketplace add https://raw.githubusercontent.com/asfbay-bit/opchain-skills/main/plugins/ow-tools/.claude-plugin/marketplace.json
/plugin install ow-tools@opchain-work-tools

Then run /ow-tools to see what your machine still needs. ow-tools installs nothing itself. See plugins/ow-tools/README.md.

The marketplace entry follows this repository's main until the first release that ships ow-tools; from then on it names that release's tag (ref: v<semver>), which this repository carries as a tag of its own, so an ow-tools update is a new release, never a mirror sync. SECURITY-MANIFEST.md lists every file with its SHA-256; its own hash is published apart from this repository at https://opchain.dev/work/ow-tools-security-manifest.sha256 (see SECURITY.md).

---

skills

Full descriptions, triggers, and examples: https://opchain.dev/skills

---

the checkpoint protocol

Every skill writes a JSON checkpoint to .checkpoints/ in your project. Skills read each other's checkpoints to make informed decisions — context flows forward without manual handoffs.

• oc-deploy-ops reads oc-code-auditor — CRITICAL findings block deploy
• The build evaluator reads oc-ux-engineer — grades frontend against the approved design spec
• oc-git-ops reads oc-app-architect — names branches by sprint

Schema lives in skills/oc-checkpoint-protocol/SKILL.md.

---

this repository

This is a public, force-push snapshot mirror of the skill source. The site, build system, and internal tooling live in a private upstream repo; only the product (this directory) is published here, refreshed on every change to main upstream.

See CONTRIBUTING.md for how issues and PRs flow back into the upstream repo.

---

license

Apache-2.0 — see LICENSE and NOTICE. Releases up to and including v1.8.2 were published under MIT.