Two different things that people mix up, so it is worth separating them first.

A skill is know-how. It teaches an agent how to do something well: your code review standards, how to structure a report, how to write a commit message the way your team does.

An integration is access. It gives an agent the credentials to reach an account: your email, your GitHub, your database, your storage.

You usually need both. A skill without access cannot act; access without a skill acts badly.

Skills

Skills are Markdown files. That is the whole format, and it is deliberate: you can read every word an agent was told, and so can anyone you work with.

They come from three places:

• The catalog. Around a hundred, covering research, code review, documents, spreadsheets, browsers, security and more.
• The marketplace. Community packs you can browse and add.
• Yours. Write one and attach it to a Solution or a bot.

A Solution stages its skills into every worker it starts, so the agent begins knowing your standards rather than being told them in a prompt each time.

Pinning

When you install a Solution, its skills are pinned to the exact version you installed. A later catalog update does not silently change how your jobs behave. You get an Update button, and you choose when.

Integrations

Settings has a catalog of around fifty services. Connecting one stores its credential in your Mac’s Keychain, and jobs that declare they need it get it injected at spawn, in that one box.

Some things worth knowing:

• It is key pasting, not one click OAuth, for most services. You get an API key from the service and paste it in. Honest, and it takes a minute.
• A job tells you before it starts if a connector it needs is not set up, so you find out on the launch sheet rather than four minutes into a run.
• Credentials never go to your phone and never touch a relay.

MCP servers

Operator speaks MCP, so an agent can use any MCP tool server you point it at. Add one in Settings and it becomes available to jobs that ask for it. This is the escape hatch for anything the built in integrations do not cover.

The marketplace

The marketplace at operatorok.com/marketplace lists open plugins: skills, bots and job packs. Adding one from the phone installs it like anything else in the catalog.

A good order to do this in

1. Connect the one or two accounts you actually work in.
2. Install the Solution that matches your work.
3. Run a job and see what it gets wrong.
4. Write one skill about that.

Most people over-collect skills before they know what they need. The fourth step is where the value is, and it takes ten minutes once you have seen the mistake.