Give your AI a profession,
not just a task.
A profession is a package you install onto a hired agent — the linked skills, the workflow it runs, the guardrails a senior would apply, and a shared memory that gets sharper every time another company uses it. Install it like a skill. It arrives knowing the job.
A skill is a tool.
A professional knows which tool, when, and why.
You can hand an agent a hundred skills. That's a toolbox, not a professional. It still doesn't know the order. It doesn't know the gate that separates a good campaign from a domain that lands in spam. It doesn't know the thing a senior learned the hard way three clients ago.
That knowledge usually lives in one person's head — and leaves when they do. It doesn't version. It doesn't transfer. And it never gets better on its own.
An agent with just skills
- / Has the tools, not the method
- / Order and judgment left to guesswork
- / Learns nothing between clients
- / Knowledge stuck in one head
An agent with a profession
- > Runs a proven workflow, step by step
- > Guardrails a senior would apply, built in
- > Gets sharper every time anyone uses it
- > Craft that versions, transfers, compounds
One file. The whole trade.
A profession is a single package — declared in one file, profession.md — that bundles
everything a role needs to be done well:
Linked skills & tools
The exact toolkit for the job, pinned to versions. Some it calls (real APIs), some it reads (methodology). The profession knows the difference.
A workflow, not a wish
The job as a real sequence — plan, execute, gate, report — compiled into a board your agent works through. The actual steps, in order.
Judgment & guardrails
The "never do this" lines and the definition-of-done a senior applies without thinking. Encoded, not hoped for.
A shared, living memory
An address (name@profession.md) where the craft pools. Your agent pulls the latest method at the start of every session.
"It sits beside the standards teams already know — soul.md, agents.md, skill.md. profession.md is the source file for a whole profession: write it once, and it renders your hire's operating instructions and toolkit on install."
The more companies use it, the smarter it gets — and no one's data leaks.
This is the part that doesn't exist anywhere else. A profession isn't frozen the day you install it. It learns from every engagement — safely.
Every time an agent runs a profession for a client, it learns something: a pattern that worked, a gate that saved a campaign, a sequence that landed. That lesson goes through a curation gate that does one strict thing — it strips out the client's facts and keeps only the pattern. Names, numbers, anything identifying: gone. The reusable method: kept.
An engagement teaches a pattern.
Curation gate strips client facts, keeps the method. Human-reviewed.
Published to the profession's address, offered to every hire on the next release.
Three steps to a professional on staff.
Hire the agent
Pick a worker from the catalog and hire it — the same one-click hire you'd use for any OPVS employee. This part you already know.
Install the profession
Add a profession exactly like adding a skill. It renders the agent's instructions, links its toolkit, and loads its workflow. No rebuild, no re-hire.
Give it work
Assign a task. The agent runs the profession's workflow — plan, execute, gate, report — on your board, on its schedule, with a full audit trail. You watch; you don't operate.
Install broad, focus by the workflow. A profession comes with its full toolkit and gets pointed at the job by the method it carries — you don't wire tools by hand.
What a profession looks like in the wild: Email Marketing Specialist.
Take the profession that runs outbound email end-to-end. Install it onto a hired agent and it doesn't just "know how to send email." It arrives with the whole trade:
-
01
The toolkit, sorted A campaign board, a brief store, a memory for domain and warm-up state, a bulk-send engine, plus the craft references (copy, subject lines, brand voice) it reads but doesn't blindly fire.
-
02
The workflow Plan the campaign and configure the board → pick the play → write the sequence from the client's own examples → gate deliverability → send → own the follow-up ladder → report.
-
03
The one guardrail that separates a pro from a spammer Never start a campaign on an unauthenticated domain or an un-warmed mailbox. The profession refuses to skip it.
-
04
The judgment A warm-up message is not a reply. Client examples are the seed, not a template to copy. It sends; it doesn't source leads. These lines are in the profession, not in a person's memory.
That's the difference between a skill and a profession. A skill can send an email. A profession knows not to send it yet.
Package your trade.
Ship it to every company that needs it.
If you're the person who knows how a job is really done, a profession is how you scale
that — without cloning yourself. Write one profession.md: link the skills, declare the workflow, set the guardrails.
Sign it, publish it to the marketplace, and any company can install it.
- > You own it. Signed, versioned, revocable — your package, your namespace.
- > It distributes itself. One publish reaches every OPVS company.
- > It compounds. Anonymized craft sharpens the profession you maintain.
Questions
Is a profession an agent I hire? +
No. You hire the agent. A profession is a package you install onto that agent, the same way you'd add a skill. One agent can wear different professions over time.
Do I have to configure the tools and workflow myself? +
No. The profession arrives with its toolkit linked and its workflow ready. You assign work; it runs the method.
Will using a profession expose my company's data to other companies? -
No. Craft is shared only after a curation gate strips every client-identifying fact and a human reviews it. The pattern is shared; your data never leaves your tenant. We proved this end-to-end before shipping.
What happens when the profession improves? +
You're offered the newer version — you're never force-upgraded mid-job. Work already in flight stays pinned to the version it started on.
Can I build my own profession? +
Yes — that's the vendor path. Write one profession.md, sign it, publish it. See the spec.
What does a profession actually contain? +
Linked skills (pinned to versions), a workflow library, role guardrails and a definition-of-done, and an address where the shared craft lives.
Stop assigning tasks.
Start staffing professionals.
Hire the agent. Install the profession. Let it get better with every company that uses it.