Create a Skill
Open the Skills section and write the primary document. Describe the method, the standard, the approach — everything an agent needs to perform this kind of work correctly.
Skills are packaged expertise that agents draw on whenever the work calls for it. Capture a method once, attach it across your workforce, and every agent applies it consistently — every time.
Prompts describe a request. They do not carry the method behind it. So the quality of specialized work ends up depending on who asked, how they asked, and which agent picked it up.
Expertise that cannot be attached is expertise that cannot scale.
Specialized knowledge — how to write a certain kind of document, how to run a certain process — lives in the people who know it. Getting agents to apply it means re-explaining it every time.
Without structured methods to draw on, agents improvise. The same type of work produces different results depending on how a request is phrased or which agent handles it.
Even when someone documents a process, distributing it, keeping it current, and making sure the right agents use it is more overhead than most teams can sustain.
A Skill is a structured document that tells an agent how to perform a specific kind of work. Attach it once, and agents draw on it whenever it is relevant — automatically, consistently, without being asked.
Every Skill starts with a primary document that explains how the work should be done — the method, the approach, the standard to follow. Written and maintained in a rich, intuitive editor.
Add any number of supporting materials to a Skill — templates, examples, reference guides, or additional documentation. Agents pull in what they need when the work calls for it.
Agents decide when a Skill is relevant. When a request or a set of instructions matches, the agent ingests the Skill — and its references — and applies the method to guide its work.
Skills can be attached to agents, Spaces, Tasks, Flows, and templates. One Skill, captured once, applied across everything that needs it.
Every Skill is governed like any other resource on Opal. Version history, access permissions, and an optional publishing workflow keep Skills accurate, controlled, and trustworthy over time.
Knowledge gives agents context — what the organization knows about its business. Skills give agents method — how to perform a specific kind of work. Both matter. They serve different purposes.
Open the Skills section and write the primary document. Describe the method, the standard, the approach — everything an agent needs to perform this kind of work correctly.
Attach supporting documents to the Skill — templates, examples, process guides, anything that helps an agent do the work to the right standard.
Connect the Skill to the agents, Spaces, Tasks, Flows, or templates that need it. A single Skill can be reused across as many places as relevant.
When an agent encounters work that matches the Skill, it ingests the Skill and its references automatically — applying the method without needing to be told.
When the method changes, update the Skill in one place. Every agent and workflow that draws on it reflects the updated approach going forward.
Agents apply the same validated method every time a Skill is relevant, so specialized work does not depend on how well a request is phrased or which agent handles it.
A single Skill can be attached to agents, Spaces, Tasks, Flows, and templates — so expertise captured once flows across your entire digital workforce.
Agents ingest a Skill when the work calls for it. Irrelevant Skills stay out of the way, keeping each agent focused on what matters for the request at hand.
A rich editor and intuitive interface mean the people who hold the expertise can create and maintain Skills directly — no technical setup required.
Version control, permissions, and an optional publishing workflow apply to every Skill — so teams can keep methods accurate, control who can change them, and ensure agents always work from a reviewed, approved version.
Real work is rarely one method. Teams build sets of Skills that together define how an agent operates, how a task should be done, and how a flow should work.
A product marketing lead doesn't write one Skill — she builds a library. Each Skill captures a piece of how documentation gets done: the standard, the naming conventions, the review bar. Together they define how the documentation agent operates. Add a Skill and the agent gets sharper; update one and every future document reflects it — without anyone re-explaining the process.
Skill set
A consulting firm's methodology isn't one document — it's a stack of them. The team turns each part into a Skill and attaches the set to the draft report task. The Skills define how that task should be done end to end, so every report follows the same method regardless of who initiates it or how the prompt is phrased.
Skill set
A senior operations analyst breaks her process into Skills — one per decision point, each with her templates and worked examples. Attached across the steps of the review flow, they define how the flow should work. When she's away, the flow keeps running her way, without the delays that come from single points of expertise.
Skill set
Granular permissions determine who can view, create, and edit each Skill — keeping sensitive methods and organizational know-how protected.
Every change to a Skill is tracked. Teams can review the history of a Skill, understand what changed, and roll back when needed.
Skill-level publishing workflows ensure changes are reviewed and approved before agents act on them — critical when methods inform regulated or high-stakes work.
Opal does not retain prompts or outputs at the model level. Agent conversations and Skill-informed outputs stay within your organization's data boundary.
All actions on Skills are logged — creation, edits, permission changes, and publishing events — providing a complete, reviewable record.
ISO 27001, ISO 42001, and SOC 2 Type II certifications are underway.
Capture your organization's expertise in Skills and put it to work — consistently, at scale, across every agent and workflow on the Agentic Operations platform.