CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cqrs-implementation/SKILL.md

The canonical home for this skill is cqrs-implementation in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The body is concise and well-structured with clear use/not-use guidance, but the instructions are abstract rather than executable and the single referenced resource file is missing from the bundle.

Suggestions

Add concrete, executable guidance to the Instructions section — example code snippets, specific commands, or a worked example of defining a command/query model and a read-model projection.

Create the referenced 'resources/implementation-playbook.md' file (or fix the path) so the progressive-disclosure navigation target actually exists.

Add an explicit validation checkpoint with a feedback loop (e.g., 'After implementing projections, verify read model consistency against the write model; if inconsistent, reprocess events') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with bullet lists and no concept-explaining fluff; every section earns its place and it assumes Claude's competence.

5 / 5

Actionability

Instructions give domain-specific directives ('Identify read/write workloads', 'Define command and query models') but are abstract and lack concrete code, commands, or specific executable details.

3 / 5

Workflow Clarity

A sequence is present (Identify, Define, Implement, Validate) with a final validation step, but checkpoints are implicit rather than explicit and lack feedback loops for error recovery.

3 / 5

Progressive Disclosure

Sections are well-organized and a one-level-deep reference is clearly signaled, but the referenced file 'resources/implementation-playbook.md' does not exist, making the navigation target broken.

3 / 5

Total

14

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 concise, concrete, and complete, clearly stating both what the skill does and when to use it with natural trigger phrases. It is distinctive within the architecture-skill space with minimal conflict risk.

DimensionReasoningScore

Specificity

Names the CQRS domain and multiple concrete actions (separating read/write models, optimizing query performance, building event-sourced systems) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Implement Command Query Responsibility Segregation for scalable architectures') and when ('Use when separating read and write models...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('separating read and write models', 'optimizing query performance', 'event-sourced systems'), but is missing a few common synonyms and tech variants.

4 / 5

Distinctiveness Conflict Risk

CQRS is a clear architectural niche with distinct triggers (event-sourced systems, read/write models) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.