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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-crdt-synchronizer/SKILL.md

Quality

Content

14%Scale 1-3

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 extensive but poorly structured dump of CRDT reference implementations that reads more like a textbook chapter than actionable agent guidance. It lacks workflow clarity (no step-by-step usage instructions, no validation checkpoints), is extremely verbose with implementations Claude could derive from its training, and references fictional/undefined APIs. The content would benefit enormously from being restructured into a concise overview with clear usage workflows and separated reference material.

Suggestions

Replace the monolithic code dump with a concise overview (under 100 lines) that describes when to use each CRDT type, with a quick-start example showing a complete working synchronization flow.

Add a clear step-by-step workflow: 1) Choose CRDT type based on use case, 2) Initialize and register, 3) Perform operations, 4) Synchronize with peers, 5) Validate convergence — with explicit validation checkpoints.

Move detailed class implementations into separate reference files (e.g., GCOUNTER.md, ORSET.md, RGA.md) and link to them from the main skill with clear navigation signals.

Remove or replace references to undefined/fictional APIs (neural_patterns, metrics_collect, VectorClock, SyncScheduler) with either real implementations or explicit notes that these are project-specific dependencies that must be provided.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~700+ lines of code. Most of this is textbook 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 — far more than needed for actionable guidance. References to fictional MCP tools (neural_patterns, metrics_collect) add unnecessary noise.	1 / 3
Actionability	The code examples are syntactically complete JavaScript classes, but they depend on undefined classes (VectorClock, SyncScheduler, PNCounter, ORMap) and fictional MCP tool APIs, making them not truly executable. The code is more of a reference implementation/pseudocode than copy-paste ready guidance for a real task.	2 / 3
Workflow Clarity	There is no clear workflow or sequence of steps for how to actually use this synchronizer. The skill presents class implementations but never describes when to use which CRDT type, how to set up synchronization, or what validation/verification steps to follow. No error recovery or validation checkpoints are defined despite this being a distributed systems operation.	1 / 3
Progressive Disclosure	The entire skill is a monolithic wall of code with no references to external files and no layered structure. All CRDT implementations are inlined rather than being split into separate reference files. There's no quick-start section or overview that points to detailed materials — everything is dumped at the same level.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 fails on every dimension. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads more like a label than a functional description.

Suggestions

Describe the concrete actions the skill performs, e.g., 'Synchronizes CRDT data structures, resolves merge conflicts in distributed documents, manages real-time collaborative state.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to synchronize distributed data, resolve CRDT conflicts, or manage collaborative editing state.'

Remove the invocation instruction ('invoke with $agent-crdt-synchronizer') from the description, as it wastes space that should be used for capability and trigger information.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for crdt-synchronizer' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and how to invoke it, providing no functional or trigger information.	1 / 3
Trigger Term Quality	The only keyword is 'crdt-synchronizer', which is technical jargon. There are no natural language terms a user would say, such as 'sync', 'conflict resolution', 'real-time collaboration', or 'merge'.	1 / 3
Distinctiveness Conflict Risk	The description is so generic ('agent skill for X') that it provides no distinguishing characteristics. Without knowing what it does, it could conflict with any data synchronization or collaboration skill.	1 / 3
	Total	4 / 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
Path: .agents/skills/agent-crdt-synchronizer/SKILL.md
Commit: 913f9ea

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.