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.
76
70%
Does it follow best practices?
Impact
—
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 with event sourcing on the iii engine) and provides an explicit 'Use when' clause with relevant trigger scenarios. The trigger terms are well-chosen for the target audience of developers building event-sourced systems. The main weakness is that the specificity of concrete actions could be improved by listing more discrete operations the skill performs.
Suggestions
Add more specific concrete actions such as 'define aggregates, replay event streams, build read model projections, handle command validation' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CQRS, event sourcing) and mentions some actions like 'commands publish domain events' and 'read model projections subscribe independently,' but doesn't list multiple concrete actions like creating projections, replaying events, building read models, etc. | 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 trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a user would say: 'CQRS', 'event sourcing', 'command/query separation', 'fan-out architectures', 'domain events', 'read model projections'. These cover the main variations a developer would use when requesting this kind of system. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: CQRS + event sourcing on a specific engine ('iii engine'). The combination of architectural pattern and platform makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a solid architectural overview of CQRS/event sourcing on the iii engine with a useful ASCII flow diagram and clear primitive mapping. However, it lacks inline executable code examples (relying on an unverifiable external reference), includes some redundant sections (duplicate boundary/usage guidance), and misses explicit error handling and validation workflows that would be important for event-sourced systems.
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.
Consolidate the 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single section to eliminate redundancy.
Add explicit error handling guidance: what happens when event publishing fails, how to handle projection errors, and whether/how to implement retry logic.
Remove explanations of CQRS concepts (write side, read side, event log) that Claude already understands — focus on iii-specific implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat information already conveyed in 'Pattern Boundaries'. The 'Key Concepts' section explains CQRS basics that Claude already knows (what write side/read side means). Some tightening is possible. | 2 / 3 |
Actionability | The skill provides common patterns with specific function signatures and a clear architecture diagram, but lacks inline executable code. It relies on an external reference file for the full working example, and the 'Common Patterns' section shows API calls in isolation without a cohesive, copy-paste-ready code block. | 2 / 3 |
Workflow Clarity | The architecture diagram clearly shows the flow from command to event to projections, and the 'Adapting This Pattern' section mentions validation before publishing. However, there are no explicit validation checkpoints, error recovery steps, or feedback loops for what to do when event publishing fails or projections encounter errors. | 2 / 3 |
Progressive Disclosure | The skill references a detailed implementation file (../references/event-driven-cqrs.js) which is good progressive disclosure, but no bundle files were provided to verify the reference exists. The content itself is reasonably structured with clear sections, but the inline content could be trimmed with more offloaded to reference files. | 2 / 3 |
Total | 8 / 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
d51a06d
- 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.