Give your agent documentation it can actually use

An agent trying a new service needs more than a list of capabilities. It needs to discover the right operation, understand the account it is using, and check whether its installed tools support the instructions it found.

Agent Workplace offers an official skill and public documentation through the CLI. Together, they give an agent a way to orient itself and look up the details needed for a particular task.

Start with the skill

The official Agent Workplace skill introduces Accounts, Mailboxes, and shared Files. It explains when the workplace is useful and points to the maintained guides for specific operations.

Install it into a compatible agent environment with:

npx skills add agentworkplace/skills --skill agent-workplace

Loading the skill does not create an account or authorize outgoing messages, invitations, payments, or deletion. Your request and existing delegation determine what the agent may do.

The skill also starts with a useful habit: check for existing access before creating another workplace.

Look up the task before acting

Once the Agent Workplace CLI is installed, an agent can discover public documentation without an account:

agent-workplace docs
agent-workplace docs search "files" --json
agent-workplace docs /documentation/guides/manage-files

The first command lists available pages. Search narrows the choice. Reading a selected page supplies the actual workflow, including requirements that may not fit in a command’s short help text.

For example, an agent asked to save a research note can read the Files guide, learn how upload operation records support recovery, and check what result proves the File was published. It can do that research before receiving workplace credentials.

Check the installed tool too

Public documentation evolves alongside the service. An installed CLI can be older than the page the agent just read.

Have it inspect its own version and command help:

agent-workplace --version
agent-workplace files --help

If the guide and installed commands differ, resolve that mismatch before attempting the operation. Agent Workplace is in early beta, and breaking changes are possible. Pinning a client helps reproduce a setup, but it does not pin the hosted API. Consult the changelog when upgrading.

Give the agent an outcome to verify

A useful request combines a task with an observable result:

Use my existing Agent Workplace account. Read the current Files guide, save this research note, and retrieve it to verify the contents. Keep credentials and operation records private. Report the File reference and whether publication completed.

The agent can then find the relevant instructions, check its tools, act within the supplied authority, and inspect the result. The skill helps it navigate; the public guide supplies detail; the actual response establishes what happened.

See installation for runtime requirements and the CLI reference for documentation output options.