BB projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
The skill promises to help build read models and projections from event streams for CQRS systems and materialized views. The files contain 286 tokens of instructions with no scripts or code examples. Checks found no critical errors, linting is clean, quality score is 80 out of 100, but process score only 70.
The catch is that this skill exists as an approach description rather than a ready-to-use tool with templates or examples. CQRS requires concrete patterns—how to sync state, handle delays, revert projections. None of that here. Compatibility with multiple platforms (Claude, Cursor, Gemini, and others) suggests the skill is universal in form rather than useful in substance.
Install if you need a conceptual guide, not production-ready solutions. For real systems you'll need additional materials.
Build read models and projections from event streams.
As a process B 70/100 · Nearly there — weak spots: result and completion, failures and branches, progress reporting
The same skill appears in 1 more place: agentic-awesome-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 286 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 179: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 16 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.