Skills
A skill is a procedure an employee follows: when to use it, its steps, what you give it and what you get back. Write one for work an employee does again and again, so it is done the same way each time.
- You are the company’s owner: only the owner creates skills.
- At least one active employee to give the skill to, or save it as a draft for later.
On this page
When to write one#
An employee works without skills: their instructions say how they work and their responsibilities what they own. Add a skill when you find yourself explaining the same process twice, such as qualifying a lead or matching supplier invoices to orders. Tone, judgement and limits stay in instructions.
| A skill holds | For example |
|---|---|
| Use it when | A new inbound lead arrives. |
| Give it → Get back | The lead’s email → a short qualification note with a score. |
| Steps | Up to 30, each with an optional note and reviewer. |
| Guidance | How to judge borderline cases. |
| Done when | Checks the work must pass before the task can close. |
| Uses and Apps it expects | Documents, examples of great work, and the apps it needs. |
The skills library#
On People, open Skills. Each row shows the skill’s department, who has it, what it uses, how many runs used it this month, how many of those passed its checks, and its latest version. Drafts holds skills not given to anyone yet, and Needs attention the skills whose checks passed less than 80% of the time this month. A skill’s page adds This month: its runs, the share that passed and their average cost.
Create a skill#
- 1
Open New skill
On People’s Skills view, choose New skill, then how to start: Describe it in a few sentences, Start from a template among Royak’s six common skills (proposal drafts, call summaries, process checklists and more), or From a finished task your company did well. Nothing is given to anyone yet.
- 2
Draft the skill
Draft the skill. A template is filled in at once. A description or a finished task is drafted by Chat in one call charged to your company’s usage: from a task, it reads how the work was done, the documents it cited, your feedback and the result, and a step it learned from your feedback says so.
- 3
Review and save
Edit anything in place: when to use it, what to give it, what you get back, each step, the guidance and the checks under Done when. Add documents and examples, and the apps it expects. Choose who gets it under Give it to, then Save and give to {name}, or Save as draft to give it later.
You can also ask Chat (“Write a skill for qualifying inbound leads”, or “Give Daniel a skill for …”): it proposes one as a card to confirm. Setting an employee up with Chat also proposes a skill when their job includes a repeated process.
To give an existing skill to someone else, open it and choose Give to employee, or add it under Skills when you edit their profile.
Suggested skills#
When you ask for the same work three or more times in 30 days and none of the employees who did it has a skill for it, it tops the Skills list, marked Suggested by Chat, with how often you asked: “You asked for this 4 times in October.” Requests count as the same when their titles match once dates and numbers are left out, so “Weekly sales report 3 Oct” and “Weekly sales report 10 Oct” count together.
- Review drafts the skill from the latest of those tasks and opens it at the review step. Saving it closes the suggestion.
- Dismiss hides it, and that work is never suggested again.
Edit a skill#
Open a skill and choose Edit, or ask Chat (“Make the lead-qualification skill also check the region”). Change a step in place, add one, remove one or drag it into order; each change is marked Changed or New, and the page says who it reaches. Save as v2 (or the next number) makes the skill’s next version.
- Everyone using the skill moves to the new version from their next task. Someone with a draft waiting gets it in the draft, and moves when you activate it.
- Work already under way keeps the version it started with.
- Versions lists each one with what changed, who saved it and when. Restore saves an earlier one as the next version.
- Skills marked Royak are the same for every company and can’t be edited. Write your own with New skill instead.
Checks: done when#
A skill can say when its work is done. In Edit, Add a check under Done when (at most 10):
| Check | How it’s decided |
|---|---|
| Required sections | By Royak, without a call. |
| Word limit | By Royak, without a call. |
| Words it never uses / Words it always uses | By Royak, without a call. |
| Judged by a call | One AI call on your usage. |
| Reviewer’s review | The reviewer a step names reads the work: one call on their model. |
A task that uses the skill can’t close while a check fails: the work goes back to the employee with the reasons, at most twice. After that it waits for you as Needs decision: accept it as it is, ask for a revision, or cancel it. The task’s record shows each check as Passed, Failed or Waiting.
- Add a document or an example links knowledge and finished work. Employees read them only where their own access reaches; the page says who can’t.
- Apps it expects lists the apps and access the skill needs, and who lacks it. It never gives access: set that in Connections.
Questions#
Skill or instructions: which should I change?
Instructions for how someone works in general (tone, judgement, what never to do). A skill for one repeated procedure with steps and a clear result.
Does giving a skill change work already running?
No. Running tasks keep the version they started with.
Can one skill be used by several employees?
Yes. Give it to as many as you like; each uses it from their next task.
What does a skill cost?
Nothing by itself. Drafting with Chat is one call, and judged checks and reviews are one call each when a task uses them.