Offing plugin for Claude

Offing's Claude plugin packages the canonical lifecycle Skill with the same version-pinned local MCP server used by the Codex adapter. It does not fork detectors, migration logic, or verification behavior.

Requirements

• Claude Code 2.1.292 or newer for the one-command marketplace install shown below.
• Node.js 22 or newer for the local Offing MCP server.

Install

Install directly from Offing's GitHub marketplace:

claude plugin install offing --marketplace velella-sh/offing

For older Claude Code versions, add the marketplace and install in two steps:

claude plugin marketplace add velella-sh/offing
claude plugin install offing@offing

Choose a scope when needed:

claude plugin install offing@offing --scope user
claude plugin install offing@offing --scope project
claude plugin install offing@offing --scope local

User scope enables Offing for you on this machine. Project scope records it in the repository's .claude/settings.json for collaborators. Local scope enables it only for you in the current repository.

For development without installing, load the adapter directory for one session:

claude --plugin-dir ./plugins/claude

Confirm

claude plugin list
claude plugin details offing

The installed plugin exposes the offing Skill and the local offing MCP server. Scan, list, explain, context, and verify behavior is checked against the Codex adapter by npm run eval:plugins.

Dependency guard

The plugin includes a PostToolUse hook that runs after Claude Code writes or edits a file. When the edit adds a dependency that Offing's lifecycle rules mark as deprecated, Claude gets a warning with the evidence and the replacement, and you see a one-line notice.

What it looks at:

• package.json: dependencies added or whose version changed.
• requirements*.txt, constraints*.txt, and pyproject.toml: added requirements.
• GitHub workflows and action.yml: added uses: references that carry a version tag, such as actions/checkout@v4.

Only what the edit added is checked, so existing dependencies never produce repeated warnings. For a range such as ^2.88.2 the lower bound is checked.

Offing: pkg:npm/request@2.88.2 — request is deprecated (high, deprecated).
The package is fully deprecated and no new changes are expected.
Replacement: Native fetch or a maintained HTTP client.
Evidence: https://www.npmjs.com/package/request

Behavior you can rely on:

• It never blocks and never edits files. The warning explains the problem and cites its sources, and you or Claude decide what to do.
• It checks with offing check, which runs locally against the lifecycle rules bundled in the pinned release. No repository content leaves your machine.
• A package with no rule produces no output. That is absence of evidence, not a safety claim.
• If the check cannot run (for example, offline on the first use), the hook says so instead of staying silent, and the edit is unaffected. An unreadable payload exits quietly.

The hook script is generated from integrations/dependency-guard/guard.mjs, which the Codex integration shares. It uses the same pinned package as the MCP server (offing@<version>). Set OFFING_CHECK_COMMAND to use another Offing command, for example a local build.

Update

claude plugin update offing@offing

The marketplace has automatic updates off by default. You can manage that setting from the Marketplaces tab in /plugin.

Disable and re-enable

claude plugin disable offing@offing
claude plugin enable offing@offing

Disabling stops the Skill and MCP server from loading but keeps the installed files and settings.

Remove

claude plugin uninstall offing@offing

If it was installed at project scope, add --scope project. To remove the marketplace after uninstalling its plugin:

claude plugin marketplace remove offing

Public directory submission

The public Claude directory submission uses:

• Repository: https://github.com/velella-sh/offing
• Plugin path: plugins/claude
• Tracked branch: main
• Submission type: Plugin bundle

The submitter must connect a GitHub account with push access, answer Anthropic's data-handling and compliance questions, and submit from the Claude developer portal. The local package is prepared for that review with a manifest, README, Apache-2.0 license, exact npm runtime pin, strict Claude validation, and the repository security/evaluation evidence in Plugin host evaluation.