skill-cloudbees-oss-devops-agent-kit-pipeline-overview · by Install
$ agentstack add skill-cloudbees-oss-devops-agent-kit-pipeline-overview ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cloudbees-oss-devops-agent-kit-pipeline-overview) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Pipeline Overview: $ARGUMENTS
Show the user a unified view of their CI/CD pipelines across all tools.
- If the user specified a component name, search for it using
components_search. Otherwise, list all components with components_list.
- For each component, gather:
a. workflow_list — all configured workflows (CloudBees + GitHub Actions) b. runs_list(limit=3) — the 3 most recent runs per workflow c. Skip any workflows with names containing "code_scan" — these are infrastructure-managed scans, not user pipelines
- Get controller data:
a. controllers_list — find Jenkins controllers b. For each controller: controllers_data_get(ci4) — runs overview (active runs, queued, wait times)
- Get security context:
a. security_issues_all_get — open vulnerability count per component
- Get feature flag context:
a. flags_applications_list — find flag applications b. For each application: flags_list — count of active flags
- Present a unified dashboard:
Organization Pipeline Status
| Component | GitHub Actions | CloudBees Workflow | Jenkins | Security | Flags | |-----------|---------------|-------------------|---------|----------|-------| | name | #N PASS/FAIL | #N PASS/FAIL | status | N HIGH | N active |
For each component, show:
- Latest run status per CI tool (pass/fail/running)
- Open security findings count and max severity
- Active feature flags
- Any blockers or issues
- Provide a summary:
- Components green vs. red
- Cross-tool patterns (e.g., "GitHub Actions healthy but CloudBees
Workflows failing on all 3 components — likely a common config issue")
- Top recommendations
- Offer next actions:
- "/triage [component]" for any failed component
- "/security-scan all" if security findings exist
- "/release-status" if all components are green
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cloudbees-oss
- Source: cloudbees-oss/devops-agent-kit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.