Built-in skills
The instructions that help agents use Opser well, plus skills you add for your own workflows.
catalogue skills reusable instructions runbook risk assessment compliance tracking vendor review process documentation status reportOn this page
Instructions for doing the work wellThe built-in foundationsAdd your business's way of workingApp skills and optional installationsKeep the boundaries clearInstructions for doing the work well
A skill is a reusable set of instructions for a kind of task. It explains when to use it, what information to gather, the process to follow, and how to check the result. A tool performs an action; a skill helps the agent choose and use those actions.
Opser gives the agent descriptions of available skills so it can choose relevant guidance, then load the full instructions as needed. You can also ask it to use a particular skill. This keeps a task focused without requiring every instruction to be repeated in every message.
The built-in foundations
These skills describe how to use the core platform. They are separate from the optional catalog and your own business procedures.
Three built-in foundations: Data Management, Internal App Builder, and External App Builder. These teach workflows; they do not grant permissions.
| Foundation | What it teaches the agent |
|---|---|
| Data Management | Inspect and structure user-managed business data, import records, and respect data boundaries |
| Data Reporting | Turn business questions into useful queries and reports |
| Internal App Builder | Design, build, test, and review an app inside the workspace |
| External App Builder | Build a separate web experience with declared data access and deployment steps |
| Scheduling | Set up recurring or one-time work and check its timing and execution |
| Memory | Save useful facts, retrieve relevant background, and remove outdated information |
| Integrations | Discover connected services and choose supported operations and accounts |
The instructions do not remove a capability's prerequisites. For example, the app-building skill can explain the workflow even when building has not been enabled in that environment.
Add your business's way of working
Create a custom skill for a process you expect to repeat. Give it a clear name and describe the trigger, required inputs, steps, output, and checks. Test it with a representative example before making it part of routine work.
For a weekly operations review, use the supplied date range, summarize open work by owner, identify stalled items, and end with an action list. Keep currencies separate and link each finding to its source.
Choose the right scope. Skills can be available to an agent, shared through the business library, or required across the workspace when configured by an authorized user. Changes to shared instructions affect more than your current conversation.
App skills and optional installations
Installed apps can contribute guidance for their own records and workflows. The platform can make those skills available alongside the app's tools, subject to access.
The Skills area also lets you browse and install available optional skills. Catalog entries evolve, so use the catalog for the current selection rather than treating a list in the docs as a fixed product inventory. Inspect the instructions and choose the agent or workspace scope deliberately.
Keep the boundaries clear
A skill does not grant access, connect an account, or install an app by describing it. Its tools still require the right permissions, configuration, and any applicable approval. If a skill references an unavailable operation, resolve that dependency instead of assuming the instructions made it available.
Use context for stable facts, a skill for a repeatable procedure, and the conversation for the task at hand. See Built-in tools for the execution layer.