CtrlK
BlogDocsLog inGet started
Tessl Logo

vannifr/ci-local-parity

Use when setting up or auditing a project's CI/CD pipeline together with local verification — ensures pnpm/npm verify (or equivalent) actually covers everything CI checks, adds pre-commit/pre-push git hooks that enforce this locally, and keeps trunk-based development honest (small commits, frequent pushes, CI checked per push not per batch). Load before building a new .woodpecker.yml/.github/workflows, before adding SonarQube/coverage, or when "it passed locally but failed in CI" comes up.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%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.

Highly actionable content with clear workflows, validation feedback loops, and clean progressive disclosure to a real reference file. The main weakness is verbosity from repeated gitleaks treatment and long prose that could be tightened.

Suggestions

Consolidate the gitleaks guidance: cover it once in the 'Gitleaks in CI' subsection and trim the checklist bullet and the standalone 'Gitleaks belongs in pre-commit' paragraph to brief cross-references.

Tighten the checklist items: several state both the rule and its rationale inline; consider moving rationale to a sub-bullet or trimming to reduce token load.

Pull the inline gitleaks diff-scoping prose ('--staged locally, diff-scoped in CI...') into references/ci-examples.md alongside the YAML it describes, keeping the body to the principle.

DimensionReasoningScore

Conciseness

The body is skill-specific and avoids explaining basics Claude already knows, but at ~260 lines it repeats the gitleaks topic across the checklist, a dedicated paragraph, and a subsection, and could be tightened without losing guidance.

3 / 5

Actionability

Provides fully executable, copy-paste-ready shell hook scripts, a concrete gracefully-degrading SonarQube check, GitHub Actions YAML, and a real reference file with complete Woodpecker/GitLab/gitleaks YAML covering the common cases.

5 / 5

Workflow Clarity

An explicit audit checklist sequences the work, and the degrading external check (credentials present → service reachable → real check, passing through its exit code) plus "How to catch this going forward" steps give explicit validation checkpoints and error-recovery feedback loops.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to references/ci-examples.md (verified present) offload the detailed Woodpecker/GitLab/gitleaks YAML and the docker reproduce command, keeping the body an overview with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

96%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, specific description with explicit trigger guidance, concrete actions, and natural user phrasing. Its only weakness is mild overlap risk with adjacent git-hook and config-drift skills, which the body explicitly acknowledges.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "ensures pnpm/npm verify... actually covers everything CI checks", "adds pre-commit/pre-push git hooks", "keeps trunk-based development honest" — giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both what (coverage verification, hooks, trunk-based enforcement) and when ("Use when setting up or auditing...", "Load before building a new .woodpecker.yml...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms including the colloquial user phrase "it passed locally but failed in CI" plus concrete config file names like ".woodpecker.yml/.github/workflows" and "SonarQube/coverage".

5 / 5

Distinctiveness Conflict Risk

The CI/local-parity framing is a clear distinct niche, but overlap-prone terms ("pre-commit/pre-push git hooks", "coverage") and the body's own disambiguation from claude-pre-commit/config-drift-checker indicate minor overlap risk with closely related skills.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents