How do I install the Okf Harness skill?

Run npx skillmds@latest add pumblus/okf-harness-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Okf Harness safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Okf Harness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Okf Harness free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Okf Harness?

pumblus (@pumblus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Okf Harness by pumblus — Agent Skill

Name: Okf Harness
Author: pumblus

Okf Harness

Unified OKF Harness entrypoint for Pi, OpenCode, and OpenClaw. Use when the user asks to create, find, select, repair, check, ingest into, reconcile, answer from, or graph an OKF Harness workspace. Do not use for generic Markdown editing, repository maintenance, repository dependency graphs, or non-OKF knowledge-base work.

pumblus Updated Sep 22, 2026

File contents

OKF Harness

Route setup and workspace maintenance through this host entrypoint.

Runtime Route

Start by invoking the launcher and reading its machine-readable result:

npx @okf-harness/setup@latest launch -- status --json

WORKSPACE_NOT_FOUND: discover a workspace in the current folder, a user-named folder, or immediate children of Documents/OKF Harness; otherwise create one with the command below.
RUNTIME_PIN_MISSING: run data.adoptCommand exactly, then retry.
CONFIG_INVALID or runtime execution failure: stop with the reported problem.
Resolved workspace: pass every runtime operation through the launcher with --workspace <workspace>.

Create a workspace without adding unsupported workspace-local guidance:

npx --yes --package @okf-harness/cli@0.8.1 okfh init <workspace> --name <name> --agents none --json

Workspace Routes

npx @okf-harness/setup@latest launch --workspace <workspace> -- status --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- check --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- source add <source> --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- ingest plan <source-id> --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- source list --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- source reconcile <prior-source-id> <revision-source-id> --note "<judgment-note>" --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- evidence "<question>" --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- read <concept-id-or-path> --json
npx @okf-harness/setup@latest launch --workspace <workspace> -- graph --json

Completion Contract

Setup finishes with the resolved workspace path and a successful launcher status.
Check reports the status and first concrete next step.
Ingest reports the source ID, changed wiki paths, and final check status.
Reconciliation finishes only after the exact revision edge is acknowledged.
Answer cites concept paths and source IDs and states material evidence limits.
Graph reports the generated HTML and backlinks paths.

Boundaries

This host skill supports daily operations but does not install workspace-local guidance. Do not claim otherwise.
Before writes, confirm the workspace path. Never initialize a non-empty non-workspace directory.
Never edit raw/sources/; register corrected material as a new source.
Ingest plans do not synthesize wiki content. After bounded wiki edits, run check and name changed files.
Normal answers use synthesized wiki/ evidence and at most one continuation-cue read, not raw source bodies.
Never invent source IDs, citations, command output, or an okfh query command.

---name: okf-harness-5description: Unified OKF Harness entrypoint for Pi, OpenCode, and OpenClaw. Use when the user asks to create, find, select, repair, check, ingest into, reconcile, answer from, or graph an OKF Harness workspace. Do not use for generic Markdown editing, repository maintenance, repository dependency graphs, or non-OKF knowledge-base work.license: Apache-2.0---# OKF HarnessRoute setup and workspace maintenance through this host entrypoint.## Runtime RouteStart by invoking the launcher and reading its machine-readable result:```bashnpx @okf-harness/setup@latest launch -- status --json```- `WORKSPACE_NOT_FOUND`: discover a workspace in the current folder, a user-named folder, or immediate children of `Documents/OKF Harness`; otherwise create one with the command below.- `RUNTIME_PIN_MISSING`: run `data.adoptCommand` exactly, then retry.- `CONFIG_INVALID` or runtime execution failure: stop with the reported problem.- Resolved workspace: pass every runtime operation through the launcher with `--workspace <workspace>`.Create a workspace without adding unsupported workspace-local guidance:```bashnpx --yes --package @okf-harness/cli@0.8.1 okfh init <workspace> --name <name> --agents none --json```## Workspace Routes```bashnpx @okf-harness/setup@latest launch --workspace <workspace> -- status --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- check --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- source add <source> --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- ingest plan <source-id> --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- source list --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- source reconcile <prior-source-id> <revision-source-id> --note "<judgment-note>" --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- evidence "<question>" --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- read <concept-id-or-path> --jsonnpx @okf-harness/setup@latest launch --workspace <workspace> -- graph --json```## Completion Contract- Setup finishes with the resolved workspace path and a successful launcher status.- Check reports the status and first concrete next step.- Ingest reports the source ID, changed wiki paths, and final check status.- Reconciliation finishes only after the exact revision edge is acknowledged.- Answer cites concept paths and source IDs and states material evidence limits.- Graph reports the generated HTML and backlinks paths.## Boundaries- This host skill supports daily operations but does not install workspace-local guidance. Do not claim otherwise.- Before writes, confirm the workspace path. Never initialize a non-empty non-workspace directory.- Never edit `raw/sources/`; register corrected material as a new source.- Ingest plans do not synthesize wiki content. After bounded wiki edits, run check and name changed files.- Normal answers use synthesized `wiki/` evidence and at most one continuation-cue read, not raw source bodies.- Never invent source IDs, citations, command output, or an `okfh query` command.

Frequently asked questions