coding-harness

Use when users need to install, bootstrap, upgrade, audit, diagnose, or explain @brainwav/coding-harness in a repository, including harness init/upgrade, CI migration, governance gates, command discovery, and Codex environment action sync.

Quality

90%

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

88%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 highly actionable with exact commands, a well-sequenced validated workflow, and good progressive disclosure to real bundle files. Minor overlap across safety/constraint sections and a few external reference paths prevent top marks on conciseness and disclosure.

Suggestions

Consolidate overlapping safety guidance (Philosophy, Avoid, Constraints, Execution Boundaries, Anti-Patterns) into a single section to cut redundancy and tokens.

Verify or annotate the Infrastructure/references/... paths in the Progressive Disclosure section; either confirm they resolve in the bundle or mark them as routing hints distinct from local references.

Consider trimming the contract/state bullets that restate commands already shown in Current Command Shape and Validation to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Dense, lean bullets with no padding or explanation of known concepts, though several sections (Philosophy, Avoid, Constraints, Execution Boundaries, Anti-Patterns) overlap and could be consolidated for a tighter token budget.	4 / 5
Actionability	Provides copy-paste-ready exact commands for the common cases (harness next --json, harness upgrade --dry-run, harness ci-migrate prepare --provider circleci --dry-run, pnpm exec tsx src/cli.ts next --json), fully executable guidance.	5 / 5
Workflow Clarity	A numbered 7-step workflow with explicit validation checkpoints (dry-run before mutation, focused gates before broad checks, stop at first blocking gate, fix and rerun) and feedback loops for destructive/batch operations like CI migration and cleanup.	5 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to real bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json); some Infrastructure/... reference paths are not present in the bundle, slightly muddying navigation.	4 / 5
	Total	18 / 20 Passed

Description

92%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, trigger-rich, and clearly distinguishes the skill with an explicit 'Use when...' clause tied to a named package. It strongly matches the highest anchors across all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (install, bootstrap, upgrade, audit, diagnose, explain) plus specific subsystems (harness init/upgrade, CI migration, governance gates, command discovery, Codex env action sync), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (operate @brainwav/coding-harness) and when via a clear 'Use when users need to...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger verbs and phrases a user would say (install, bootstrap, upgrade, audit, diagnose, explain, CI migration, governance gates, command discovery), though it lacks synonyms or extension-style terms common to the highest anchor.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to a named package @brainwav/coding-harness with distinct triggers (harness init/upgrade, CI migration, governance gates, Codex env action sync), giving a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 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/Agent-Skills
Path: Skills/agent-ops/coding-harness/SKILL.md
Commit: f1f2f21

Reviewed: 21 hours 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.