Tessl • The management layer for AI agent skills

SkillPublic

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

68%

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 ./.agent/skills/cqrs-implementation/SKILL.md

Quality

Content

46%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 well-organized and token-efficient with clear use/don't-use sections, but the instructions are abstract directives with no concrete guidance, and progressive disclosure fails at its core job: the single referenced playbook file does not exist in the bundle and is cited at two conflicting paths. The workflow lacks validation checkpoints or failure-recovery loops despite covering projection synchronization, an operation prone to drift and failure.

Suggestions

Fix the dangling references: create the playbook at a single canonical path (e.g. references/implementation-playbook.md) and update both the Instructions, Resources, and Knowledge Modules sections to point to it consistently.

Add concrete, executable guidance to the Instructions — e.g. a named projection pattern, a synchronization approach (change-data-capture vs event subscription), or a short code sketch — instead of abstract directives like 'Implement read model projections and synchronization'.

Add validation checkpoints with feedback loops, e.g. how to detect projection lag or rebuild a read model after failure, rather than the single unelaborated 'Validate performance, recovery, and failure modes' bullet.

Trim the duplication between the 'Use this skill when' bullets and the frontmatter description, and merge the Resources and Knowledge Modules sections into one.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of CQRS concepts, but the 'Use this skill when' bullets largely restate the frontmatter description, and the playbook is referenced twice in different sections at inconsistent paths.	4 / 5
Actionability	The Instructions are high-level directives ('Define command and query models with clear boundaries', 'Implement read model projections and synchronization') with no concrete patterns, commands, or examples; all specifics are deferred to an external playbook, leaving minimal concrete guidance in the body.	2 / 5
Workflow Clarity	A rough sequence is present (identify → define → implement → validate) and validation is named ('Validate performance, recovery, and failure modes'), but there are no explicit checkpoints or feedback loops describing what to do when synchronization or validation fails.	3 / 5
Progressive Disclosure	Scored against the actual bundle: no bundle files or directories exist, so the only detailed reference is dangling, and it is duplicated at two inconsistent paths ('resources/implementation-playbook.md' vs './sub-skills/implementation-playbook.md'), breaking navigation to the deferred content.	2 / 5
	Total	11 / 20 Passed

Description

78%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.

A strong description in third-person voice that clearly states both the capability and explicit 'Use when' triggers with concrete, natural phrases. Its main weaknesses are a single-action 'what' statement and one overly broad trigger ('optimizing query performance') that could conflict with general performance-tuning skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Command Query Responsibility Segregation') with one concrete action ('Implement'), but the 'Use when' clause lists trigger scenarios rather than additional capabilities, so coverage of concrete actions is not comprehensive.	3 / 5
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') with three concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('separating read and write models', 'optimizing query performance', 'event-sourced systems'), but misses common variations such as 'event sourcing', 'projections', or 'read/write side'.	4 / 5
Distinctiveness Conflict Risk	CQRS is a distinct niche with clear triggers, but 'optimizing query performance' is broad enough to overlap with general database- or query-performance skills, presenting minor conflict risk.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Path: .agent/skills/cqrs-implementation/SKILL.md
Revision: c4a059b

Reviewed: 15 days ago

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.

cqrs-implementation

Table of Contents

Is this your skill?