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.

1.64x

Quality

—

Does it follow best practices?

Impact

87%

1.64x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with complete executable code, but it is a monolithic, token-heavy file with no progressive disclosure into referenced files and lacks an explicit sequenced workflow with validation checkpoints for its database/event operations.

Suggestions

Move the five large code templates into scripts/ files and replace inline blocks with short snippets plus clearly signaled references (e.g., 'See scripts/command_bus.py'), keeping SKILL.md a concise overview.

Add an explicit numbered implementation workflow (define commands → wire handlers → set up projections → wire API) with validation checkpoints (e.g., verify the event store after appending, confirm read-model lag is within SLA before serving queries).

Tighten the body by trimming the inline ASCII architecture diagram and duplicative template boilerplate, retaining only what Claude would not already know.

Dimension	Reasoning	Score
Conciseness	The body avoids lecturing on CQRS theory but ships ~400 lines of inline Python across five templates, which is far more tokens than needed inline and could be tightened or moved to scripts/; matches 'mostly efficient but could be tightened' rather than the lean top anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code (CommandBus, QueryBus, FastAPI endpoints, read-model synchronizer, consistency handler), matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Templates imply a sequence but there is no explicit ordered implementation workflow and no validation checkpoints/feedback loops for the event-store and database operations, matching the 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	All content sits inline in a single SKILL.md with no references/ or scripts/ files, and large code templates that should be separate are inline, matching the 'content that should be separate is inline' anchor rather than the one-level-deep reference pattern.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 is specific, uses third person, and includes an explicit 'Use when' clause covering both what the skill does and when to invoke it. Trigger terms are natural and the niche is distinct from other skills.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions: 'Implement Command Query Responsibility Segregation', 'separating read and write models, optimizing query performance, or building event-sourced systems' — closest to the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' ('Implement CQRS for scalable architectures') and 'when' via an explicit 'Use when...' clause, matching the top anchor; not capped at 2 because the trigger clause is present.	3 / 3
Trigger Term Quality	Natural terms a user would say appear: 'separating read and write models', 'optimizing query performance', 'building event-sourced systems' — good coverage of natural variations, matching the top anchor; not reduced to 2 because it goes beyond a single keyword.	3 / 3
Distinctiveness Conflict Risk	CQRS is a clear niche with distinct triggers (event-sourcing, read/write model separation) unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (555 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

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.