ci-check-name-parity

Validate and align required-check names across GitHub workflows, .harness/ci-required-checks.json, harness.contract.json, and repo docs. Use this skill when CI check names or required-check policy changes.

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

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

The body is lean and efficient with excellent progressive disclosure and a clearly sequenced, validated workflow. The only gap is a missing concrete command for the rename-propagation step, which keeps actionability at 4 rather than 5.

Suggestions

Add an executable command or explicit step for propagating a rename across all sources of truth (e.g., a sed/grep recipe or a second script invocation) so the workflow is fully copy-paste ready.

Consider de-duplicating the report-script invocation between Workflow step 1 and the Validation section to shave a few tokens.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned body with no padding and no explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides real, executable commands (the report script, npm test, a full rg invocation) and references real bundle files, but the 'propagate the rename' step lacks a copy-paste command, keeping it just below fully executable.	4 / 5
Workflow Clarity	Numbered workflow with explicit fail-fast validation, a re-run-after-change feedback loop, and a dedicated Failure mode section providing checkpoints for error recovery.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references (comparison-matrix.md, contract.yaml, evals.yaml) and a scripts tool, each with 'Read when' navigation guidance; all referenced files exist.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is specific, distinctive, and explicitly answers both what and when with an explicit 'Use this skill when' trigger. It is held back from a perfect score only by slightly limited synonym/trigger coverage and a two-verb action set.

Suggestions

Broaden the 'when' clause with synonyms a user would naturally say, e.g. 'Use when CI check names, branch protection, required checks, or PR pipeline policy change.'

Add one or two more concrete verbs (e.g. 'propagate' renames, 'document' intentional mappings) to lift specificity from 4 to 5.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete sources (GitHub workflows, .harness/ci-required-checks.json, harness.contract.json, repo docs) with two concrete verbs ('Validate and align'), but lacks the multi-action coverage of a score-5 example.	4 / 5
Completeness	Clearly answers both 'what' (validate/align check names across four named sources) and 'when' (explicit 'Use this skill when...' clause), though the trigger enumeration is narrower than the score-5 example.	4 / 5
Trigger Term Quality	Includes natural trigger phrases ('CI check names', 'required-check policy changes') but misses common synonyms users might say like 'branch protection', 'PR pipeline', or 'check name drift'.	4 / 5
Distinctiveness Conflict Risk	Highly specific CI required-check name parity niche across four named config surfaces, making it unlikely to trigger for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/diagram-cli
Path: .codex/skills/ci-check-name-parity/SKILL.md
Commit: a07a18d

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.