Orathon skills setup

One sentence sets up a person's AI skills

A company's shared skills live once, in its own Google Drive. Each person's private skills live in their own Drive. Someone joining a company pastes a single sentence into Claude and the setup happens in that conversation.

How a person starts

Every company has its own address. The sentence is the same every time, with the company's own address in it.

Set up my skills by following https://orathon.com/setup-skills/your-company.

Claude opens that page, works out whether the company is already set up, connects what it needs, builds the person's private skills, saves instructions that stick for future conversations, and tests the result. The person is asked only to sign in, approve something, or make a decision that is genuinely theirs.

What gets built

For the company, once. A shared AI router that tells everyone's Claude where to look, a registry of shared skills, the company's own rules, and a first shared skill for company branded decks. All of it in the company's own Drive, shared with the audience the administrator chooses, never public.

For each person, privately. A Personal Skills folder in their own Drive, restricted to them, starting with a skill that drafts email in their voice, built from their own sent mail. Orathon is never added to it.

What Orathon stores

A short registry record per company: a stable id and address, the display name, who its administrators are, a link to the company's own configuration document in Drive, the setup status, and the setup version. Nothing else. No mail, no writing profiles, no Google credentials, and no employee lists.

The address decides which configuration is used. Google permissions decide what a person can actually open.

For administrators

The first person to set a company up has to be authorized to do it. Having the address is not authority, and neither is an email domain. Registration happens at https://orathon.com/setup-skills/admin, where an administrator signs in with their work Google account and Orathon checks with Google Drive, from its own server, that the account can actually administer the location the company will live in. There is no code or password to type, and no way to register without that check.

Registered is not the same as ready. A company becomes ready only once its Setup Configuration document has been verified inside that shared location. Until then, other employees are not onboarded against it: they get their own private setup and the company connection is recorded as pending.

Anyone who is not the administrator can still finish their own private setup immediately.

Orathon. Procedure version 1.0.0. Questions: hello@orathon.com