Guides

Teach it a recipe once. It keeps it forever.

A skill is a repeatable way of doing something — a morning brief, a call prep, a tidy-up — that your agents can pick up when the moment fits. You describe it in plain words; from then on it is just a thing they know how to do.

01The idea

A skill is a capability; an agent is who uses it

Teach it once. Any agent you grant it can do it.

Think of the difference this way. An agent is a specialist — a person you have hired for a kind of work. A skill is a capability that person can pick up: a named recipe for one repeatable task. An inbox-keeper agent might hold the skills for “draft a reply in my voice” and “flag anything urgent”; a researcher might hold “read around a topic” and “write a sourced summary”.

The reason to separate them is reuse. A skill lives in a shared library, not locked inside one agent. Teach “file this properly” once and you can grant it to every agent that ought to have it — and improving it in one place improves it for all of them.

What a skill is made of

You never write any of this out as fields — you describe it and 1Presence shapes it — but under the hood a skill is three plain things:

When it fires

The cue that brings it out — a phrase you say (“prep me”), or a moment in a routine when it fits.

What it does

The steps, in order — what to gather, what to check, how to put it together. Written in plain English, not code.

What it produces

The shape of the result — a one-page brief in a set folder, a reply drafted for your review, a tidy note.

Because it is all plain language, a skill is something you can open and read on its own page — see exactly what it does, which agents hold it, and when it last ran.

02Teach one

You build a skill by describing it

The same way you do everything else here: you say what you want in your own words, and 1Presence turns it into something precise, asking a sharp question or two where it needs to.

Create a skill
Whenever I say “prep me”, check my next meeting, pull context from my vault, and write a one-page brief.

It shapes a skill that triggers on “prep me”, gathers the right context, and files a brief in a set place — confirming the details with you.

Make a “morning brief” skill: my calendar, my unread mail, anything urgent, one page in Daily/.

It builds the recipe and saves it to your library, ready to grant to whichever agent should run it.

Teach it a “file this” skill that decides where a note belongs, writes it there, and cross-links it.

It captures the pattern as a reusable skill you can point at any conversation later.

Refine or share one
In my prep skill, also scan email threads with the attendees from the last couple of weeks.

It edits the existing skill in place — the change holds for every agent that uses it.

Give my inbox-keeper the “draft a reply” skill.

It grants that skill to that agent, so the capability is now part of what it can do.

My editor needs its own stricter version of the summary skill.

It forks the skill into a copy tailored for that agent, leaving the shared one untouched.

How teaching a skill goes

  1. 1

    Describe the pattern

    Say what the task is, when it should fire, and roughly what it should produce — a sentence or two is plenty.

  2. 2

    Answer a question or two

    1Presence checks the details that matter — the exact trigger, where the output should land, whether to include a source — right there in the chat.

  3. 3

    It saves it to your library

    The skill is written up in plain language and filed, with its own page you can open and read any time.

  4. 4

    Grant it to the agents that need it

    Hand the skill to one agent or several. Each one can now reach for it when the moment fits.

03When to use one

A skill, or a whole agent?

A quick way to choose. Reach for a skill when you want to capture one repeatable task — a thing you explain the same way each time and want done consistently. Reach for a whole agent when you want a standing specialist with its own focus, voice and set of skills — an inbox-keeper, a researcher — that you talk to directly and that gets better at its job over time.

They compose. A specialist agent is really an identity plus a handful of skills plus the connectors it can reach. And once you have a shelf of skills, building the next workflow becomes a matter of arranging what you already have, not inventing from scratch.

You do not have to start from a blank page, either. The Catalog keeps a shelf of ready-made skills you can copy and then shape to fit — often the fastest way to see what a good skill looks like.

It compounds

A private operating system for how you work.

Skills accumulate. Six months in, you have a library of them — each saving a few minutes of explanation, each producing a consistent result, each editable in plain words and shared across your agents. The way you work, taught once and kept.

Common questions

What is the difference between a skill and an agent?

An agent is a specialist — a standing assistant with its own focus and voice that you talk to. A skill is a single reusable recipe an agent can pick up. One agent can hold many skills, and the same skill can be granted to many agents. More on building agents.

Do I have to write any code or fill in a form?

No. You describe the skill in plain language and 1Presence shapes it into something precise, asking a question or two where it needs to. It reads as plain English on its own page, and you edit it the same way.

If I change a skill, does every agent get the change?

Yes — a skill lives in a shared library, so editing it once updates it for every agent that holds it. If one agent needs a different version, ask for its own copy and 1Presence forks it, leaving the shared one as it was.

Where do I find ready-made skills to start from?

The Catalog puts a shelf of ready-made skills on the add screen — copy the one closest to what you want and shape it to fit. See the Catalog guide.

Teach it the thing you explain every week.

Pick a task you describe the same way each time — a brief, a tidy-up, a draft — and turn it into a skill your agents just know.

Built by conversation. Edited the same way, any time.