The Agent Reads Every File the Job Needs

Point the agent at the folder holding the sources. It reads every file the job needs in one pass and returns a finished document in the format the department circulates, parked beside the files it came from.

Record the standing corrections once in the rules file: which folder is authoritative, what stays untouched, how a figure is formatted in the house layout. From there each run is reviewed rather than rewritten.

Procedures Written During the First Real Run

Do the job once and narrate it while it happens. The reading, the dead ends and the order of the steps go into the skill file, so the next run follows the record instead of repeating the search.

Tune the trigger line against real requests until it matches the wording people actually use, then hand the start to the person who owns the task.

Mail, Calendar and Records Reached Under Existing Access

The agent reads the mailbox, the drive and the calendar as the account it acts for, through Microsoft Graph with delegated permissions. The data stays where it is, so the existing permission model remains the only one to maintain.

Withdraw access once in the directory and every connected surface goes with it. Give business-database connectors descriptions written in the office’s own German terms, so a half-remembered employee or building name resolves to the right record.

One task
already run every Monday becomes the first skill
By hand once
then recorded, then run from the skill it produced
1 tenant
the Microsoft 365 already paid for, reached where it is
Your account
the agent sees only what the signed-in person may already open

Building the First Skills on Work the Office Already Does

Where the Work Already Happens 3 steps
01

The Agent Is Configured Inside the Working Folder

Set the agent up in the folder where the documents live. Add a rules file stating how it behaves, give it a session directory it can inspect, and put the folder under version control on the first day. Research, drafting and file work are handed over there.
02

Whole Tasks Handed Over as Finished Files

Hand over the whole task: which source files to read, what to research, what to draft, and which format to return. Word, Excel and PowerPoint files come back in the layout the office already circulates. The person who owns the result reviews it and sends it.
03

Applications Without an API Driven Through Their Interface

For a supplier portal, a desktop application or any screen with no API, use browser and desktop automation: the agent reads the screen, clicks and types. Write each interface trap into the skill as a rule, such as a field set programmatically keeping the form's own default.
Reaching the Systems Already in Use 2 steps
04

Mail, Files, Calendar and Teams as Endpoints

Reach Outlook, SharePoint, OneDrive, the calendar and Teams through Microsoft Graph, as the person the agent acts for. Use delegated permissions in your own tenant, so the boundary Microsoft Entra ID already enforces stays the boundary. Two approvals switch it on: an administrator in Entra, the account owner in Claude.
05

A Connector for the System That Has No Connector

Wrap an existing REST API, a database or an internal service as a Model Context Protocol server. Describe each tool and its arguments in the vocabulary the office uses. The system behind it stays as it is, and the agent passes typed values instead of reading a screen.
Skills Built on Real Work 3 steps
06

Do the Job by Hand Once, Then Record What Happened

Run the job by hand once with the person who owns it. Record what was done, in order, including what cost time. Turn that record into the skill, and write each failure mode into it as a rule, such as an import that replaces every record it is not given.
07

A Skill Is Plain Markdown Anyone Can Read

Write the skill as a plain text file: the line that decides when it fires, the steps in the order they run, and the detail in reference files loaded only when their step needs them. Keep it beside the work it belongs to, in version control.
08

The First Skill Is One Monday Task

Pick one task somebody already performs every week and build the first skill on that real work, with the person who runs it. A weekly performance and search audit built this way runs on a schedule and files its own prioritised issue.
Supervision and Handover 2 steps
09

Every Write Runs Supervised and Verified

Run anything that mutates a live or remote system deliberately, with a verification step after it. Keep read-only integrations read-only, and keep credential values out of the procedure files: the file names the credential and its location. Loosen supervision one procedure at a time, on evidence from its runs.
10

Packaged for Whoever Owns the Task

Package the same recipes as skill folders the desktop experience picks up from the company's own file storage, so the owner of a task starts their own runs. For a team, bundle a command, a house-style skill and an internal connector into one installable unit.

Frequently Asked Questions

Do we have to replace the software we already run?
No. Microsoft 365 is reached through Graph inside your own tenant with delegated permissions, so Outlook, SharePoint, OneDrive, the calendar and Teams keep their licensing and their permission model. Two approvals switch it on: an administrator in Microsoft Entra, and the account owner in Claude. Systems outside the tenant get a connector, and applications with no API are driven through the interface a person uses.
Do we need a developer to run this day to day?
Not for running it. Editing a procedure is editing a text file, which puts it inside reach of a technically curious business user, and the desktop packaging lets the owner of a task start their own runs. A developer is needed where an internal system ships no connector of its own, which is a bounded piece of work.
Is our data leaving the country?
Content stays in the region your tenant is provisioned in, and the agent sees what the account it acts for may see. The integration reads in place, so no second copy is made. For services outside the tenant, and for the model provider, residency is settled per service in the compliance pass.
What is left if the person who set this up leaves?
The skills, the connectors and the rules files sit in your own storage under your own accounts, as text your people can open and change. Every integration signs in through the directory, and everything runs on company machines and company accounts. The handover test is whether somebody else runs Monday's job on Monday from the file alone.