agent-crdt-synchronizer

Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer

2.93x

Quality

—

Does it follow best practices?

Impact

97%

2.93x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

27%

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

The skill body is an extensive code catalog of CRDT implementations that is verbose and monolithic, with undefined helper types preventing full executability and no progressive disclosure or validation-gated workflow. It reads as a reference dump rather than focused, actionable guidance.

Suggestions

Move the full class implementations into reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links, e.g. 'G-Counter: see [references/g-counter.js]'.

Define or stub the undefined dependencies (VectorClock, SyncScheduler, applyOrderedOperation, applyCRDTOperation, serializeState) so the code is actually executable, or explicitly justify them as pseudocode.

Add a sequenced synchronization workflow with validation checkpoints (e.g. verify vector-clock ordering, confirm convergence after merge, retry on sync failure) rather than presenting classes in isolation.

Dimension	Reasoning	Score
Conciseness	The body is ~970 lines of full class implementations with repeated boilerplate (onUpdate/notifyUpdate copied into every class) and explanatory CRDT concepts Claude already knows, matching the 'verbose; padded with unnecessary context' anchor rather than the mostly-efficient score-2.	1 / 3
Actionability	The class methods are concrete and largely complete, but several referenced types are never defined (VectorClock, SyncScheduler, applyOrderedOperation, applyCRDTOperation, serializeState), so the code is not fully executable or copy-paste ready, fitting the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	Content is organized as a catalog of CRDT implementations rather than a sequenced workflow, and the synchronization/distributed operations lack explicit validation checkpoints or error-recovery feedback loops, matching the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Everything lives in one ~970-line monolithic file with no bundle files, no split-out references, and no navigation signals, matching the 'monolithic wall of text; poor organization' anchor rather than score-2 which requires some structure and signaled references.	1 / 3
	Total	6 / 12 Passed

Description

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 generic boilerplate that names the skill and its invocation token but never states its capabilities or when to use it. It fails all four dimensions because nothing concrete or trigger-oriented is communicated.

Suggestions

Replace the description with concrete CRDT actions, e.g. 'Implements state-based and operation-based CRDTs (G-Counter, OR-Set, LWW-Register, RGA) with delta synchronization for eventually consistent distributed state.'

Add an explicit trigger clause: 'Use when synchronizing replicated state across nodes, resolving merge conflicts without consensus, or implementing conflict-free data types.'

Drop the '$agent-crdt-synchronizer' invocation token from the description; trigger terms should reflect natural user phrasing, not internal invocation syntax.

Dimension	Reasoning	Score
Specificity	The phrase 'Agent skill for crdt-synchronizer' only labels the skill and names no concrete actions, matching the 'vague or no actions' anchor rather than the score-2 anchor that names domain and some actions.	1 / 3
Completeness	It states only that this is an 'Agent skill for crdt-synchronizer' and omits both what it concretely does and any 'Use when...' trigger, so neither the what nor the when is explicitly answered.	1 / 3
Trigger Term Quality	'invoke with $agent-crdt-synchronizer' is an invocation token, not a natural keyword a user would say; there is no plain-language trigger term, matching the 'no natural keywords' anchor.	1 / 3
Distinctiveness Conflict Risk	The boilerplate 'Agent skill for X - invoke with $X' pattern carries no capability signal and would be indistinguishable from any other similarly-formatted skill, matching the 'very generic; would conflict' anchor.	1 / 3
	Total	4 / 12 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
skill_md_line_count	SKILL.md is long (1002 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: ruvnet/claude-flow
Commit: 03d4f84

Reviewed: 2 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.