用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Arvo-AI/aurora --skill cloudbees命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | cloudbees |
| id | cloudbees |
| description | CloudBees CI integration for investigating builds, deployments, pipeline stages, and test results during RCA |
| category | cicd |
| connection_check | {"method":"is_connected_function","module":"chat.backend.agent.tools.cloudbees_rca_tool","function":"is_cloudbees_connected"} |
| tools | ["cloudbees_rca"] |
| index | CI/CD -- investigate CloudBees CI builds, deployments, pipeline stages, logs, test results |
| rca_priority | 4 |
| allowed-tools | cloudbees_rca |
| metadata | {"author":"aurora","version":"2.0"} |
CloudBees CI integration for investigating builds and deployments during Root Cause Analysis. CloudBees CI uses the same APIs as Jenkins: Core REST API, Pipeline REST API (wfapi), and Blue Ocean REST API.
Unified CloudBees CI investigation tool for Root Cause Analysis.
Actions:
recent_deployments -- Query stored deployment events; optional service filter and time_window_hoursbuild_detail -- Core API: SCM revision, changeSets, build causes, parameters. Requires job_path + build_numberpipeline_stages -- wfapi: stage-level breakdown with status and timing. Requires job_path + build_numberstage_log -- wfapi: per-stage log output for a specific node_id. Requires job_path + build_number + node_idbuild_logs -- Core API: console output, truncated to ~1MB. Requires job_path + build_numbertest_results -- Core API: test report with failure details. Requires job_path + build_numberblue_ocean_run -- Blue Ocean API: run data with changeSet and commit info. Requires pipeline_name + run_numberblue_ocean_steps -- Blue Ocean API: step-level detail for a pipeline node. Requires pipeline_name + run_numberRequired params vary by action: job_path + build_number for Core/wfapi, pipeline_name + run_number for Blue Ocean. service is optional for recent_deployments.
Recent deployments are a leading indicator of root cause. Always check if a deployment occurred shortly before the alert fired.
cloudbees_rca(action='recent_deployments', service='SERVICE') -- Check for recent deployscloudbees_rca(action='build_detail', job_path='JOB', build_number=N) -- Build details + commitscloudbees_rca(action='pipeline_stages', job_path='JOB', build_number=N) -- Stage breakdowncloudbees_rca(action='build_logs', job_path='JOB', build_number=N) -- Console outputcloudbees_rca(action='test_results', job_path='JOB', build_number=N) -- Test failuresrecent_deployments to find deployments near the incident time.build_detail to get SCM changes and build causes before reading logs.pipeline_stages for stage-level breakdown to narrow which stage failed.flag_changes unless Feature Management is known to be connected.cross_controller_deployments or controller_list unless Operations Center OR a manually-registered controller fleet (Multiple Controllers mode) is connected.{cloudbees_deploys_section}
cloudbees_rca(action='recent_deployments', service='{service_name}') -- Recent deployscloudbees_rca(action='build_detail', job_path='JOB', build_number=N) -- Build details + commitscloudbees_rca(action='pipeline_stages', job_path='JOB', build_number=N) -- Stage breakdowncloudbees_rca(action='stage_log', job_path='JOB', build_number=N, node_id='NODE') -- Stage logscloudbees_rca(action='build_logs', job_path='JOB', build_number=N) -- Console outputcloudbees_rca(action='test_results', job_path='JOB', build_number=N) -- Test failurescloudbees_rca(action='blue_ocean_run', pipeline_name='PIPELINE', run_number=N) -- Blue Ocean dataRecent deployments are a leading indicator of root cause.
These actions work in two cases: when Operations Center is connected (provider: cloudbees_oc), OR when the user has manually registered multiple standalone controllers via "Multiple Controllers" mode (provider: cloudbees_fleet — for clients that run several controllers but have no OC):
controller_list — List all controllers and their status (online/offline)cross_controller_deployments — Query recent builds across ALL controllersIn fleet mode, controllers were registered individually (each with its own URL + token), since standalone CloudBees CI controllers cannot be discovered automatically without Operations Center.
For per-build introspection (build_detail, pipeline_stages, build_logs, etc.) in either OC or
fleet mode, pass controller_url — get the URL from controller_list or
cross_controller_deployments (the _controller_url field) first.
These return a helpful error if neither OC nor a fleet is connected.
This action is ONLY available when Feature Management is connected (provider: cloudbees_fm):
flag_changes — Query recent feature flag changes (requires app_id parameter)Only use this if you have confirmed Feature Management is connected AND you have an app_id.