Sign inBook a briefing
Skills and AI buttons

Every AI button, explained and under control.

Behind every AI button in Nexus is a skill that sets its instructions, what it reads and which tools it may use. Skills are written, tested and approved like code, and anyone can right-click a button to see what it will do before pressing it.

Right-click to see what runsTested before every changeRolled out in stages
nexus · the right-click menu on a buttonSample data
What a button runs, shown from the button itself
Right-click any button. Finding out what “Explain this delay” runs before pressing it, from the button itself.Sample data
The library

Every skill in one place, with an owner.

Find, add, copy, merge and retire skills. Each has an owner, a cost and a record of how well it does its job, and near-duplicates are found before they multiply.

The skills library

Find, add, change, copy, import, merge and withdraw skills.

  • An owner for every skill
  • Cost per skill and unit
  • Duplicates found and merged
nexus · skills · the librarySample data
The skills library
The library. Finding, adding and withdrawing skills.Sample data
Changing a skill

Tested on real cases before anyone relies on it.

A change to a skill is drafted, run against past cases in shadow and checked by a model from another family. Changes that let a skill write, not just suggest, need a second approver.

The skill editor

Draft a new version of a skill and test it before review.

  • Instructions, tools and examples
  • Tests beside the editor
  • Cost shown per run
nexus · the skill editorSample data
Drafting a new version of a skill
The skill editor. Drafting version 4 of the skill behind “Explain this delay”.Sample data
Rolling out

Out in stages, back in one step.

New versions go to a small share of runs first. If quality drops, the rollout stops and goes back to the old version. Bad results reported by people become test cases, so the same mistake is caught next time.

Versions in stages

  • A small share of runs first
  • Quality compared live
  • Back in one step
nexus · skills · versions in stagesSample data
A new skill version on a small share of runs
Versions in stages. Watching version 4 on a small share of runs before it goes to everyone.Sample data
Your own version

Make it yours, inside the limits.

People can make their own version of a skill: plainer, shorter, with their own examples. Their version can never reach further than the original.

  • One personal version per person
  • Never more reach than the original
  • Shared with the team if it works
nexus · personal versions and their limitsSample data
Making a personal version of a skill
Personal versions. Making a personal version of “Draft a reply”: plainer, shorter, with a different example.Sample data
Questions

About skills and AI buttons.

Can people see what an AI button does?

Yes. Right-click any AI button to see the skill, the model, what it reads and who changed it last.

Do skills work in code editors?

Yes. Skills can be written and tested in your own editor and sent through the same approval path.

Book a briefing

Look behind one button.

Pick the AI button your team uses most. We will show what runs behind it and how to make it better.