Skip to main content
A skill is a short runbook Rubix loads when a task needs it. In this tutorial, you turn one of your own runbooks into a skill and try it in chat. RubixKube uses the open Agent Skills format, so you can start from a SKILL.md file written for another tool.

Before you start

  • You need to be an admin in your organization.
  • Have a runbook you already use, in any format.

What a skill looks like

A skill is a name, a description and instructions:

Step 1: Pick a real runbook

Skills work best when they cover something your team already does in a specific way. Good candidates:
  • Post-deploy verification. Compare current metrics with the last stable version.
  • Team handoff. Summarize open incidents, Tasks and recent changes for the next person.
  • Pre-change check. Run a standard readiness check before a risky deploy.

Step 2: Write the skill

Open Customize > Skills and click New skill. Fill in the form, or click Fill from a SKILL.md file to start from a file. Write Instructions like a handover note. Use short sentences and specific numbers (“20% worse than the baseline”, not “much worse”). Write When to use it with care. Rubix reads it to decide when to load the skill, so name the service or the situation. Click Create skill. The skill is on as soon as you create it.

Step 3: Try it in chat

Skills have no test button, so try yours in a real session.
1

Pin the skill

Start a New session, type @, open Skills and pick yours.
2

Ask Rubix to run it

For example: “Run this for orders-api.”
3

Fix the instructions

Open the skill in Customize > Skills, click Edit, and change what didn’t work. Then try again in a new session.
Then check that Rubix finds the skill by itself. Start a new session, don’t pin anything, and ask the question your team would ask. If Rubix doesn’t load the skill, make When to use it more specific.
A skill doesn’t give Rubix more permissions, and it doesn’t take any away. Modes and hooks decide what can run. In Auto, a skill that tells Rubix to make a change makes it without asking, unless the change is destructive.

Step 4: Keep it current

Update the skill when the runbook changes. To stop using it for a while, turn it off with its switch. Deleting a skill can’t be undone.

Example to copy

Common questions

Built-in skills come with RubixKube. Yours belong to your organization, and only your organization sees them. Both work the same way. If you give yours the same name as a built-in, yours replaces it. See Skills.
Rubix loads a skill by itself when a task fits. A command is a prompt a person puts in the chat box with /.

Skills

Built-in skills and how to manage yours.

Chat prompts

Good skills start with good prompts.