skill-cloudbees-oss-devops-agent-kit-release-status · by Install
$ agentstack add skill-cloudbees-oss-devops-agent-kit-release-status ✓ 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-release-status) 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
Release Status: $ARGUMENTS
components_list— get all components in the organization- For each component:
a. workflow_list — identify CI and release workflows b. runs_list(limit=5) — get latest run status per workflow Skip code_scan workflows. c. security_issues_open_get or security_findings_summary_get — check for open vulnerabilities on the default branch d. branches_list — verify the default branch
- Check release orchestration:
a. Look for components with release/deploy workflows (workflowdispatch triggers, staged deployments) b. automation_jobs_list — check for staged deployment jobs (staging -> approval -> production pattern) c. Check for PENDINGAPPROVAL jobs — these are deployment gates waiting on human sign-off
- Check feature flags:
a. flags_applications_list — find flag applications b. flags_environments_list — list environments (staging, production) c. flags_configurations_list — check flag states per environment
- Present a release readiness report:
Release Readiness Report Date: [timestamp] Verdict: READY / NOT READY / BLOCKED
| Component | CI Status | Security | Flags | Blocker | |-----------|-----------|----------|-------|---------| | name | GREEN/RED | N HIGH | state | desc |
Blockers by Priority:
- [Highest priority blocker with specific details]
- [Next blocker]
...
What Must Be Done Before Release:
- [ ] Specific action item 1
- [ ] Specific action item 2
- Offer next actions:
- "/triage [component]" for any red component
- "/security-scan [component]" for components with findings
- "/flag-rollout [flag] enable" to activate flags for release
- Post release readiness to Slack
- Trigger release workflow via
workflow_trigger(with explicit
user confirmation — show which workflow will be triggered and what it will do before executing)
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.