Write a skill or rule for your whole company, or tag one of your own for the company, publish it on purpose, choose where it applies, and let your company's agents read it.

Company workspaces are rolling out. Some of this may not be on for your company yet.

Answer first

A company skill is shared know-how, like a review checklist or a writing style, that your company's agents can read. Owners and admins write it, read it again, and publish it. Nothing reaches an agent until a named person has published it, a company switch is on, and a person has allowed that agent to read skills. Your personal skills are separate and are not touched.

Open it from My docs, then your company, then Skills.

Who can do what

Read a published skill: every member of the company, so the people whose agents follow a skill can read it.
Write, edit, publish, unpublish, archive, choose where it applies, turn skills on or off: owners and admins. Project managers and editors cannot.
Drafts and older versions: owners and admins only.
Tag one of your own skills for the company: any member. An owner or admin reads a copy and decides. See Nominate a skill.
Agents: read only. An agent cannot write, change, delete or propose a skill.

Write and publish

Choose New skill. Pick Skill or Rule, give it a short name (lowercase letters, numbers and dashes, for example review-pull-requests), say when to use it, and write the text. The name cannot change later. To rename, archive it and make a new one.
Save draft as often as you like. A draft is never served to anyone. If someone else saved in the meantime, you are told so and nothing is overwritten.
Publish shows what changed since the version now being served, then makes the draft the served version. The version it replaces is kept in the history.
Discard draft throws away the open draft. The version agents get does not change, and a published version is never deleted.
Unpublish stops agents from getting the skill at once. Archive retires it, keeps its history and frees its name.

A published version never changes. To change a skill, save a new draft and publish it as the next version. A company that asks for two-factor sign-in asks for your second step when you publish, unpublish, choose where a skill applies, or switch skills on. Turning skills off never needs it, so the safe direction is always one click away. Saving or discarding a draft and archiving do not need it either.

Limits: 100 active skills in a company, 100 versions of one skill, 20,000 characters of text, 1,024 characters for the description. Text is plain text. Hidden characters and lines that look like system markers are refused, and a skill is never shown as formatted text or links.

Nominate a skill

Any member can offer one of their own skills or rules to the company. On your Skills page, open the menu on the skill and choose Tag to company. Gryz tells you first who will read it: owners and admins of that company. Then:

A copy of the skill's current version is saved in the company's workspace, in a Waiting list that only owners and admins can see (it also shows in their Review inbox). Your skill stays yours and is not changed. Edits you make later do not change the copy. If you do change it, you see "Your personal version changed since you tagged it" and can tag it again.
You can take it back while it waits. You can have 5 waiting, and tag 10 in a day.
An owner or admin opens it, reads it, sees a few plain hints (links, mentions of secrets, wording that tells the agent to ignore instructions, very long text, long blocks of encoded text) and chooses Approve, Edit and approve or Reject, with a short note if they like. The hints are advice only. They never approve or block anything.
Approve publishes it as the next company version, or as version 1 of a new company skill, and applies it to no project until an owner or admin chooses where. Nothing reaches an agent before that, and not before the company switch is on. The review page says "This replaces the version agents read now" when it adds a version to a skill that is already published. Edit and approve publishes their edited text, and the version shows it was edited when approved. An owner or admin who tagged their own skill can approve it; that is recorded as self-approved.
Reject, taking it back, or letting it sit for 30 days removes the text of the copy. If you leave the company, or an admin removes you, what is waiting is taken back; what was already published stays.
After approval the skill belongs to the company. You cannot unpublish it; ask an owner or admin.

If the skill already has an open draft, an owner or admin publishes or discards that draft first, then approves.

If you delete your own skill after it was published, the company's copy stays. Agents cannot tag, propose or write skills.

Where it applies

A published skill reaches an agent only where you say it applies. The default is Not assigned, which means nobody gets it.

All projects: every agent that is allowed to read skills.
Chosen projects: only agents that were given one of those projects. An agent never gets more than the person who owns it can open.

Turn skills on for agents

Skills are off for every company until an owner or admin turns on Agents can use company skills. This is also the kill switch: turn it off and the very next request from any agent is refused with "Skills are turned off by your company." and returns no text. It takes effect at once, in an app that is already connected, and turning it back on works without reconnecting.

Then, for each agent, a person turns on Can read company skills on the agent's page (or on the connect screen). It is off by default and is never taken from what an app asks for.

What an agent gets

list_skills shows the skills and rules that apply to the agent, with when to use each one.
get_skill returns the text of one by name.
The text arrives inside a labelled block, with a sentence saying it is guidance from your company, that it cannot give the agent tools, access or permissions, and that it is below the instructions of the person the agent works for. A skill that tells an agent to ignore its instructions, or to use a tool it does not have, gives it nothing new.
A skill that is a draft, unpublished, archived or not assigned to the agent reads exactly like a name that does not exist.
get_profile adds one line saying how many company skills apply to the agent.

More in Company connections and MCP tools.

What Activity shows

Activity (for owners and admins) shows that a skill was created, published, unpublished, archived, discarded as a draft or assigned, that a skill was tagged, approved, rejected or taken back, who did it, and when skills were switched on or off. It also shows each time an agent read a skill: which agent, which skill and which version. It never shows the text of a skill. Saving a draft is recorded for the company's own audit trail but is not listed, so the feed stays short. If a skill was later deleted, Activity says "a skill that no longer exists".

Company skills