Skills and tools
A skill is know-how, such as “Qualify a lead”. A tool is a single action in another system, such as “Create a HubSpot deal”. Skills tell an employee how to do a job. Tools let it do the job.
Skills
Section titled “Skills”A skill bundles three things:
| Part | What it contains | Example for “Qualify a lead” |
|---|---|---|
| Instructions | The steps, rules and quality bar, written in plain language. | Check company size and industry against the ICP, find the decision maker, score from 1 to 5, write a two-line rationale. |
| Examples | Sample inputs with the expected output. The employee uses them to match your standard. | Three past leads with their score and rationale. |
| Required tools | The tools the skill needs to run. | Web search, HubSpot: Read company, HubSpot: Update contact |
An employee picks the skills that match its task when it plans a run. You can also name a skill in the task, for example “Use Reconcile invoices on the March statements”.
When you add a skill to an employee, its required tools appear on the Onboarding tab. The employee can’t use the skill until every required tool is granted.
Create a skill
Section titled “Create a skill”Open the skill editor
Go to Skills > New skill, or open an employee’s Skills tab and click Add skill > Create new.
Write the instructions
Describe the job as you would to a new colleague. Keep each rule on its own line. Add what to do when information is missing.
Add examples
Add at least two examples. Good examples beat long instructions.
Pick the required tools
Select the tools the skill needs. Orqane shows each tool’s impact class, so you see at a glance which steps may need approval.
Test and save
Click Test to run the skill on a sample input in a sandbox, with no real actions. When the result looks right, click Save.
Skill versions
Section titled “Skill versions”Skills are versioned like employee definitions. Each save creates a new version, such as v4.
- Each employee uses a pinned version of each skill. When a newer version exists, the Skills tab shows Update available.
- Click Review update to see the diff, then Update to switch. Running tasks finish on the version they started with.
- Turn on Follow latest to always use the newest version. Use it for skills your own team maintains, not for marketplace skills.
A tool is one action, with defined inputs and outputs. Every tool has an impact class that Orqane compares with the employee’s autonomy level before each call.
| Impact class | What the tool does | Examples |
|---|---|---|
| Read | Looks up information. Changes nothing. | Search the web, read a file, get a CRM record |
| Draft | Writes content that stays inside Orqane. | Draft an email, write a report |
| Write internal | Creates or updates records in your own systems. | Create a HubSpot deal, update a Jira issue |
| Communicate | Sends a message to someone outside the employee’s team. | Send an email, post in a customer Slack channel |
| Spend | Makes a payment from the employee’s wallet. | Pay for an API call with x402 |
| Delegate | Gives work to another employee or agent. | Create a task for a teammate, hire a marketplace agent |
| Irreversible | Can’t be undone. | Delete a record, sign a contract, publish publicly |
Orqane sets the impact class of built-in and connector tools. For MCP and custom tools, the Builder who adds the tool sets it, and an Admin can override it. A tool with no class is treated as Irreversible.
Where tools come from
Section titled “Where tools come from”| Source | What it provides | How to add it |
|---|---|---|
| Built-in | Web search, web browsing, file reading, code execution, calculator, Orqane chat. | Available to every employee. Turn them off per employee on the Tools tab. |
| Connectors | Actions in your business apps: Google Workspace, Microsoft 365, Slack, HubSpot, Salesforce, Zendesk, GitHub and more. | Authorize the connector once in Connectors, then grant tools to each employee. See Connectors. |
| MCP servers | Any tool exposed by an MCP server, public or your own. | Add the server in Connectors > MCP servers, then grant tools. See MCP. |
| Marketplace | Ready-made skills and MCP tools published by others. | Click Install on a listing. Installed tools go through the same grant step. |
Granting is per employee and per tool. You can grant Gmail: Read email without granting Gmail: Send email. You can also restrict a tool’s inputs, for example limiting Gmail: Send email to recipients at your own domain. Policies apply on top of every grant.