CloudBees Unify agent skills for Claude Code, Cursor and RevampKey

5 ready-made playbooks that teach an AI agent how to do real CloudBees Unify work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect CloudBees Unify

Connect CloudBees Unify once and all 5 skills install themselves and stay up to date. Mac, Windows and Linux.

All 5 CloudBees Unify skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereAsks before writing21 CloudBees Unify tools

Use the CloudBees Unify MCP Server safely

Connects your AI assistant to CloudBees Unify and confirms organization, component and environment before reading delivery data. Any change, such as approving a gate or altering a flag, waits for your explicit yes.

Use it when

You have just connected CloudBees Unify and want to know what the assistant can safely do
You are about to ask about runs, gates or flags and need the right environment selected first
A query came back empty or refused and you want to know whether scope or permissions caused it

Tools it uses

controllers_list
branches_list
endpoint_list
actions_list
automation_jobs_list
automation_pending_tasks_list
automation_trigger_by_branch
automation_rerun
automation_stop
automation_approve_manual_gate
automation_reject_manual_gate
controllers_data_get
flag_configuration_get
flag_approval_requests_list
flag_target_groups_add
flag_serve_to_target_group
flag_configuration_conditions_set
endpoint_add
extensions_list
flag_custom_properties_add
flag_custom_properties_delete

Example

Connect to CloudBees Unify and check how many runs are waiting for approval in the staging environment of the payments component.

I'll confirm the organization and the payments component first. In staging there are 3 manual gates waiting: 2 for the release-candidate workflow and 1 for the database migration job. I have not approved or rejected any of them. Tell me which to act on and I'll draft the decision for your yes.

Use in RevampKeyRead the full skill →

Asks before writing8 CloudBees Unify tools

CI controller and automation health check

Audits your CloudBees CI controllers and automation read-only, finding branches and jobs that do not trigger, stuck or stopped automation, and a prioritised list of gaps with owners to contact. It asks before rerunning or triggering anything.

Use it when

A release branch has not built in weeks and you need to know why
You want a coverage report of which branches and jobs CI actually runs
Stuck or stopped automation needs to be routed to the right owners

Tools it uses

controllers_list
controllers_data_get
automation_jobs_list
branches_list
actions_list
automation_pending_tasks_list
automation_rerun
automation_trigger_by_branch

Example

Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.

I checked 6 controllers in the payments component over the last 30 days. The release/2.4 branch has an automation but no triggered run in 34 days, so it is a P1 gap, owned by the platform team. Two feature branches have no automation at all, which is a P3 coverage gap. One manual gate has been waiting 9 days and is blocking the 2.4 promotion. I haven't rerun or approved anything; say the word if you want the release/2.4 build triggered.

Use in RevampKeyRead the full skill →

Asks before writing7 CloudBees Unify tools

Audit a feature flag before rollout with CloudBees Unify MCP Server

Reads a feature flag's configuration, targeting and approval state in each environment, flags risky or stale targeting, and recommends staged serving or cleanup. It asks before changing anything.

Use it when

Before widening a flag from an internal cohort to all users
When a flag has been on for months and may be ready for cleanup
When two environments seem to serve a flag differently

Tools it uses

flag_configuration_get
flag_custom_properties_target_group_usage
flag_custom_properties_flag_usage_per_environment
flag_custom_properties_list
flag_approval_requests_list
flag_serve_to_target_group
flag_configuration_conditions_set

Example

Audit the checkout-redesign flag in production and staging before we roll it out to all enterprise customers on Monday.

Checkout-redesign is on for 2 target groups in production and still at the test variation in staging, so staging does not represent production. The default serves the old checkout to 1 rule-less group. One pending approval request would widen the enterprise group next week. Recommend moving the enterprise rollout behind a staged cohort first. I have changed nothing.

Use in RevampKeyRead the full skill →

Read-only5 CloudBees Unify tools

Review pending approvals with AI

Lists manual approval gates waiting in CloudBees Unify, checks what each one promotes and the evidence behind it, and recommends approve, hold or reject. It only approves or rejects a gate when you explicitly confirm it.

Use it when

A release is waiting at a production approval gate and you want to know if it is safe
You want to clear the pending-tasks queue without approving anything blindly
You need to see what each waiting gate is promoting and from where

Tools it uses

automation_pending_tasks_list
automation_jobs_list
actions_list
automation_approve_manual_gate
automation_reject_manual_gate

Example

What's waiting for approval in CloudBees Unify right now, and which of those should I worry about?

One task is pending: the production gate for payments-api v2.14.0, which has waited 26 hours. Its upstream tests passed, but a high-severity scan finding is still open, so I recommend holding it. Nothing has been approved or rejected yet; tell me if you want me to act on it.

Use in RevampKeyRead the full skill →

Asks before writing10 CloudBees Unify tools

Triage failing CloudBees Unify pipelines with AI

Finds the first real failure in a workflow run, classifies it as code, credential, environment or infrastructure, and proposes a next action. It asks before rerunning, stopping or triggering anything.

Use it when

A build or deploy workflow went red and you need to know why
A run has been stuck for a long time and you want to know if it is hung or waiting
The same pipeline keeps failing and you want to know whether to rerun or fix it

