| name | devopsctl |
| description | Use an installed devopsctl CLI to operate an enterprise DevOps platform. Trigger when the user asks an agent to inspect or manage business spaces, apps, services, deployments, Jenkins publish/build history, login/auth status, or supported DevOps backend API calls. |
DevOps CLI
Use this skill whenever a task can be handled through the configured DevOps backend instead of manually browsing the UI or reconstructing API calls.
CLI
Resolve an installed executable. This sanitized skill does not bundle an organization-specific binary.
DEVOPSCTL="${DEVOPSCTL:-$(command -v devopsctl)}"
test -n "$DEVOPSCTL" || { echo "devopsctl is not installed" >&2; exit 1; }
"$DEVOPSCTL" --help
Configure the backend through the CLI config, DEVOPS_BASE_URL, or --base-url. Never infer an internal endpoint.
Workflow
- Resolve
devopsctl from PATH or DEVOPSCTL.
- Check auth with
"$DEVOPSCTL" auth status --pretty.
- If not logged in, run
"$DEVOPSCTL" login --username <email> and let the user enter the password when prompted. Prefer this over asking for cookies.
- Use text output for human-readable summaries. Use
--json --pretty when the next step needs structured data.
- For apps, list business spaces first and always pass
--business-space-id to app list.
- Use
"$DEVOPSCTL" health --pretty for backend health checks and "$DEVOPSCTL" routes --json --pretty to discover supported backend routes.
- For unsupported endpoints, use
"$DEVOPSCTL" call METHOD PATH.
Command Reference
Read references/cli-usage.md when you need exact flags, backend endpoints, JSON/query field names, or examples.
Safety
Treat create, update, delete, write, Jenkins build, rebuild, cancel, deploy, restart, rollout, and any non-GET raw API call as mutating operations.
Before running any mutating operation, get a second confirmation from the user in the current conversation, even when the user already requested the operation. Present the exact command or API method/path, target resource identifiers, and expected effect, then wait for an explicit affirmative reply. Do not treat prior intent, tool approval, or successful authentication as confirmation.
