A skill packages how your team does a job, such as how to triage a phishing report, review an IAM policy or write a detection rule, so every agent that uses it works the same way. Skills are versioned, and every version is scanned for security issues before you publish it.
Use a skill when several agents or harnesses should follow the same method. Use knowledge for reference material such as policies, and a memory space for facts agents learn as they work.
Add a skill
- Go to Skills and choose to add a skill.
- Upload a ZIP file containing the skill's instructions and any supporting files. Only
.zipfiles are accepted. - Give it a name, a version in semantic-version format (for example
1.0.0) and optional tags so others can find it. - Add version notes: a short changelog of what changed in this version.
The new version starts as a draft, and its security scan starts straight away.
Scanning uses the workspace's global AI configuration. Set it up first in Connect your AI models.
Review the security scan
Every version gets a scan report before it can be published. The report shows:
| Section | What it means |
|---|---|
| Critical issues | Problems that should block publishing, such as instructions that try to override an agent's guardrails |
| High vulnerabilities | Serious weaknesses to fix before agents use the skill |
| Medium and low findings | Issues to review and fix when you can |
| Partial compliance | Checks the skill only partly meets |
Open View report for the detail, or Download Markdown to attach the report to a review or change ticket.
If the scan flags a malicious prompt, autobotAI warns you before publishing. You can upload a fixed version, cancel, or continue only if you have reviewed the finding and accept it.
Publish a version
- Publish makes a version available to agents. Only one version of a skill is published at a time, so publishing a new version replaces the previous one for every agent straight away.
- Unpublish withdraws the published version. A published skill must be unpublished before it can be deleted.
- Statuses are Draft, Published and Archived, and each version keeps its notes and scan report.
Roll out changes the way you would for code: upload a new version, review its scan, test it with one agent, then publish.
Use platform skills
Skills marked Platform are provided by autobotAI. You can't change them directly. Choose Fork to customize to make your own copy, adapt it to how your team works, and publish it when ready.
Give skills to agents
- Optimus: open Optimus settings and choose the skills, and versions, it may apply on the Skills tab. See Investigate with Optimus.
- Harnesses: when Optimus builds a harness, its agents use the skills you have assigned. See Build with AI Builder and Optimus.
Good practice
- One job per skill. Small skills are easier to review, test and reuse.
- Write the method, not the data. Keep secrets and customer data out of skills; agents get credentials through integrations.
- Treat a critical finding as a stop. Fix and re-upload rather than publishing over it.
- Use version notes. They are the change history reviewers and auditors read.