Conflicts

Once there are many skills, they start arguing with each other. The classic example:

Skill A: “always answer as briefly as possible”. Skill B: “always spell the answer out in detail, with examples”.

The AI gets both instructions at once — and behaves unpredictably. The Conflicts section finds contradictions like that before they spoil your work.

Skills

Press Find conflicts — onplate analyzes the instructions of every skill in the catalog pairwise. For each conflict it finds you see:

• which two skills clash;
• the Reason — which instructions exactly contradict each other, with line numbers;
• What to do — advice: which skill to switch off, what to rephrase or merge.

If there are no contradictions, you see “No conflicts found”.

A conflict is best resolved through the Editor (rephrase the instruction and publish a new version) or simply by removing the install of one of the skills in Bindings.

MCP

The MCP tab catches a different kind of problem — collisions between entries in AI configs:

• A collision with somebody else’s entry — the AI config already has a server with the same name, added outside onplate; the install would overwrite that setting;
• Overwriting under a shared key — two of your servers claim the same name in the config, and installing one erases the other.

onplate shows both sides of the collision so you can decide which entry should stay.

Subagents

The Subagents tab catches what the MCP tab does, but in the AI’s agent directory. A subagent file is one per name (<agents>/<name>.md), so two of the same name cannot coexist: if the AI directory already holds somebody else’s file with that name, unmanaged by onplate, the install would overwrite it. Such cases are marked as a collision with a foreign file — naming the AI and the name.

The analysis on all three tabs is local only: onplate reads the directories and configs on your computer and sends nothing anywhere.