iii-event-driven-cqrs
Implements CQRS with event sourcing on the iii engine. Use when building command/query separation, event-sourced systems, or fan-out architectures where commands publish domain events and multiple read model projections subscribe independently.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-event-driven-cqrs/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies its niche (CQRS + event sourcing on a specific engine) and includes an explicit 'Use when' clause with good trigger terms. Its main weakness is that it describes the architectural pattern rather than listing concrete actions the skill performs (e.g., creating command handlers, setting up event stores, building projections). Adding more specific action verbs would improve specificity.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates command handlers, configures event stores, builds read model projections, and sets up event subscription pipelines.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CQRS, event sourcing, iii engine) and describes the architectural pattern at a high level, but doesn't list multiple concrete actions like 'create command handlers, build read model projections, configure event stores'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implements CQRS with event sourcing on the iii engine) and 'when' (explicit 'Use when' clause covering command/query separation, event-sourced systems, and fan-out architectures with specific elaboration). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'CQRS', 'event sourcing', 'command/query separation', 'fan-out architectures', 'domain events', 'read model projections'. These are terms a developer would naturally use when requesting this kind of system. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of CQRS, event sourcing, and the 'iii engine' platform. The niche architectural pattern and platform-specific scope make conflicts with other skills very unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with good progressive disclosure and a clear architectural overview. Its main weaknesses are the lack of inline executable code (relying entirely on an external reference) and missing validation/error-handling steps in the workflow. Some content is redundant (repeated boundary sections) and explains concepts Claude already understands.
Suggestions
Add at least one inline, executable code snippet showing a minimal command function that validates, appends an event, and publishes — don't rely solely on the external reference file.
Include explicit validation checkpoints in the workflow (e.g., what to do if state::set fails, how to handle publish errors, event ordering conflicts).
Consolidate the 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single section to eliminate redundancy.
Remove or minimize the 'Key Concepts' explanations of CQRS fundamentals (write side, read side, event log) — Claude already knows these; focus on iii-specific details only.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom largely repeat what 'Pattern Boundaries' already covers. The 'Key Concepts' section explains CQRS basics (write side, read side, event log) that Claude already knows. Some tightening is possible. | 2 / 3 |
Actionability | Provides a useful primitives table and common patterns with specific function signatures, but the actual executable code lives entirely in an external reference file. The skill body itself contains no copy-paste-ready code blocks — only an architecture diagram in text and API call snippets as bullet points, not runnable examples. | 2 / 3 |
Workflow Clarity | The ASCII architecture diagram clearly shows the flow from command to event to projections, and the common patterns section lists the sequence of operations. However, there are no explicit validation checkpoints or error-handling feedback loops for what is a multi-step process involving state mutations and event publishing. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Key Concepts, Architecture, Primitives, Reference Implementation, Common Patterns, Adapting, Boundaries). The full implementation is appropriately delegated to a single reference file with a clear link, keeping the skill as an overview — exactly one level deep. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- iii-hq/iii
- Commit
8921efa
- 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.