CtrlK
BlogDocsLog inGet started
Tessl Logo

harness-sync

HAR: Sync Plans.md with implementation. Drift detect, marker update, retrospective. Trigger: sync-status, where am I, check progress. --snapshot for snapshots. Do NOT load for: planning, implementation, review, release.

79

Quality

100%

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

The canonical home for this skill is harness-sync in Chachamaru127/claude-code-harness

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, executable skill body: lean tables and copy-paste commands, a clear multi-step workflow with validation gates and confirmation checkpoints, and tidy self-contained organization. Note that the body references an external scripts/plan-registry.sh that is not bundled, but this is an environment path rather than a SKILL bundle reference.

DimensionReasoningScore

Conciseness

The body is lean — tables and executable commands dominate, with no padding explaining concepts Claude already knows, matching 'Lean and efficient; assumes Claude's competence'.

3 / 3

Actionability

Concrete copy-paste bash is provided throughout (e.g. 'grep -E "cc:完了|pm:確認済" Plans.md', 'git log --oneline -10', the snapshot mkdir+date block), meeting 'Fully executable code/commands; copy-paste ready'.

3 / 3

Workflow Clarity

A clear sequence (Step 0 → Step 6 plus R1–R4) is given with a Step 0 format-validation gate that stops on failure and a Step 3 yes/no confirmation checkpoint before the destructive Plans.md update, plus an anomaly-detection checklist.

3 / 3

Progressive Disclosure

The skill is self-contained with well-organized sections (Quick Reference, options, numbered steps, retrospective sub-steps); no bundle files are needed, so well-organized sections satisfy the anchor for skills without external references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person description that lists concrete actions, provides natural trigger phrases, and adds an explicit negative-trigger clause to avoid sibling-skill conflicts. Strong across all dimensions.

DimensionReasoningScore

Specificity

Quotes list multiple concrete actions — 'Drift detect, marker update, retrospective' and '--snapshot for snapshots' — matching the anchor 'Lists multiple specific concrete actions'.

3 / 3

Completeness

It states what ('Sync Plans.md with implementation. Drift detect, marker update, retrospective') and explicit when via 'Trigger: ...', plus a negative-trigger clause, clearly answering both what AND when.

3 / 3

Trigger Term Quality

'Trigger: sync-status, where am I, check progress' supplies natural phrases a user would say ('where am I', 'check progress'), meeting the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

The 'Do NOT load for: planning, implementation, review, release' clause carves a clear niche around Plans.md↔implementation sync and actively avoids conflict with sibling harness skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
Chachamaru127/claude-code-harness
Reviewed

Table of Contents

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.