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.

Quality

48%

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 ./skills/projection-patterns/SKILL.md

The canonical home for this skill is projection-patterns in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a placeholder with no actionable content. It describes the domain (projection patterns for event-sourced systems) but provides zero concrete guidance—no code examples, no specific patterns, no commands, and no real workflow. All substance is deferred to a referenced file that doesn't exist in the bundle, making the skill non-functional.

Suggestions

Add at least one concrete, executable code example showing a basic projection/read model implementation (e.g., an event handler that updates a materialized view).

Replace the generic instruction bullets ('Apply relevant best practices') with specific, actionable steps for building a projection, including event subscription, state mutation, and idempotency handling.

Define a clear workflow with validation checkpoints, e.g.: 1) Define read model schema, 2) Implement event handlers, 3) Replay events to build initial state, 4) Verify projection accuracy against source events.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns so the skill is self-contained enough to be useful.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add some value but the 'Do not use' section is trivially obvious. The Instructions section is entirely generic boilerplate ('Clarify goals, constraints, and required inputs') that could apply to any skill and wastes tokens.	3 / 5
Actionability	The skill provides zero concrete guidance—no code, no commands, no specific patterns, no examples. The instructions are entirely vague ('Apply relevant best practices and validate outcomes') and delegate everything to a referenced file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes with no sequencing, no validation checkpoints, and no specifics about how to actually build projections or read models.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable disclosure strategy, but no bundle files are provided so the reference is unverifiable and potentially broken. The SKILL.md itself contains almost no substantive content to serve as an overview, making the disclosure structure hollow.	2 / 5
	Total	7 / 20 Passed

Description

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

This is a solid skill description that clearly communicates its purpose and when to use it. The 'Use when' clause with three concrete scenarios is well-constructed. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating projection handlers, creating database schemas for read stores, handling idempotency).

Suggestions

Expand the 'what' clause with more specific actions, e.g., 'Build read models and projections from event streams, generate projection handlers, create denormalized query stores, and handle rebuild/replay logic.'

Dimension	Reasoning	Score
Specificity	Names the domain (CQRS/event sourcing) and mentions concrete concepts like 'read models', 'projections', and 'event streams', but doesn't list specific actions beyond 'build'. Missing details like what kinds of projections, what databases, or what specific operations are supported.	3 / 5
Completeness	Clearly answers both 'what' (build read models and projections from event streams) and 'when' (implementing CQRS read sides, building materialized views, optimizing query performance in event-sourced systems) with an explicit 'Use when' clause containing concrete trigger scenarios.	5 / 5
Trigger Term Quality	Includes strong domain-specific trigger terms like 'read models', 'projections', 'event streams', 'CQRS', 'materialized views', 'query performance', and 'event-sourced systems'. These are natural terms a developer would use. Missing some synonyms like 'denormalized views', 'read store', 'query side', or 'event handlers'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on the read/query side of CQRS and event sourcing. Could have minor overlap with a general event sourcing skill or a CQRS command-side skill, but the specific focus on read models, projections, and materialized views narrows the scope well.	4 / 5
	Total	16 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/projection-patterns/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

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.