version

Prints the project's vendored plumbline version alongside the carried payload version.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill version-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-plumbline/skills/version
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill version-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project pins a vendored copy of the plumbline linter, its version can drift behind the version carried by the installed ok front-door plugin. This Skill surfaces both versions side by side so you can see whether the project lints at an older pinned version than the payload offers. ## Core Features & Use Cases - Dual version report: Runs the vendored binary at .ok-plumbline/bin/plumbline and the carried payload binary, printing each version on its own labeled line. - Drift detection: A mismatch between the two lines signals that the front door has moved ahead and the project has not yet converged. - Graceful absence handling: Reports none when the project has no vendored binary or when the ok front door is not installed on the machine, and explains the 0.0.0-unvendored placeholder stamped on unvendored payload copies. - Use Case: After updating the ok plugin, run /version in a project to confirm whether its pinned linting version still matches the newly carried payload before deciding to converge. ## Quick Start Invoke the /version slash command to print the project's vendored plumbline version next to the carried payload version.

Frequently Asked Questions about version

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

FAQPage Schema
How do I check which plumbline version my project lints with?▼

Run the /version slash command. It executes the vendored binary at .ok-plumbline/bin/plumbline and prints the version your project currently lints with on the project line.

Why does the payload version differ from my project version?▼

The versions differ when the installed ok front door has moved ahead of your project's last converge. The project keeps linting at its pinned version until you deliberately converge to the newer payload.

What does 0.0.0-unvendored mean in the version output?▼

A payload copy reporting 0.0.0-unvendored is expected. That placeholder is replaced with the real version only when converge vendors the binary into a project.

What does it mean when /version reports none for the payload?▼

A payload line reading none means the ok front door is not installed on this machine. The project still lints at its own pinned vendored version regardless.

Does the version command run automatically during conversation?▼

No. The skill is only activated by the explicit /version slash command and is never auto-triggered by conversation content.