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

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-crdt-synchronizer/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely weak description that essentially only provides an invocation command. It fails on every dimension: no concrete actions, no natural trigger terms, no 'what' or 'when' guidance, and no distinguishing information. Claude would have no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Synchronizes data across distributed nodes using CRDTs (Conflict-free Replicated Data Types), resolves merge conflicts, and maintains eventual consistency.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to synchronize distributed data, resolve merge conflicts in replicated systems, or work with CRDT-based collaboration.'

Remove the invocation instruction ('invoke with $agent-crdt-synchronizer') from the description and replace it with functional content that helps Claude decide when this skill is relevant.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for crdt-synchronizer' is entirely abstract and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the invocation command, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'crdt-synchronizer', which is technical jargon unlikely to be used naturally by users. There are no natural keywords like 'sync', 'conflict resolution', 'collaborative editing', or 'real-time data'.	1 / 3
Distinctiveness Conflict Risk	While 'crdt-synchronizer' is a specific name, the description is so vague that Claude cannot determine when to use it versus any other agent skill. The lack of any functional description makes it indistinguishable in practice.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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

This skill is an extremely verbose code dump of CRDT implementations that provides little actionable guidance beyond what Claude already knows about CRDTs. It lacks any workflow structure, validation steps, or progressive disclosure — it reads more like an incomplete library source file than an instructional skill. The code references many undefined classes and contains simplified placeholder logic, undermining its claim to actionability.

Suggestions

Replace the full class implementations with a concise overview of supported CRDT types, key API patterns, and specific gotchas/constraints that Claude wouldn't already know — aim for under 100 lines.

Add a clear step-by-step workflow showing how to initialize a CRDT synchronizer, register data types, perform sync operations, and validate convergence, with explicit checkpoints.

Split detailed implementations into separate reference files (e.g., COUNTERS.md, SETS.md, REGISTERS.md) and keep SKILL.md as a navigational overview with links.

Ensure code examples are either fully executable (with all dependencies defined or imported) or clearly labeled as illustrative patterns rather than copy-paste-ready code.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~700+ lines of code. Most of this is standard CRDT implementation that Claude already understands conceptually. The skill dumps full class implementations for G-Counter, OR-Set, LWW-Register, RGA, Delta-State framework, Causal Tracker, Composite CRDT, and Consensus Integration — all of which could be summarized in a fraction of the space with key patterns and gotchas only.	1 / 3
Actionability	The code examples are fairly complete JavaScript classes, but they reference undefined dependencies (VectorClock, SyncScheduler, PNCounter, ORMap, sendSyncRequest, etc.) making them not truly executable. Several methods contain simplified/placeholder logic with comments like 'in practice would use more sophisticated causal ordering' — this is pseudocode dressed as real code.	2 / 3
Workflow Clarity	There is no clear workflow or step-by-step process for how to actually use this CRDT synchronizer. The content is a collection of class implementations without guidance on sequencing operations, no validation checkpoints, no error recovery steps, and no clear instructions on when/how to invoke synchronization or verify convergence.	1 / 3
Progressive Disclosure	The entire content is a monolithic wall of code with no references to external files and no layered structure. All CRDT implementations are inlined in a single document with no separation between quick-start overview and detailed reference material. No bundle files exist to support progressive disclosure.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 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	10 / 11 Passed

Repository: ruvnet/claude-flow
Commit: 9d4a9ea

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