od-tune-collab

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/scenarios/od-tune-collab/SKILL.md

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).

Repository: nexu-io/open-design
Path: plugins/_official/scenarios/od-tune-collab/SKILL.md
Commit: 1a7a23d

Last updated: about 7 hours ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.