Skill cicd pipeline management

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

CI/CD pipeline skill — build status, logs, reruns, deployments via mcp-cicd

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 author says it does

Copied from the file, not written here

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.

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, 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)

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

Safe Deployment (2-3 calls)

list_pipeline_runs(branch: "main", status: "success") — verify CI green
get_deployment_status(env: "staging") — current state
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

Gives 0 of the 12 instructions most ci cd skills give

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

pin third-party actions to full commit SHAsin 33 of 392
cache dependencies appropriatelyin 24 of 392, across 12 files
optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
enforce all quality gates before mergein 20 of 392, across 7 files
Configure branch protection rulesin 19 of 392, across 5 files
use environments for deployment trackingin 19 of 392, across 7 files
implement manual gates for productionin 19 of 392, across 7 files
implement security scanningin 18 of 392, across 5 files
fix failing code instead of disabling checksin 18 of 392, across 4 files
use CI/CD variables for secretsin 18 of 392, across 6 files
move checks upstream in the pipelinein 17 of 392, across 3 files
use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

investigate root cause after 2 failed reruns
list pipeline runs for build status
get pipeline logs to debug failures
list artifacts to download outputs
cancel pipelines to stop builds
diagnose failures as test build or infra

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.