Found during the #318 pre-release pass on v0.0.10 (macOS), part three, walking agent-skills.html as a reader and following it literally — which is the only way this shows up, because everything on the page is plausible.
I installed the skills before starting the pass and used them throughout, so this is what the page costs somebody doing the same.
The install block cannot be run
git clone https://github.com/MeshBench/meshbench-scripting-skills
git clone https://github.com/MeshBench/meshbench-dev-skills
| URL |
today |
MeshBench/meshbench-scripting-skills |
301 → MeshBench/agent-skills — the clone works, on a redirect, and lands in a directory with a different name |
MeshBench/meshbench-dev-skills |
404 |
So the second line fails, and the symlink example four paragraphs down references $PWD/meshbench-scripting-skills/skills/…, which is not the directory the first line actually created.
The table names three skills, two repositories and one skill that is not published
| `meshcoresim` | … | `meshbench-scripting-skills` |
| `meshbench-scripting` | … | `meshbench-scripting-skills` |
| `wb2-design-language` | … | `meshbench-dev-skills` |
Against what is actually published in MeshBench/agent-skills:
- the skill is
meshbench-driving, not meshcoresim. meshcoresim is its directory name inside the MeshBench repository (.claude/skills/meshcoresim/); the published, loadable name is meshbench-driving, and that is what a reader has to type to invoke it directly.
wb2-design-language is not published at all, deliberately. agent-skills/README.md says so in its second paragraph: "The ones for developing MeshBench itself are not published, because the only place that work happens is a checkout of the repository." So the page's third row, and the second clone line, describe something that was decided against.
Two of the three rows in "The three skills" therefore do not match what a reader can get.
The plugin route is missing, and it is the one that works
agent-skills/README.md documents a marketplace install that this page does not mention:
/plugin marketplace add MeshBench/agent-skills
/plugin install meshbench@meshbench-skills
with the note that plugin skills are namespaced, so they are meshbench:meshbench-driving and meshbench:meshbench-scripting when installed that way. For the one agent row the page says is verified — Claude Code — that is the shortest correct path and it is absent.
repositories.md carries the same two names
| `MeshBench/meshbench-scripting-skills` | agent skills for driving and scripting a workbench |
| `MeshBench/meshbench-dev-skills` | agent skills for developing MeshBench |
One redirects, one 404s, and the page is titled "Repositories and licences", which is where a reader goes precisely to find out what exists.
Suggested fix
- One repository,
MeshBench/agent-skills, everywhere.
- Two skills:
meshbench-driving and meshbench-scripting, under their published names.
- Drop
wb2-design-language from the table, or keep the row and say plainly that it lives only in the MeshBench checkout and is not published — which is a fair thing to say and answers the question the row raises.
- Add the
/plugin marketplace add route for the Claude Code row.
Separately, two things the skill text itself gets wrong
Filed against the MeshBench repository, since that is where the skill's source lives, but noting them here because this page is how they reach a reader: meshbench-driving says session.describe lists every verb (it answers four facts; session.verbs is the one), and gives $XDG_RUNTIME_DIR/meshbench.sock as the address without saying it is Linux-only.
The rest of the page is good
The per-agent directory table, the honesty about only the Claude Code row being verified, the symlink-versus-copy advice and the "agents that upload rather than read a directory" section are all sound, and the linked further reading resolves (three of those links are 308 redirects to the same page, which is fine).
Found during the #318 pre-release pass on v0.0.10 (macOS), part three, walking
agent-skills.htmlas a reader and following it literally — which is the only way this shows up, because everything on the page is plausible.I installed the skills before starting the pass and used them throughout, so this is what the page costs somebody doing the same.
The install block cannot be run
MeshBench/meshbench-scripting-skillsMeshBench/agent-skills— the clone works, on a redirect, and lands in a directory with a different nameMeshBench/meshbench-dev-skillsSo the second line fails, and the symlink example four paragraphs down references
$PWD/meshbench-scripting-skills/skills/…, which is not the directory the first line actually created.The table names three skills, two repositories and one skill that is not published
Against what is actually published in
MeshBench/agent-skills:meshbench-driving, notmeshcoresim.meshcoresimis its directory name inside the MeshBench repository (.claude/skills/meshcoresim/); the published, loadable name ismeshbench-driving, and that is what a reader has to type to invoke it directly.wb2-design-languageis not published at all, deliberately.agent-skills/README.mdsays so in its second paragraph: "The ones for developing MeshBench itself are not published, because the only place that work happens is a checkout of the repository." So the page's third row, and the second clone line, describe something that was decided against.Two of the three rows in "The three skills" therefore do not match what a reader can get.
The plugin route is missing, and it is the one that works
agent-skills/README.mddocuments a marketplace install that this page does not mention:with the note that plugin skills are namespaced, so they are
meshbench:meshbench-drivingandmeshbench:meshbench-scriptingwhen installed that way. For the one agent row the page says is verified — Claude Code — that is the shortest correct path and it is absent.repositories.mdcarries the same two namesOne redirects, one 404s, and the page is titled "Repositories and licences", which is where a reader goes precisely to find out what exists.
Suggested fix
MeshBench/agent-skills, everywhere.meshbench-drivingandmeshbench-scripting, under their published names.wb2-design-languagefrom the table, or keep the row and say plainly that it lives only in the MeshBench checkout and is not published — which is a fair thing to say and answers the question the row raises./plugin marketplace addroute for the Claude Code row.Separately, two things the skill text itself gets wrong
Filed against the MeshBench repository, since that is where the skill's source lives, but noting them here because this page is how they reach a reader:
meshbench-drivingsayssession.describelists every verb (it answers four facts;session.verbsis the one), and gives$XDG_RUNTIME_DIR/meshbench.sockas the address without saying it is Linux-only.The rest of the page is good
The per-agent directory table, the honesty about only the Claude Code row being verified, the symlink-versus-copy advice and the "agents that upload rather than read a directory" section are all sound, and the linked further reading resolves (three of those links are 308 redirects to the same page, which is fine).