onplate
РусEng
All documentation

Bindings

A binding is the fact of an install: “skill X version 1.2.0 is installed into Claude, globally, at this path”. The Bindings section is the map of the managed copies onplate rolled out into your AI tools. If you want to know “what exactly did onplate install, and where?” — this is the place.

Three tabs: Skills, MCP and Subagents. Resources installed as part of a package are visible inside them too.

What you see for every install

  • the name and the version — which version exactly is deployed;
  • the AI tool and the scope: global or project (for project ones, the path to the project folder);
  • File — the exact path of the installed file or profile (for MCP, which config was changed);
  • the install date;
  • the scanner verdict — a “Dangerous” or “Suspicious” badge on a resource that has something against it.

The verdict right in the row

A dangerous resource used to look like any other in this list, even though this is the list that shows what actually sits inside your AI. Now the security scanner verdict is visible in the row on all three tabs. Only “Dangerous” and “Suspicious” are shown: a “safe” badge on every row would be noise, and its absence is not the same as a good score — so resources that were never scored carry no badge.

The badge is clickable and leads to the findings themselves:

  • a skill or a subagent — its card opens in the Storage or in Subagents with the findings panel already unfolded;
  • an MCP server — the server card opens with the findings panel unfolded;
  • a resource from a package — the package itself opens, scrolled to that resource and its score.

Filters

  • AI — installs of the chosen tool only;
  • Scope — all / global / project;
  • Outdated installs only — see below.

Outdated installs

When a new version of a skill is published in storage, the old installs do not go anywhere — they keep working, but they get an “↑ newer available: v…” mark. From there it is your call:

  • Update — roll the fresh version out over the old one;
  • switch the version — pick any version from the list, including an older one: useful when a new edition of the skill turned out worse in a particular AI.

The “Outdated installs only” filter shows everything that fell behind; the count is on the Dashboard as well. If everything is current: “No outdated installs”.

Orphaned installs

If a skill was removed from storage but the install stayed, it is marked “skill deleted from storage”. The file on disk keeps influencing the AI even though there is nothing left to manage it with. Press the trash icon — onplate removes both the file and the binding.

Removing an install

The delete button removes the install: the file is taken out of the AI folder, and for MCP the entry is removed from the config. The source skill, MCP server or subagent in storage is not deleted. For project installs onplate shows the exact path it is about to change and asks for a confirmation.

After the operation, open Orbi: a confirmed result means onplate re-read the binding map and saw the expected state. If the result is unconfirmed, refresh the tab and check the path before repeating — the file or the config may have changed partially.