ok-version

Reports the active ok-planner plugin and conduct versions for the current session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with the ok-planner plugin suite, it can be unclear which plugin version and which conduct version are actually governing the current session, especially after updates or reloads. This Skill gives a definitive, read-only answer without touching disk or making any drift judgment. ## Core Features & Use Cases - Plugin version recital: Reads the version from the SessionStart hook's injected context line and reports it, or reports unknown if absent. - Conduct version recital: Reads the Conduct version: line from the active Output Style in the system prompt, reporting unstamped if none exists. - Use Case: After updating plugins, run /ok-version to confirm whether the session picked up the new version, then decide whether to /reload-plugins and /clear or start a fresh session. ## Quick Start Invoke the /ok-version slash command to print the plugin and conduct versions active in this session.

Frequently Asked Questions about ok-version

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

FAQPage Schema
How do I check which plugin version is running in my Claude Code session?▼

Invoke the /ok-version slash command. It reads the version from the SessionStart hook's injected context line and reports it, or reports unknown if that line is absent from the session.

How do I find the active conduct version in a session?▼

The skill inspects the active Output Style instructions in the system prompt for a line beginning with Conduct version: and reports it verbatim. If no such line exists, it reports unstamped.

Why does the version check report unknown or unstamped?▼

Unknown means the SessionStart hook context line was not injected into this session. Unstamped means no ok-conduct output style is active or the active style predates version stamping.

Does the version check read files from disk or compare versions?▼

No. The skill is strictly read-only against session context: it never reads disk, never edits files, never compares versions, and never issues a drift verdict. It only recites what the session reports.

What should I do if the reported version is not what I expect?▼

Investigate from there: run /reload-plugins followed by /clear, or start a fresh session so the updated plugin and conduct versions are loaded into context.