agent-crdt-synchronizer

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

2.93x

Quality

11%

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 description is extremely minimal and essentially non-functional as a skill selector. It provides no information about what the skill does, what actions it performs, or when it should be used. The only distinguishing element is the technical name 'crdt-synchronizer', which is insufficient for Claude to make informed skill selection decisions.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Synchronizes conflict-free replicated data types (CRDTs) across distributed nodes, 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 CRDT merge conflicts, or manage replicated state across nodes.'

Include natural keywords users might say, such as 'distributed data sync', 'eventual consistency', 'replicated data', 'merge conflicts', 'CRDT' to improve trigger term coverage.

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 provides an invocation command ('invoke with $agent-crdt-synchronizer') but no functional description or usage triggers.	1 / 3
Trigger Term Quality	The only keyword is 'crdt-synchronizer', which is technical jargon. There are no natural user-facing trigger terms. A user would not naturally say 'crdt-synchronizer' when seeking help with conflict-free replicated data types or synchronization tasks.	1 / 3
Distinctiveness Conflict Risk	The term 'crdt-synchronizer' is niche enough that it's unlikely to conflict with many other skills, but the lack of any descriptive content means Claude cannot reliably determine when to select it versus other data synchronization or collaboration skills.	2 / 3
	Total	5 / 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 dump of CRDT implementation code that explains well-known computer science concepts Claude already understands. It lacks any clear workflow, has no validation steps, references undefined dependencies and fictional MCP tools, and fails to organize content with progressive disclosure. The skill would benefit enormously from being reduced to a concise overview with project-specific conventions and references to separate implementation files.

Suggestions

Reduce the content to a concise overview (under 100 lines) covering project-specific CRDT conventions, supported types, and usage patterns—move full implementations to separate reference files.

Add a clear workflow section with numbered steps for initializing, synchronizing, and validating CRDT state, including error recovery procedures.

Remove or replace references to undefined dependencies (VectorClock, SyncScheduler, PNCounter, ORMap) and fictional MCP tools with actual available tools or clearly mark them as interfaces to implement.

Add progressive disclosure by splitting into SKILL.md (overview + quick start) and separate files like CRDT_TYPES.md, DELTA_SYNC.md, and CONSENSUS_INTEGRATION.md with clear navigation links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines of code. Most of this is standard CRDT implementation that Claude already knows (G-Counter, OR-Set, LWW-Register, RGA are well-documented academic concepts). The skill dumps full class implementations rather than providing concise, project-specific guidance.	1 / 3
Actionability	The code examples are relatively complete JavaScript implementations, but they reference undefined dependencies (VectorClock, SyncScheduler, PNCounter, ORMap) and fictional MCP tools (memory_usage, metrics_collect, neural_patterns). The code is illustrative rather than truly executable or copy-paste ready.	2 / 3
Workflow Clarity	There is no clear workflow or sequence of steps for when/how to use this synchronizer. It's a collection of class implementations without guidance on deployment order, initialization sequence, validation checkpoints, or error recovery procedures. The 'Core Responsibilities' section lists concepts but not actionable steps.	1 / 3
Progressive Disclosure	Monolithic wall of code with no references to external files. All CRDT implementations are inlined when they could easily be split into separate reference files. The document lacks a quick-start section and buries any overview under hundreds of lines of implementation detail.	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: f547cec

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