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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

45%

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

The body is a well-organized overview with good progressive disclosure to a real references file, but it stops at description: no executable code or commands live in SKILL.md, and there is no sequenced implementation workflow with validation checkpoints. It reads as a concept summary rather than an actionable guide.

Suggestions

Add at least one minimal executable snippet (e.g. a command bus dispatch + a read-model projection) directly in SKILL.md so the skill is actionable before opening references.

Replace the ASCII diagram and 'Comprehensive guide...' line with a compact sequence (command -> handler -> event -> projector -> read model) that doubles as the workflow.

Spell out a validation/feedback loop for projection rebuild and eventual consistency (rebuild -> checkpoint -> verify read model version) instead of listing it only as a do/don't.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with a useful table and do/don't lists, but the ASCII architecture diagram and restating of CQRS concepts Claude already knows ('Comprehensive guide to implementing CQRS patterns') add tokens that could be trimmed.	2 / 3
Actionability	The body offers no executable code or commands; it describes components in a table and defers all templates to references/details.md, matching the 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	There is a clear when-to-use list and component breakdown, but no sequenced implementation workflow, and validation/checkpoints for eventual consistency or projection rebuilds are only mentioned as do/don't items rather than as explicit steps.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview that clearly signals a single one-level-deep reference (references/details.md) for templates, and that file exists with well-organized template sections; navigation is easy.	3 / 3
	Total	8 / 12 Passed

Description

67%

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 cleanly answers both what and when with an explicit 'Use when' clause, but it reads as a domain declaration rather than a list of concrete actions and leans on pattern jargon over natural user phrasings. It is distinguishable but broad enough to risk overlap with general architecture skills.

Suggestions

Lead with concrete actions (e.g. 'Separate read and write handlers, build event projections, sync read models from an event store') instead of restating the CQRS pattern name as the action.

Add natural trigger phrasings a user would say verbatim, such as 'CQRS', 'command/query separation', 'read model', or 'event-sourced system'.

Tighten 'scalable architectures' to a clearer niche so it conflicts less with general database or API-design skills.

Dimension	Reasoning	Score
Specificity	Names the domain (CQRS, read/write models, query performance, event-sourced systems) but lists the pattern rather than multiple distinct concrete actions; closer to 'Processes PDF files and extracts content' than a multi-action list.	2 / 3
Completeness	Explicitly answers both what ('Implement Command Query Responsibility Segregation for scalable architectures') and when ('Use when separating read and write models, optimizing query performance, or building event-sourced systems'), satisfying the 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes relevant terms ('separating read and write models', 'query performance', 'event-sourced systems') but relies on pattern jargon; missing common user phrasings like 'CQRS', 'command/query separation', or 'read model' as standalone triggers.	2 / 3
Distinctiveness Conflict Risk	The CQRS niche is fairly specific but 'scalable architectures' and 'optimizing query performance' are broad enough to overlap with general database or architecture skills.	2 / 3
	Total	9 / 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: wshobson/agents
Commit: 5cc2549

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