mcpbeat

Od Tune Collab

nexu-io/od-tune-collab

Default reference pipeline for the tune-collab taskKind — pick a direction, patch-edit the existing artifact, critique, hand off.

3k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
83386
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/nexu-io/open-design --skill od-tune-collab

What comes with it

12 093 bytes besides the instruction
examples/hero-tune.html
open-design.json

The instruction itself

2 sections, as written by the author

od-tune-collab (scenario)

Spec §1 / §10.1 / §21.5 / §23.3.3: the canonical "iterate on an

existing artifact" flow. Inherits parentArtifactId from the

project metadata so the produced artifact's

ArtifactManifest.parentArtifactId is set automatically — the

artifact lineage chain stays intact across multi-turn tune cycles.

Default pipeline

{
  "stages": [
    { "id": "direction", "atoms": ["direction-picker"] },
    { "id": "patch",     "atoms": ["patch-edit"] },
    {
      "id": "critique",
      "atoms": ["critique-theater"],
      "repeat": true,
      "until": "critique.score>=4 || iterations>=3"
    },
    { "id": "handoff",   "atoms": ["handoff"] }
  ]
}

The handoff stage records handoffKind: 'patch' (or

'deployable-app' when the user opted in via

od plugin run --target deployable-app AND build-test ran

successfully somewhere upstream in the project's history).

How to use it

Copy the folder

Take nexu-io/od-tune-collab from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.