cqrs-implementation

Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cqrs-implementation/SKILL.md

Quality

Content

65%

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

A concise, well-structured overview with clear use/no-use guidance, but the instructions stay at a high level without executable detail or explicit validation checkpoints, and the single referenced resource file is absent from the bundle.

Suggestions

Add concrete, actionable detail to the Instructions — e.g., a minimal command/query interface sketch or a specific projection pattern — so the body instructs rather than describes.

Make the validation step an explicit checkpoint with a feedback loop (validate → fix → re-validate) before declaring the implementation complete.

Either create the referenced 'resources/implementation-playbook.md' or remove the dangling reference so progressive disclosure points to real content.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows; the use/do-not-use lists and instructions are brief with no padding, so most tokens earn their place.	3 / 3
Actionability	Instructions such as 'Define command and query models with clear boundaries' and 'Implement read model projections and synchronization' are recognizable process steps but remain abstract, with no concrete code, commands, or specific patterns.	2 / 3
Workflow Clarity	A sequence exists (identify → define → implement → validate) and validation is mentioned, but it is a single implicit step with no explicit checkpoints or fix→retry feedback loop.	2 / 3
Progressive Disclosure	The body is well organized and signals a one-level reference to 'resources/implementation-playbook.md', but that referenced path does not exist in the bundle, so the disclosure points to missing detail.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 strong, focused description that clearly states the capability and provides explicit use-when guidance for a distinct architectural niche. The main weakness is trigger-term naturalness: it leans on formal terminology over the shorthand users actually say.

Dimension	Reasoning	Score
Specificity	Names multiple concrete activities — 'separating read and write models, optimizing query performance, or building event-sourced systems' — matching the anchor for listing several specific actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Implement Command Query Responsibility Segregation for scalable architectures') and when via a clear 'Use when...' clause with explicit triggers.	3 / 3
Trigger Term Quality	Trigger terms are domain-appropriate but technical; it spells out 'Command Query Responsibility Segregation' and 'event-sourced systems' rather than the common variations ('CQRS', 'event sourcing') a user would naturally say, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	CQRS is a well-defined niche with distinct, specific triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/cqrs-implementation/SKILL.md
Commit: e63f7dd

Reviewed: about 5 hours 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.