Teach the procedure once. Stop pasting it every morning.

If you are pasting the handbook into the box every morning, you do not have a team.

You have a very fast intern with amnesia, and you are the amnesia.

A skill is the procedure, written once. How Clerk formats an invoice. When Mail CC's you. What Maker is not allowed to say about price. How Watch records a vendor quote. Teach it. Tag it. Let the next teammate use it without a meeting.

This is not "custom GPTs." This is not a personality. Helpful assistant is not a skill. "Chase unpaid invoices every weekday at 9, draft the reminder, stop before send, never CC legal on the first nudge" is a skill.

The job has to be writable

If you cannot write it like a hire, you do not have a skill. You have a vibe.

Talk the way you would on someone's first day. "Bell & Rowe is always late. Nice version first. Fourteen days, then the short one. You do not threaten. You do not invent a fee." That is a procedure. Chief can turn that into a document. You can edit the document. Clerk can run it on a clock.

People skip the writing because the model sounds smart in the demo. The demo does not know your footer, your entity name, or the fact that you never offer a discount on a Thursday. The skill is how that stuff stops living in your head.

Shared is the whole point

Clerk's invoice format should not be a secret Clerk keeps in a thread.

Maker will need the same number on the winter pricing page. Scout will need the same offer on a list. If each one "kind of remembers" a different version, you will ship three prices and call it a season.

A shared skill is how a team compounds. One procedure. Tags so it is findable. Invoice. Tone. Brand. Refunds. The Hartley path. When Mail needs the refund skill, it should not ping you for the paragraph you already approved in March.

A workspace holds the files. A skill holds the moves.

Keep living skills short. A procedure that reads like a novel will not be followed. A procedure that is three screenshots and a joke will not survive a second teammate. Write it like you want it done at 6:10 PM when you have already shut the laptop.

How Octopus expects you to teach

You describe the job like a hire.

Chief writes the process.

You edit it like a document.

That is the loop. You do not need to know how to code. You do need to be willing to say no to a sentence. If Chief writes "escalate as needed" and you leave it, you will get improvisation. Replace it with the actual rule. Needs you. Tap. Done.

Tags are how the rest of the desk finds the thing. Do not invent a taxonomy for fun. Invoice. Inbox. Calendar. Vendors. The words you would search at 7:04 AM.

You can hire, rename, or fire teammates whenever. The skill should survive the fire. If Mail leaves, the refund procedure is still there for the next Mail. That is the difference between a person-shaped chat and a studio.

What is not a skill

A dumped PDF of the employee handbook. That is storage. Put it in the workspace. Point the skill at the two pages that matter.

A personality. "Be punchy." Cool. Punchy where. Punchy to whom. Punchy on a late invoice is how you lose Bell & Rowe.

A giant prompt that tries to be every job. One agent with every tool and no owner gets vague fast. Each teammate holds one job, one schedule, one set of access. Skills are per job, shared where the jobs overlap.

A secret. Keys stay in the vault. A skill may say "use the Stripe key from the vault." It may not paste the key.

Teach it once, then watch a Tuesday

The first week is still a first week.

Run Clerk on the overdue list with the skill in place. Read the drafts. Edit the skill, not the vibe. If the footer is wrong, the skill is wrong. If the tone is wrong, the skill is wrong. Do not sit in the thread fixing each letter like a teacher with a red pen for the rest of the year.

Then let Maker borrow the format. If the number changes, you will see it, because there is one document.

$99 includes OSS models, a computer, and a board. Bring ChatGPT, Claude, or Grok if you already pay. Same desk. The skill is yours to export if you cancel. The point of teaching once is that you are not trapped in a prompt you cannot leave.

Stop being the handbook. Write it down. Let Chief draft. You edit. Clerk runs. Maker inherits. That is a team.