Tsed CLI
tsedio/tsed
Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…
Kernel-version skew check (ADR-027). An agent skill from ruvnet/metaharness.
$ npx skills add ruvnet/metaharness --skill diag-harness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ruvnet/metaharness diag-harness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .claude/skills/diag-harness && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .claude/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harnessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ruvnet/metaharness --skill diag-harness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ruvnet/metaharness diag-harness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .agents/skills/diag-harness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .agents/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/metaharness --skill diag-harness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ruvnet/metaharness diag-harness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .cursor/skills/diag-harness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .cursor/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ruvnet/metaharness.git --path .claude-plugin/skills/diag-harness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ruvnet/metaharness --skill diag-harness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ruvnet/metaharness diag-harness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .gemini/skills/diag-harness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .gemini/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ruvnet/metaharness diag-harnessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ruvnet/metaharness --skill diag-harness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .github/skills/diag-harness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .github/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/metaharness --skill diag-harness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ruvnet/metaharness diag-harness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/metaharness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude-plugin/skills/diag-harness .opencode/skills/diag-harness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diag-harness" agent skill from https://github.com/ruvnet/metaharness/tree/main/.claude-plugin/skills/diag-harness into .opencode/skills/diag-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diag-harness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
diag-harnessKernel-version skew check (ADR-027). An agent skill from ruvnet/metaharness.
Diag Harness is an agent skill from ruvnet/metaharness. Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/kernel@X.Y.Z next step. Exits 2 if no .harness/manifest.json at path.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records and Project scaffolding. It works with npm and Model Context Protocol. The repository describes itself as: 🛠️ The meta-harness for AI agents — scaffold your own focused, branded agent harness with its own npx CLI, MCP server, memory, learning loop, and witness-signed releases. Works… The licence is MIT.
Read from SKILL.md and the folder at commit e0dfd44. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Diag Harness loads about 835 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 282 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ruvnet/metaharness at commit e0dfd44, republished under its MIT licence (© ruvnet). 282 words, ~835 tokens.
.claude/skills/diag-harness/SKILL.md (or your agent's skills folder).Codex skill: kernel-version skew check for a scaffolded harness — the ADR-027 diagnostic UX loop.
Single-question check: does my local @metaharness/kernel match what this harness was scaffolded against? That's the cross-machine compatibility question almost every "this harness doesn't work" support ticket turns out to be.
Reads .harness/manifest.json:
| Field | Source | Meaning |
|---|---|---|
meta.surface | iter 56 | Which surface produced the harness (cli or web-ui) |
meta.kernel_version | iter 58 | The @metaharness/kernel version stamped at scaffold time |
Resolves the local @metaharness/kernel via createRequire rooted at the harness's own package.json (real Node resolution). Computes the skew verdict and prints a copy-pasteable next step.
| Verdict | Exit | Message |
|---|---|---|
match | 0 | PASS kernel versions match exactly |
patch-diff | 0 | WARN patch-level skew (usually safe; may include bugfixes) |
minor-diff | 1 | WARN minor-level skew (new kernel features may be missing) + Run: npm install @metaharness/kernel@X.Y.Z |
major-diff | 1 | FAIL MAJOR skew — APIs may have changed; expect breakage + Run: npm install @metaharness/kernel@X.Y.Z |
no .harness/manifest.json at path | 2 | FAIL no .harness/manifest.json found at this path |
/diag-harness # cwd
/diag-harness path=./my-harnessharness diag # cwd
harness diag ./my-harness # explicit path
harness diag ./my-harness --json # machine-readable for CI
harness diag ./my-harness --bundle # support-ticket JSON (iter 90)The --bundle form (iter 90) emits a single JSON snapshot of the diag report + sanitised manifest + @metaharness/* deps + Node/platform info — everything a maintainer needs to triage a bug report. Object keys matching secret|token|key|password|api_key are redacted so the bundle is safe to paste into a public GitHub issue.
harness diag — checking /tmp/my-harness
surface: cli
manifest kernel: 0.1.0
installed kernel: 0.1.0
PASS kernel versions match exactly@metaharness/kernel in a harness's package.jsonharness doctor fails with cryptic shape errors (skew is the usual cause)scaffold (create-agent-harness)
↓
your code lives in the harness
↓
diag (this skill) <- before anything else, check compatibility
↓
doctor / validate / sign / publishmanifest.meta.surface addedmanifest.meta.kernel_version stamped at scaffold timeharness diag subcommand© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude-plugin/skills/diag-harness of ruvnet/metaharness.
Open the folder on GitHubat commit e0dfd44
Diag Harness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diag Harness this skillruvnet/metaharness | 696 | — | ~835 | Automated safety check: Pass | MIT | |
| Tsed CLItsedio/tsed | 3.1k | — | ~2.7k | Automated safety check: Pass | MIT | |
| MCP Server Trello Releasedelorenj/mcp-server-trello | 445 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Appbuilder Project Initadobe/skills | 197 | — | ~6.4k | Automated safety check: Notes | Apache-2.0 | |
| Cabloy Spec Generationcabloy/cabloy | 982 | — | ~3.2k | Automated safety check: Notes | MIT | |
| Init Tauri Appglebis/claude-skills | 391 | — | ~1.5k | Automated safety check: Pass | MIT |
tsedio/tsed
Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…
delorenj/mcp-server-trello
Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.
adobe/skills
Initialize an Adobe App Builder project end-to-end and prepare the machine to build one.
cabloy/cabloy
A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.
glebis/claude-skills
Scaffold a new Tauri v2 project with the cenno/cull house conventions — delegates boilerplate to npm create tauri-app, then layers an opinionated core plus opt-in modules (CLI+MCP, SQLite…
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
ruvnet/metaharness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI.
ruvnet/metaharness
Diff two scaffolded harnesses (ADR-031). An agent skill from ruvnet/metaharness.
ruvnet/metaharness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot…
ruvnet/metaharness
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture.
ruvnet/metaharness
7-section readiness scorecard for a LOCAL repo. An agent skill from ruvnet/metaharness.
ruvnet/metaharness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness.
Works with
Categories
Kernel-version skew check (ADR-027). An agent skill from ruvnet/metaharness. Diag Harness is an agent skill from ruvnet/metaharness. Kernel-version skew check (ADR-027).
Diag Harness fits situations like: tasks that involve Architecture decision records; tasks that involve Project scaffolding.
Run `npx skills add ruvnet/metaharness --skill diag-harness -a claude-code`. Or copy the skill folder (.claude-plugin/skills/diag-harness in ruvnet/metaharness) into .claude/skills/diag-harness in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ruvnet/metaharness --skill diag-harness -a codex`. Or copy the skill folder (.claude-plugin/skills/diag-harness in ruvnet/metaharness) into .agents/skills/diag-harness in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/metaharness --skill diag-harness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diag-harness, .gemini/skills/diag-harness, .github/skills/diag-harness and .opencode/skills/diag-harness in your project.
SKILL.md names no scripts, command-line tools or credentials: Diag Harness is instructions for the agent only. Our summary lists: Node.js.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Diag Harness is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 835 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Diag Harness: Tsed CLI (tsedio/tsed, 3.1k stars), MCP Server Trello Release (delorenj/mcp-server-trello, 445 stars), Appbuilder Project Init (adobe/skills, 197 stars) and Cabloy Spec Generation (cabloy/cabloy, 982 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ruvnet (a GitHub user) maintains it in ruvnet/metaharness, which has 696 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 10, 2026.
Source: ruvnet/metaharness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.