Essentials

For: tenant administrators and plugin users.

Install ai.oz0/essentials to get the verified plugins as a set at versions chosen to run together. The set has no tools, agents or flows of its own.

One install decision covers each member's exact version, source and access to the other members. Once installed, the members behave as ordinary plugins.

The members are the ai.oz0 connectors and the reference capabilities that use them: each capability's connectors are in the set, so its grants are asked once, on the same screen.

Its evals

Evaluated together: 3 evals (7 cases), last passed 2026-10-19.

• pr-reviewer reviews a pull request through github: the review flow posts its review as a comment through github's comment function.
• merge-when-green on github: a green pull request is merged at its head commit; failing checks and a draft get a comment and wait.
• support-triage triages Jira Cloud tickets through atlassian and acknowledges them through email: a ticket is labelled, assigned and acknowledged; an unsure triage waits for a person first; an empty search triages nothing.

What the evals check is the members together, at their pins:

• Each tool step is the member's own code. github's, email's and support-triage's functions run at the set's versions against the fakes their own tests use: GitHub's REST API, the platform's mail route, nothing at all for support-triage's own steps. atlassian runs no code of its own (Atlassian's MCP server does the work), so its steps are answered by the fake of that server in atlassian's tests, which lists only the functions of atlassian's pinned listing and refuses the rest.
• The flows' own logic runs on what the members answer, with the platform's expressions and recorder, so a member whose answer changes shape or meaning changes the flow's outcome.
• Models and people are recorded. The agents' answers are recorded model answers, as an eval's cassette holds them, and the approval is a recorded decision.

make test-essentials runs them live from a checkout of this repository and fails when a member answers otherwise than the recorded steps; oz0 plugin test plugins/essentials and the quality gate replay those steps, so no case reaches an outside service. ServiceNow, web and memory are members the evals do not run: their own tests and evals cover them.

A new version of the set pins newer plugins only after the evals pass again.

Install

oz0 plugin install hub:ai.oz0/essentials

The install shows the set's members and what it does with each, then each member's own needs, what it may do and what it reaches, and asks once. A member you have already:

• at the set's version is kept and asks nothing;
• at an older version is updated to the set's, checked against the plugins that use it;
• at a newer version, or from another source than the set's (another publisher's listing, a fork, another commit), is kept, and marked as different from the combination the evals ran on.

Each member then needs what it needs on its own: connect GitHub, Atlassian and ServiceNow, set the mail relay, and set the settings each one asks for (the members' pages say which).

After the install

The members are ordinary plugins. Update one as you would any plugin: the update is checked against the plugins that use it, and the set's page marks a member that is off its pin. The set's pins say which versions its evals ran on together, not what must stay installed. Removing the set removes the members it installed that nothing else uses (no other plugin's grant or uses:, an optional one included, and no other set), and lists the ones that stay, with why.

"Verified" means the project tested, pinned and secured these plugins, never that a vendor of the systems they reach endorses them.