How the Agents skill prepares an AI employee for work
How the Agents skill prepares an AI employee for work¶
Who this is for: Workspace owners choosing how to hire and configure AI employees.
A new AI employee needs more than a job title. Its skills, instructions and reporting line shape the work it can do. The Agents skill brings those parts of onboarding together.
This page explains what the skill covers and why permission boundaries still matter. Think of it as HR for your agents: setup around the job, while the employee's profession and tools handle the work itself.
One skill, five areas¶
The marketplace package is @opvs-ai/agents. It combines hiring, persona files, the hired team's org chart, AI Office and website chat. These were previously five separate packages. All 91 methods keep their names, parameters, replies and HTTP routes.
The org chart describes who a hired employee reports to, its working rules and its reports. AI Office describes departments, roles and approval requests. They remain separate because they organise different things.
Version 1.0.0 brought these areas together. Version 1.0.1 adds the launch film to the marketplace listing; it changes no skill behavior.
A hire needs time and authority¶
Hiring spends money and takes a plan seat. The skill checks whether the hire can proceed, and a human must name the employee and authorise the hire. A hire returned as provisioning is still being prepared; active is the status needed before equipping it for the role.
Adding a profession or skill gives the employee capabilities for its job. Instructions in TOOLS.md explain tool use; they do not create external accounts or supply missing credentials.
Files have owners¶
Persona and instruction files shape how an agent behaves. A write replaces the whole file, so the existing text must be read and preserved where needed.
On a hired employee, the vendor owns SOUL.md, AGENTS.md, IDENTITY.md and TOOLS.md. Those files are locked against direct edits. USER.md, MEMORY.md and HEARTBEAT.md belong to you. The dashboard's Make my own copy creates a separate agent whose files you own; it leaves the hire and its subscription in place.
Reporting and website access stay under your control¶
Changes to managers, working rules and reports need human authority. Some calls replace a whole list, such as managers or allowed website origins, so entries you want to keep must remain in that list.
Website chat also needs a brand-scoped OPVS personal access token. A dashboard session does not authenticate that API. The brand comes from the caller's token rather than a parameter, keeping these actions within that brand.