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

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/nic-ci-pipelines/SKILL.md

Quality

Content

63%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 thorough, well-structured reference for NIC CI/CD with concrete gotchas and a clear release-pipeline sequence. Its main weaknesses are restated release architecture, a monolithic single-file layout with no progressive disclosure to reference files, and the absence of copy-paste workflow templates.

Suggestions

Split the 'Key Workflows' catalog and 'CI Patterns' into a reference file (e.g. references/workflows.md) and keep SKILL.md a lean overview that links to it, improving progressive_disclosure.

De-duplicate the two-stage release description: keep one canonical explanation (prose or diagram) and have the other sections reference it rather than restaging build/publish/registries each time.

Add 1-2 copy-paste workflow snippets or a 'workflow_call' template for the most common tasks (adding a matrix variant, adding a gated job) to lift actionability toward fully executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is information-dense project knowledge with no basic-concept padding, but the two-stage release architecture is restated across the ASCII diagram, the 'Two-Stage Release Architecture' prose, and the release workflow tables, so it could be tightened; not a 4 'minor instances' case.	3 / 5
Actionability	Concrete scripts, paths, and commands ('.github/scripts/validate-workflow-gating.sh', 'make update-crds', 'copy-images.sh $1', 'get-from-vault') plus explicit do/don't gotchas give mostly executable guidance; it stops short of 5 because there are no copy-paste workflow templates for common tasks.	4 / 5
Workflow Clarity	The prep -> publish pipeline is clearly sequenced with an explicit 'release-gate' validation step and a retry-without-rebuild feedback loop, and the gotchas act as a checklist; it is reference-oriented rather than a numbered task checklist, so it does not reach 5.	4 / 5
Progressive Disclosure	Headers and a 'read this first' overview give good navigation, but this is a ~440-line monolith with no bundle files: the Key Workflows catalog and CI Patterns could live in separate reference files, fitting the 'content that should be separate is inline' anchor rather than the 'most content appropriately placed' bar of 4.	3 / 5
	Total	14 / 20 Passed

Description

82%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, third-person description with an explicit 'Use when' trigger clause and a well-scoped NIC niche. The only weakness is that the 'what' states covered topics rather than concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete areas ('reusable workflow patterns, and matrix builds for NIC') but the 'what' clause is topic nouns rather than action verbs, so it does not reach the 'lists several specific actions' bar of 4.	3 / 5
Completeness	Explicitly answers 'what' ('CI/CD pipeline structure, GitHub Actions workflows, reusable workflow patterns, and matrix builds for NIC') and 'when' with a 'Use when ...' clause listing five concrete triggers, matching the anchor.	5 / 5
Trigger Term Quality	Natural developer phrases like 'debugging build failures', 'adding new workflow steps', and 'modifying build matrices' give good keyword coverage; a few synonyms (e.g. workflow file extensions, 'GitHub Actions' variants) are missing, stopping short of 5.	4 / 5
Distinctiveness Conflict Risk	The 'for NIC' scoping and CI/CD-specific triggers carve a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: 95d3987

Reviewed: 3 days 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.