CI Health Report
Use when checking CI/CD health, Jenkins build failures, flaky tests, build success rates, or generating a CI health report. Trigger phrases: CI health, build failures, jenkins report, flaky tests, build health, are builds passing, CI status.
Install
/plugin marketplace add npow/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add npow/claude-skills --skill ci-health-reportgit clone --depth 1 https://github.com/npow/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/ci-health-report ~/.claude/skills/ci-health-reportPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# CI/CD Health Report
Produce an actionable weekly health report for Jenkins CI builds using Boost MCP tools. The report root-causes failures and groups them — a list of build numbers is not a report.
## Configuration
See [`_shared/report-config.md`](../_shared/report-config.md) for the standard config resolution pattern.
**Config schema** (`~/.claude/skills/ci-health-report/config.json`):
- `repos`: list of `{hostType, projectKey, repoSlug}` objects
- `controllers`: list of Jenkins controller names
- `job_name_contains`: substring match on job name
- `lookback_days`: number (default: 7)
**Required scope:** at least one of `repos`, `controllers`, or `job_name_contains`.
## Arguments
- **repos**: list of {hostType, projectKey, repoSlug} to check
- **controllers**: Jenkins controller names to scope search
- **job_name_contains**: substring match on job name
- **lookback_days**: how far back to check builds (default: match your cadence — 1 for daily, 7 for weekly)
## Workflow
1. **Discover jobs.** Use `search_jobs` with configured scope. Filter to ACTIVE state.
2. **Get recent builds.** For each job, call `search_builds`. Compute per-job: total builds, failures, success rate.Details
- Skill name
ci-health-report- Repository
- npow/claude-skills
- Path
ci-health-report/SKILL.md- License
- Apache-2.0
- Repo updated
- 20 August 2026
FAQ
What does the CI Health Report skill do?
Use when checking CI/CD health, Jenkins build failures, flaky tests, build success rates, or generating a CI health report. Trigger phrases: CI health, build failures, jenkins report, flaky tests, build health, are builds passing, CI status.
How do I install the CI Health Report skill?
Claude Code plugin: /plugin marketplace add npow/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is CI Health Report popular?
It lives in npow/claude-skills, which has 5 GitHub stars and 1 forks.
Related skills
Autopilot
5npow/claude-skills
Use when the user says "autopilot", "build this", "make it", "ship it", "just do it", "do it", "implement this", or gives a vague idea, spec, task list, or bug fix and expects autonomous execution. Handles decomposition, agent coordination, and verification automatically. "build me end to end", "go from idea to code", "do everything", "run this autonomously". Follows the Spec-Driven Development workflow: specify → clarify → plan → tasks → analyze → implement.
Build Python Library
5npow/claude-skills
Implements pip-installable Python libraries from scratch using src layout, pyproject.toml, and pytest. Use when the user asks to build, create, implement, or scaffold a Python library, package, pip package, middleware, SDK, or wrapper. Covers project scaffolding, proxy/wrapper patterns, provider-agnostic interfaces, async/sync support, and test infrastructure.
Canon Design Review
5npow/claude-skills
Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"
Deep QA
5npow/claude-skills
Use when reviewing, auditing, QAing, critiquing, verifying, or assessing any artifact — a spec, code change, diff, PR, research report, skill, prompt, or document. Also use for pre-completion verification ("verify this works", "prove this is done", "evidence before claiming complete"). Trigger phrases include "review this", "audit this", "QA this", "find issues", "find defects", "critique this", "check this for problems", "what's wrong with this", "evaluate this", "run QA", "review the diff", "review the PR", "review my code", "deep QA", "defect audit", "code review", "assess this", "verify th
Never Again
1malaysherasia-ai/claude-never-again
Capture a bug or mistake as a permanent guardrail so it cannot happen twice. Use this skill whenever a bug is fixed, a test fails and is repaired, the user says "you did that again", "don't do that", "remember this", "never do X", or any correction is made that a future session would otherwise forget. Also use when the user asks to review, promote, or clean up existing lessons and hooks.
Deep QA Ensemble V1
5npow/claude-skills
Use when the user asks to review with ensemble judges, or explicitly requests the ensemble variant of deep-qa. Benchmark variant that uses three heterogeneous providers for severity judging instead of a single judge. Same triggers as deep-qa but with multi-provider ensemble scoring.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.