Tools it uses

automation_jobs_list
automation_rerun
automation_pending_tasks_list
automation_stop
automation_trigger_by_branch
controllers_list
controllers_data_get
branches_list
endpoint_list
actions_list

Example

Why did the release workflow on the main branch fail last night, and is it safe to rerun?

The first failure was in the integration tests step of run #412, with a connection timeout to the artifact registry. The next two failures were downstream, because the deploy step depends on the test artifact. This looks like infrastructure rather than code: the same registry timeout appeared in two earlier runs this week. A rerun is reasonable, but I have not triggered it. Say the word if you want me to rerun run #412.

Use in RevampKeyRead the full skill →

Get all 5 without copying a file

RevampKey adds the skills when you connect CloudBees Unify, updates them for you and removes them when you disconnect.

Download RevampKey

How CloudBees Unify skills work

Connect CloudBees Unify
The CloudBees Unify MCP server gives the agent its tools.
Ask in plain words
“Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install CloudBees Unify skills

In RevampKey the skills install themselves when you connect CloudBees Unify. In other tools each skill is one folder with a SKILL.md file, and you also need the CloudBees Unify MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect CloudBees Unify. All 5 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.”
Download RevampKeyConnect CloudBees Unify · 1 click
Get RevampKey to connect CloudBees Unify
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and CloudBees Unify is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials ci-controller-health-check feature-flag-rollout-audit pending-approval-review pipeline-failure-triage; do curl -fsSL --create-dirs -o .claude/skills/cloudbees-unify-mcp-server-$s/SKILL.md https://revampkey.com/marketplace/cloudbees-unify-mcp-server/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the CloudBees Unify MCP server in Claude Code.

Run this in your project folder to add all 5 skills:

for s in essentials ci-controller-health-check feature-flag-rollout-audit pending-approval-review pipeline-failure-triage; do
  curl -fsSL --create-dirs -o .claude/skills/cloudbees-unify-mcp-server-$s/SKILL.md https://revampkey.com/marketplace/cloudbees-unify-mcp-server/skills/$s/SKILL.md
done

Ask in plain language, for example “Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.”

Into the shared .agents/skills folder

Connect the CloudBees Unify MCP server in Cursor.

Run this in your project folder to add all 5 skills:

for s in essentials ci-controller-health-check feature-flag-rollout-audit pending-approval-review pipeline-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/cloudbees-unify-mcp-server-$s/SKILL.md https://revampkey.com/marketplace/cloudbees-unify-mcp-server/skills/$s/SKILL.md
done

Ask in plain language, for example “Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.”

Into the shared .agents/skills folder

Connect the CloudBees Unify MCP server in Codex.

Run this in your project folder to add all 5 skills:

for s in essentials ci-controller-health-check feature-flag-rollout-audit pending-approval-review pipeline-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/cloudbees-unify-mcp-server-$s/SKILL.md https://revampkey.com/marketplace/cloudbees-unify-mcp-server/skills/$s/SKILL.md
done

Ask in plain language, for example “Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.”

Into the shared .agents/skills folder

Connect the CloudBees Unify MCP server in VS Code.

Run this in your project folder to add all 5 skills:

for s in essentials ci-controller-health-check feature-flag-rollout-audit pending-approval-review pipeline-failure-triage; do
  curl -fsSL --create-dirs -o .agents/skills/cloudbees-unify-mcp-server-$s/SKILL.md https://revampkey.com/marketplace/cloudbees-unify-mcp-server/skills/$s/SKILL.md
done

Ask in plain language, for example “Check our CI controllers for the payments component and tell me which branches aren't building and what's stuck.”

RevampKey or copy the files?

In RevampKey

One click when you connect CloudBees Unify
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the CloudBees Unify MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

CloudBees Unify skills FAQ

What is a CloudBees Unify agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each CloudBees Unify skill describes one job, which CloudBees Unify tools to use in which order, what to check first and when to stop and ask you.

Do the CloudBees Unify skills change anything on their own?

1 of the 5 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in CloudBees Unify.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect CloudBees Unify; elsewhere you copy the folders into your project or skills directory.

Do I need the CloudBees Unify MCP server too?

Yes. The skills tell the agent how to do the work; the CloudBees Unify MCP server gives it the tools to do it. The CloudBees Unify MCP setup guide covers every client.

CloudBees Unify MCP server setup · This page as Markdown

Put CloudBees Unify’s best workflows in your agent

Download RevampKey, connect CloudBees Unify and ask your first question in about a minute.

Download RevampKey Connect CloudBees Unify · 1 click

All 5 CloudBees Unify skills

Use the CloudBees Unify MCP Server safely

Use it when

Tools it uses

CI controller and automation health check

Use it when

Tools it uses

Audit a feature flag before rollout with CloudBees Unify MCP Server

Use it when

Tools it uses

Review pending approvals with AI

Use it when

Tools it uses

Triage failing CloudBees Unify pipelines with AI

Use it when

Tools it uses

Get all 5 without copying a file

How CloudBees Unify skills work

How to install CloudBees Unify skills

RevampKey or copy the files?

In RevampKey

Copy into your project

CloudBees Unify skills FAQ

Put CloudBees Unify’s best workflows in your agent

Skills for related tools