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.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

78%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 well-structured, actionable skill body: concrete hook scripts with graceful-degradation validation, a clear auditing checklist, and clean one-level-deep reference splitting. Slightly verbose in places and uses some project-specific placeholders, but genuinely non-obvious domain guidance throughout.

Suggestions

Tighten the checklist item rationales (e.g. the coverage and deploy-docs items) to one line each — the core rule is already stated up front.

Replace the remaining `<external-check-name>`/`<external-scanner>` placeholders with one fully-worked concrete example (SonarQube already is) and note the templating convention once, rather than scattering placeholders.

Consider an explicit 'Audit workflow' numbered sequence at the top that references the later sections in order, so the thematic sections read as an ordered procedure.

DimensionReasoningScore

Conciseness

Dense, substantive domain guidance that mostly earns its tokens (non-obvious points like the gitleaks --staged sham check and image parity), but several checklist elaborations and rationale paragraphs could be tightened without losing clarity.

4 / 5

Actionability

Provides concrete, executable pre-commit/pre-push shell scripts, a full SonarQube graceful-degradation script, GitHub Actions YAML, and gitleaks commands; minor gaps come from `<external-check-name>` style placeholders and the full CI YAML being delegated to the reference file.

4 / 5

Workflow Clarity

A clear auditing checklist plus explicit validation checkpoints (the 3-step credential/reachable/real-check gate and 'query the real CI pipeline status') and feedback loops are present, but the cross-section ordering is thematic rather than one strict end-to-end procedure.

4 / 5

Progressive Disclosure

SKILL.md serves as the overview with well-signaled, one-level-deep links to the real references/ci-examples.md file (verified present) for Woodpecker/GitLab syntax, full gitleaks YAML, and the container reproduction command — easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

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

An excellent description: concrete actions, natural trigger terms including a real user phrase, explicit what-and-when guidance, and a distinct niche. Uses the conventional third-person 'Use when' trigger form rather than first/second person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'ensures pnpm/npm verify actually covers everything CI checks', 'adds pre-commit/pre-push git hooks that enforce this locally', 'keeps trunk-based development honest (small commits, frequent pushes, CI checked per push not per batch)' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (the three 'ensures' actions) and when ('Use when setting up or auditing…', 'Load before building a new .woodpecker.yml/.github/workflows…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms including file extensions (.woodpecker.yml/.github/workflows), tool names (SonarQube, gitleaks implied), and the genuinely user-spoken phrase 'it passed locally but failed in CI'.

5 / 5

Distinctiveness Conflict Risk

Carves out a clear niche — the CI/local parity axis — with distinct, specific triggers that are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

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