Skip to main content
Copy any of these into a chat with Rubix and swap in your own names. Open a chat with New session in the sidebar, or click Ask Rubix on any page.

​
Ask better questions

Name the thing you mean, where it runs and the time you care about. Rubix then has less to guess. Keep going in the same session. Rubix remembers the conversation, so “and what about orders-api?” works as a follow-up.

​
Understand a problem

Start of the day:
When something looks wrong:
Looking for a pattern:
Checking resources:
Learning something new:

​
Check what changed

Most problems start with a change, so this is a good first question.

​
Plan a change

Rubix can think through a change with you in any mode. Whether it can make the change depends on your mode.
Attach the YAML file to that last one before you send it.
After an incident:

​
Cost questions

Rubix answers from what your sources and connected tools can read, such as requests, limits and usage. If none of them carry billing data, treat any dollar amount in the answer as an estimate. Find waste:
Compare:
Right-size:
Plan ahead:

​
Use @ and /

Type @ in a message to add context. You’ll get a list of incidents, RCAs, Tasks, environments, past sessions, skills and time windows. Pick one and Rubix looks at that exact thing. When the chat is open beside a page, you can add that page too. Pick an incident, then ask:
Pick an RCA, then ask:
Pick an environment and the time window “Since the last deploy”, then ask:
Type / in an empty message box to open commands: You can type the value straight after the command, such as /mode assist. /mode appears once a session has started. Commands your organization saved in Customize > Commands appear in the same menu and put a saved prompt in the message box.

Talk to your infra

How chatting with Rubix works.

Your first incident

Follow one incident from start to finish.

Rubix chat

Everything in the chat, explained.

Add custom skills

Turn your best prompts into skills.