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.
60
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 + event sourcing on a specific engine) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capabilities described stay at the architectural pattern level rather than listing concrete, granular actions the skill performs.
Suggestions
Add more specific concrete actions such as 'create event stores', 'build read model projections', 'replay event streams', or 'define command handlers' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (CQRS, event sourcing) and mentions some actions like command/query separation, publishing domain events, and read model projections subscribing. However, it doesn't list multiple concrete actions (e.g., 'create event stores', 'build projections', 'replay events') — it stays more at the architectural pattern level. | 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, fan-out architectures with domain events and projections). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'CQRS', 'event sourcing', 'command/query separation', 'event-sourced systems', 'fan-out architectures', 'domain events', 'read model projections'. These are terms a user working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of CQRS, event sourcing, the 'iii engine' platform, and fan-out architecture creates a very specific niche that is 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 with event sourcing on the iii engine, with a clear diagram and useful primitive mapping table. However, it lacks inline executable code (deferring entirely to an unverifiable reference file), has redundant sections, and misses validation/error-recovery workflows that are important for event-sourced systems. The content would benefit from a concrete inline example and consolidation of repeated boundary/usage guidance.
Suggestions
Add a minimal but complete inline code example showing a command publishing an event and a projection subscribing to it, rather than relying solely on the external reference file.
Add explicit error handling and validation workflow steps — e.g., what happens when event publishing fails, how to handle projection replay, or how to verify event log consistency.
Consolidate the 'Pattern Boundaries', 'When to Use', and 'Boundaries' sections into a single section to reduce redundancy and save tokens.
Remove or minimize explanations of general CQRS/event sourcing concepts (Key Concepts section) that Claude already knows, focusing instead 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 largely repeat the 'Pattern Boundaries' section. The 'Key Concepts' section explains concepts like PubSub fan-out and CQRS that Claude already understands. Some tightening is possible. | 2 / 3 |
Actionability | The skill provides common code patterns (trigger calls, registerWorker, etc.) and an architecture diagram, but no complete executable code inline — it defers to a reference file. The 'Common Patterns' section shows API call signatures but not a runnable example. The reference file is not provided in the bundle, so actionability depends on an external file we can't verify. | 2 / 3 |
Workflow Clarity | The architecture diagram shows the flow clearly, 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 get out of sync — important for event-sourced systems. | 2 / 3 |
Progressive Disclosure | The skill references a full implementation file at '../references/event-driven-cqrs.js', which is good progressive disclosure structure. However, no bundle files were provided, so we can't verify the reference exists. The inline content is reasonably organized with clear sections, but the redundant 'When to Use' / 'Boundaries' sections at the end could be consolidated. | 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
a7ebbbb
- 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.