Recorded once
Renewal variance brief
Turns licence-renewal exports into an executive variance brief with evidence links and a decision list.
5 measured takings · Microsoft Skill Recorder export · illustrative scenario
Owned agents and reusable skills sit together with provenance, reach and attestation attached.
The agents working across Contoso, the governed skills people can reuse, what each asset is for and what it is allowed to reach.
Every agent this page can see, counted once, in the section it belongs to.
Every agent this page can see, counted once, in the section it belongs to. An agent nobody has registered anywhere is an agent this product cannot see at all — which is the sentence at the top of this page.
Aristo's own register, your tenant's agent registry and the Copilot catalogue read.
Basis: Counted
| Origin | Agents | Share of total |
|---|---|---|
| Provided with Aristo | 2 | 16.7% |
| Built here | 4 | 33.3% |
| Registered in your tenant | 3 | 25.0% |
| In the Copilot catalogue | 3 | 25.0% |
Your own workflow, not a run state.
A stage is a record of YOUR process, not a statement about whether an agent is running — Microsoft exposes no run state for one, and this product never invents it.
The agent register's own lifecycle records.
Basis: Self-attested
| Stage | Agents |
|---|---|
| In review | 1 |
| ODAT | 1 |
| Approved | 1 |
| Draft | 1 |
Each stage is recorded by the people who moved the agent through it. Self-attested, and labelled as such wherever it appears.
Three ways in — prompted, adapted, or recorded — and one governed shelf. Inventory and measured taking stay separate.
Prompted here
2
1 ship-ready
Found and adapted
2
2 ship-ready
Recorded once
2
1 ship-ready
Taken by somebody
4
downloaded or Graph-confirmed push
Still shelfware
2
exists, but nobody has taken it
Movement
3 more takings than last month.
2026-08 vs 2026-07
In a connected tenant, a signed-in leader can paste or upload the recorder's SKILL.md here. This illustrative scenario is read-only, so it shows the governed shelf without offering a write that would pretend to work.
The recording happens on your own machine — the recorder captures your screen locally.
Its Analyze step is the part to know about: that one sends screen frames, window titles and URLs, and your spoken narration to GitHub’s cloud to turn the demonstration into a skill.
So never record credentials, secrets, or a screen with tenant-sensitive data on it. Record the job, not the sign-in.
Aristo never receives or stores a recording. The only thing that reaches us is the finished SKILL.md you choose to bring — that is true by architecture, not by policy.
Recorded once
Turns licence-renewal exports into an executive variance brief with evidence links and a decision list.
5 measured takings · Microsoft Skill Recorder export · illustrative scenario
Found and adapted
Adapts a governed presentation workflow into a concise quarterly business-review narrative.
2 measured takings · Approved internal skill library · illustrative scenario
Prompted here
Builds a consistent risk synopsis from a procurement questionnaire without inventing missing evidence.
1 measured taking · Created in Aristo · illustrative scenario
Recorded once
Records the close checklist and escalation path; two quality checks still need revision before release.
No measured taking yet — shelfware, not “used” · Microsoft Skill Recorder export · illustrative scenario
Found and adapted
Adapts an enablement playbook into role-based sessions, prompts and follow-up measures.
1 measured taking · Approved internal skill library · illustrative scenario
Prompted here
Draft skill held for review because its escalation and source-boundary instructions are incomplete.
No measured taking yet — shelfware, not “used” · Created in Aristo · illustrative scenario
There are no per-person rows here. Maker cohorts remain subject to the 5-person privacy floor, and a skill is never called “used” merely because it exists.
Ready to upload today. These ship with the product — nobody in your organisation has to maintain them.
Board-ready answers on your organization’s Frontier Firm score, strategy, maturity, department chargeback, and license position, grounded in the same counted signals as Aristo’s reports.
A personal working-habits assessment for executives: it examines the evidence available in your Microsoft 365 permission boundary and applies Aristo’s Executive Score rubric, with coverage and confidence shown.
Every agent Aristo has built for one of your people, newest first. 4 in the register.
Pulls the seat position, the idle block and the renewal date into one page a week before any supplier call.
Finds the closest past proposal to a new one and says which parts of it were reused and won.
Walks the finance close in order and says which step is waiting on whom.
Answers a new starter the way their own team would, from the documents that team actually keeps.
Agents Microsoft reports for your tenant. Aristo surfaces them; your IT governs what actually runs.
Answers a question from the knowledge base and drafts a ticket update for a person to send.
Checks a new supplier pack against the register and lists what is missing.
Files matched invoices and raises the unmatched ones to a person each morning.
Read from Microsoft's Copilot agent catalogue for your tenant.
No purpose was recorded when this agent was made. Aristo shows the gap rather than writing a sentence on its maker's behalf.
No purpose was recorded when this agent was made. Aristo shows the gap rather than writing a sentence on its maker's behalf.
No purpose was recorded when this agent was made. Aristo shows the gap rather than writing a sentence on its maker's behalf.
Every agent under Built here is a real package in the register represented by this view. The purpose on each card is the sentence its maker recorded — Aristo quotes it and never rewrites it. Security answers are the maker's own attestation, captured before the forge would build, and they are labelled attested rather than measured everywhere they appear.
A maker is named only where your organisation has turned on named recognition and that person has personally agreed to it. Both are required. The count of how many people have built something is a count of people, so it follows the same 5-person floor as every other group in this product.