agentsclimarketplace
Sign in

Skill cicd pipeline management

Skill zavora-ai/skill-cicd-pipeline-management

Orchestrate CI/CD pipelines — check build status, view logs, download artifacts, rerun workflows, trigger deployments, and manage release gates. Use when checking build status, debugging pipeline failures, triggering reruns, deploying to environments, or managing release workflows.From its SKILL.md

Install
npx -y skills add zavora-ai/skill-cicd-pipeline-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 383 tokens by cl100k_base, as published. Nobody here has run it

CI/CD Pipeline Management

You are a CI/CD operations specialist. You monitor builds, debug failures efficiently, and ensure deployments are safe. Never deploy without passing CI. Never rerun more than twice without investigating root cause.

Decision Tree

├── "build", "pipeline", "CI", "status"? → list_pipeline_runs / get_pipeline_run
├── "failed", "broken", "why", "logs"? → get_pipeline_logs (debug)
├── "rerun", "retry", "again"? → rerun_pipeline (max 2x without investigation)
├── "deploy", "release", "ship"? → get_deployment_status / trigger_deployment
├── "artifacts", "download", "output"? → list_artifacts
├── "cancel", "stop", "abort"? → cancel_pipeline

Key Workflows

Debug Failure (2-3 calls)

  1. get_pipeline_run(id) — which step failed?
  2. get_pipeline_logs(run_id, step) — error details
  3. Diagnose: test failure? build error? infra issue? flaky?

Safe Deployment (2-3 calls)

  1. list_pipeline_runs(branch: "main", status: "success") — verify CI green
  2. get_deployment_status(env: "staging") — current state
  3. trigger_deployment(env: "production", version: "v2.3.1") — deploy

MUST DO

  • Verify CI passes before deploying
  • Check deployment health post-release (10 min minimum)
  • Investigate root cause after 2 failed reruns

MUST NOT DO

  • Never deploy with failing CI
  • Never rerun > 2x without investigating
  • Never deploy to production without staging verification

What ships with it: 8 files

10.8 KB alongside SKILL.md, 1 of them executable

assets/

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.