nic-ci-pipelines

CI/CD pipeline structure, GitHub Actions workflows, reusable workflow patterns, and matrix builds for NIC. Use when working on CI workflows, debugging build failures, adding new workflow steps, modifying build matrices, or understanding the release pipeline.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured reference skill that conveys CI pipeline architecture and key constraints efficiently without padding. Actionability and progressive disclosure are strong but not maximal given the reference-only, single-file nature.

Suggestions

Add a short "common tasks" section with one or two concrete commands (e.g., how to run a single matrix job locally or re-trigger a workflow) to lift actionability from reference-descriptive to executable.

Consider splitting the detailed workflow tables into a references/ file linked from a trimmed overview, which would let the body stay a tighter entry point while preserving detail.

Add a brief validation note for the destructive guardrails (e.g., how to verify a NAP matrix stays amd64-only or confirm a secret was not committed) to give the Gotchas a feedback-loop character.

Dimension	Reasoning	Score
Conciseness	Lean reference material with no concept padding (no explanation of what GitHub Actions is), well-structured tables and bullets; every token earns its place and Claude's competence is assumed.	5 / 5
Actionability	Provides concrete guidance via specific file paths (".github/data/matrix-images-oss.json"), named workflows, and concrete patterns; as an instruction-only reference it has no executable code, but the guidance is actionable with minor gaps.	4 / 5
Workflow Clarity	The architecture diagram clearly sequences reusable-workflow composition, and the Gotchas section acts as guardrails; there are no validation/feedback loops, but no destructive batch operation is being prescribed, so the cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Architecture, Key Workflows, CI Patterns, Gotchas) with no external references needed for this overview; at ~120 lines the simple-skill 5 exception does not strictly apply, and a few detailed tables could theoretically be split out.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both scope and trigger conditions with concrete, natural language a user would say. The only weakness is that the "what" portion leans on noun-phrases rather than verb-actions.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capabilities ("reusable workflow patterns", "matrix builds") plus concrete trigger actions ("debugging build failures", "modifying build matrices"), but the "what" leans on nouns rather than verb-actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("CI/CD pipeline structure, GitHub Actions workflows, reusable workflow patterns, and matrix builds for NIC") and when ("Use when working on CI workflows, debugging build failures...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage with phrases a user would actually say ("CI workflows", "build failures", "build matrices", "release pipeline"), though a few synonyms or file-path triggers are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped explicitly to "NIC" with a clear CI/CD niche and distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nginx/kubernetes-ingress
Path: .github/skills/nic-ci-pipelines/SKILL.md
Commit: 0eb3072

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.