Skip to main content
A skill is a playbook. Step-by-step instructions for a job you want done the same way every time: how to write a weekly client recap, how to triage a support inbox, how to prep for a sales call. Your AI doesn’t carry every skill around. It sees a short list of what’s available and loads the full playbook only when the job calls for it.

​
Use the skills Arora ships

Arora comes with skills that teach your AI how to get the most out of Arora itself, like working with very large documents. They load on their own when they’re useful.

​
Write your own

When you’ve explained the same process to your AI more than twice, make it a skill.
Next time, just ask for it by name:
Your skills live on your Arora account, not in one AI app. Write a skill in Claude and it works in ChatGPT, too. No skill files to copy around.

​
Keep them current

You don’t have to rewrite a whole skill to change it. Your AI can add a new step at the end, or replace one section and leave the rest alone.

​
Which skill wins

If you and Arora both have a skill with the same name, yours wins. That means you can override any built-in skill with your own version.

​
Team skills

Sharing a skill with your whole organization is in beta. Once it opens up, org owners and admins will be able to promote a personal skill to the team library so everyone runs the same playbook.

​
Limits

Large skills open on your workspace, so your AI reads only the section it needs.
Tools: bridge_load_skill (list, get), bridge_create_skill, bridge_update_skill (append, replace_section), bridge_delete_skill. Precedence on a name clash: yours, then your organization’s, then Arora’s default.
Last modified on October 13, 2026