Skip to main content
A skill is something you ask for. A play is something that just happens. Plays are your standing rules. “Every new ClickUp task gets normal priority unless I say otherwise.” “Every Slack message I send to a client stays under three sentences.” Once a play is on, Arora applies it every time a matching request comes through. You don’t have to remember to ask.

​
Why plays live on Arora

Plays live on the server, not in your AI app. No rules files. No custom instructions to paste into every tool. Write the rule once and it applies in Claude, ChatGPT, and anywhere else you use Arora.

​
Four kinds of rules

​
Make one

Describe the rule. Your AI sets it up.

​
Scope it

A play can apply to one app or all of them, to one kind of action (create, update, read) or all of them, and to one kind of record (tasks, contacts, deals, messages, events) or all of them. You can also give a play keywords. Then it only fires when your request mentions one of them. Leave keywords off and it’s always on.

​
Browse the library

Arora has a library of ready-made plays for common workflows. Ask your AI to search it:

​
Personal and team plays

  • Personal plays are yours. You can create, edit, turn off, and delete them.
  • Team plays come from your organization. You’ll see them in your list and they apply to your work, but you can’t change them.
Deleting a play turns it off. It stops applying right away.
Library: bridge_list_plays, bridge_get_play, bridge_search_plays. Personal: bridge_list_my_plays, bridge_create_play, bridge_update_play, bridge_delete_play (soft delete). Rule types: prompt_instruction, set_default, set_field, structured_template. Connector scope: clickup, hubspot, slack, gmail, gcalendar, or * for all.
Last modified on October 13, 2026