Skills cqrs-implementation
📦

cqrs-implementation

Content revision r2 Safe 🌐 Network access⚙️ External commands

Implement Reliable CQRS Architectures

Complex systems often mix writes and reads, limiting scalability and clarity. This skill guides separate models, projections, synchronization, and consistency decisions.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "cqrs-implementation" from https://skillstore.io/skills/sickn33-cqrs-implementation.md and its manifest at https://skillstore.io/api/skills/sickn33-cqrs-implementation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-cqrs-implementation.md Signed manifest GET /api/skills/sickn33-cqrs-implementation/manifest Signed lockfile GET /api/skills/sickn33-cqrs-implementation/lockfile

Test it

Using "cqrs-implementation". Design CQRS boundaries for an order service with heavy customer reporting.

Expected outcome:

  • Commands: create order, add item, and cancel order.
  • Queries: retrieve an order, list customer orders, and search orders.
  • Read model: denormalized order views optimized for reporting.
  • Consistency: asynchronous projections with defined lag and checkpoint monitoring.

Using "cqrs-implementation". Review a projection that can restart after processing failures.

Expected outcome:

Track durable checkpoints, make event application idempotent, retry transient failures, isolate invalid events, and test full projection rebuilds.

Using "cqrs-implementation". Decide whether a simple inventory tool needs CQRS.

Expected outcome:

Keep a conventional CRUD design when workloads are modest, models are similar, and immediate consistency is required throughout.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All 12 static findings are false positives caused by database client methods, ordinary identifiers, UUID generation, and Markdown code formatting. No malicious intent, prompt injection, external command execution, or network request was found.

2
Files scanned
585
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

🌐 Network access (1)
resources/implementation-playbook.md:269
⚙️ External commands (2)
SKILL.md:34 SKILL.md:38
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-cqrs-implementation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-cqrs-implementation/security.svg)](https://skillstore.io/skills/sickn33-cqrs-implementation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-cqrs-implementation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-cqrs-implementation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-cqrs-implementation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). cqrs-implementation security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-cqrs-implementation/audits/5

BibTeX citation

@techreport{sickn33-sickn33-cqrs-implementation-2026, author = {sickn33}, title = {cqrs-implementation security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-cqrs-implementation/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "cqrs-implementation security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-cqrs-implementation/audits/5" identifiers: - type: other value: "skillstore:sickn33-cqrs-implementation:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
wshobson Recommended

wshobson-cqrs-implementation

Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated

2026-08-21

sickn33 Current

sickn33-cqrs-implementation

Skillstore Score 78
Evidence Confidence High
Skillstore usage 9
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Separate a Growing Service

Map an existing service into commands, queries, handlers, and independently optimized data models.

Plan Scalable Read Models

Design projections, checkpoints, pagination, and synchronization for workloads with heavy reporting demand.

Review Consistency Tradeoffs

Define acceptable projection lag, read-your-writes behavior, rebuild procedures, and failure handling.

Try These Prompts

Identify CQRS Boundaries 
Review this application description: [description]. Identify commands, queries, handlers, and read models. Explain whether CQRS is justified.
Design a CQRS Feature 
Design a CQRS flow for [feature]. Include command validation, emitted events, query models, projection updates, and consistency expectations.
Adapt the Implementation Templates 
Adapt the CQRS patterns to [language and framework]. Preserve parameterized queries, handler boundaries, projection checkpoints, and explicit failure behavior.
Audit a Production CQRS Design 
Review this CQRS design: [design]. Assess idempotency, ordering, retries, projection rebuilds, schema evolution, observability, consistency targets, and recovery risks.

Best Practices

  • Define consistency targets and acceptable projection lag before implementation.
  • Keep command validation, event persistence, and query retrieval responsibilities explicit.
  • Test projection idempotency, checkpoint recovery, and complete rebuild procedures.

Avoid

  • Do not introduce separate models when simple CRUD meets the requirements.
  • Do not share persistence schemas tightly between command and query paths.
  • Do not ignore ordering, retries, duplicate events, or stale read behavior.

Frequently Asked Questions

What does this skill help implement?
It guides command and query separation, handler design, read model projections, synchronization, and consistency handling.
Does this skill require event sourcing?
No. CQRS can use conventional persistence, although the playbook includes event-driven patterns.
Which technology stack does it demonstrate?
The detailed examples use Python, asynchronous database access, and FastAPI.
When should CQRS be avoided?
Avoid it when CRUD is sufficient, separate models are impractical, or immediate consistency is required everywhere.
Does it generate production-ready infrastructure?
No. Teams must choose infrastructure, complete integrations, and validate performance and recovery in their environment.
How does it address eventual consistency?
It covers projection checkpoints, synchronization loops, rebuilds, expected versions, timeouts, and stale-data warnings.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/cqrs-implementation

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads · 127 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md