Skip to content
TrustedSkillsbeta
Back to all skills

Cqrs Implementation

Checked
wshobson·vlatest·backend·MIT

This skill provides a CQRS implementation for your application, enabling decoupled read and write models for improved scalability & performance.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill cqrs-implementation -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 544 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The CQRS (Command Query Responsibility Segregation) implementation skill enables AI agents to separate read and write operations in software systems, improving performance and scalability. It provides tools for designing domain models that handle commands and queries independently, making complex applications more maintainable.

When to use it

  • When building scalable web applications with high concurrency requirements.
  • In microservices architectures where data consistency is critical.
  • For legacy systems needing refactoring to improve separation of concerns.
  • When optimizing database performance through read/write isolation.

Key capabilities

  • Separation of command and query models for better scalability.
  • Support for event sourcing patterns in domain-driven design.
  • Integration with message queues for asynchronous processing.
  • Tools for maintaining data consistency across distributed systems.

Example prompts

  • "Implement a CQRS pattern for a user management system."
  • "Design a read model that aggregates user activity logs."
  • "Set up an event bus to handle command and query operations separately."

Tips & gotchas

  • Ensure your team is familiar with domain-driven design principles before using this skill.
  • Be mindful of increased complexity in debugging due to the separation of concerns.