The methods other researchers already wrote down.
Somebody has solved the procedure you are about to write from scratch. The Marketplace is where they published it: tools that run real computation, skills that carry a method, plugins that chain a whole study, and MCP servers that connect the services you need. Add one in a click — or publish your own.
Already in EBONEX.
You install none of these: they ship with the product and the agent reaches for them when the work calls for one. Docking of every kind, molecular dynamics, interaction analysis and scientific writing.
What researchers have put up.
Click one to open it. If you are not signed in yet, you will be — and then you land on that package, ready to add.
Four kinds, and they stack.
You do not need to know which one you want. You need to know what each is for.
Open it, read what it touches, add it.
Nothing is added to your workspace without you reading what it is allowed to do first.

The package page
Every package has one: what it does, who published it, and — the part worth reading — its Access list. A tool that wants the web, your files, the browser, email, the schedule or notifications has to say so there, and you see that list before you decide. Nothing is hidden behind an install button.

Your copy, in your workspace
Adding a package copies it into your own library rather than linking to the publisher’s. It appears in your Tools or Skills list with its own switch, and if the publisher pauses or withdraws it tomorrow, the copy you added keeps working. What you installed does not stop being yours because somebody else changed their mind.
Publish what your group already knows.
A department’s standard procedure is worth more written down once than taught twenty times.

Write the file, upload it, send it for review
If what you have is knowledge — a protocol, a review standard, the way your group writes up a result — a declarative package is a single JSON file with no executable code in it. You can write it by hand today, upload it from the Marketplace and send it for review; the server validates it, it is scanned, and an administrator reads it before it goes live. If what you have is a program to run, the Documentation sets out the tool format and what backs it. For a department or institution programme, write to support@ebonex.co.uk.
Start now
Find the one you were about to build.
Open the Marketplace, add what you need, and get back to the question you actually wanted to answer.