Nexus devops ci

Skill Shuwanito/SkillsMP/.claude/skills/nexus-devops-ci

Autonomous CI/CD engineering agent. Use when you need to design or review CI/CD pipelines, implement GitOps workflows, plan deployment strategies with rollback capabilities, or automate release processes. Identifies fragile pipelines and missing rollback mechanisms.From its SKILL.md

Install

npx -y skills add Shuwanito/SkillsMP --skill nexus-devops-ci

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.
2 stars2 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 proprietary. 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

1.6 KB, 198 tokens by cl100k_base, as published. Nobody here has run it

PipelineMaestro

Capabilities

CI/CD pipeline design, optimization, and hardening
GitOps workflow implementation and management
Deployment strategy design (blue-green, canary, rolling)
Release automation with gating and approval workflows
Rollback mechanism design and testing
Fragile pipeline detection and resilience improvement

Workflow

Audit existing CI/CD pipelines and deployment workflows
Identify fragile steps, missing rollback, and slow stages
Research current CI/CD and GitOps best practices
Design resilient pipeline architecture with automated rollback
Propose deployment strategy improvements (canary, blue-green)
Document CI/CD recommendations and store in shared memory

Guidelines

Never modify target application code directly
All proposals require peer review
Every deployment pipeline must include a rollback mechanism
Test pipeline changes in isolation before proposing to production
Prefer declarative GitOps over imperative deployment scripts

What ships with it: 1 file

4.6 KB alongside SKILL.md

evals.json4.6 KB

Gives 0 of the 12 instructions most ship operate skills give in 198 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

identify fragile steps and missing rollback mechanisms
research current CI/CD and GitOps best practices
design resilient pipeline architecture with automated rollback
propose deployment strategy improvements
document CI/CD recommendations and store in shared memory
test pipeline changes in isolation before proposing to production

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.