Backend Event Stores
v1.0.0Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, implementing event persistence, projections, snapshotting, or CQRS patterns.
⭐ 0· 747·0 current·0 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content: SKILL.md and README contain architecture guidance, SQL schema, and example Python implementations for event stores. There are no unrelated binaries, credentials, or config paths requested that would be inconsistent with implementing event persistence, projections, and snapshotting.
Instruction Scope
Runtime instructions are design guidance and code examples (SQL, Python) scoped to event store tasks. The SKILL.md does not instruct the agent to read unrelated system files, harvest environment variables, or transmit data to unexpected endpoints. Example code would, if executed, interact with a database — which is expected for this purpose — but the skill itself does not instruct automatic execution or data exfiltration.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute. README suggests manual copy and an npx example pointing at a GitHub tree (documentation only). Because nothing is automatically downloaded or extracted by the skill, install risk is low.
Credentials
The skill declares no required environment variables, credentials, or config paths. Example code will need database connection details when used, but the skill does not demand or bake in any secrets itself.
Persistence & Privilege
Skill flags show default behavior (always: false, user-invocable: true). It does not request permanent presence or elevated platform privileges and does not modify other skills or system-wide settings.
Assessment
This skill is an offline guide and appears coherent with its stated purpose, but note: (1) provenance is unknown (no homepage and an owner ID only) — review content before trusting it; (2) code snippets (SQL, Python) are examples that will need real DB connection details if you execute them — never run example commands or npx installs from unknown sources without inspecting the code first; (3) README contains an npx add example referencing a GitHub tree — running npx/npm commands that fetch remote code can execute code on your machine, so only run them after verifying the repository and author. If you plan to use the provided snippets, review and test them in an isolated environment and ensure any DB credentials are provided securely.Like a lobster shell, security has layers — review code before you run it.
latestvk97atxvkrgrbhb2pmwe6b3zwch80x8py
License
MIT-0
Free to use, modify, and redistribute. No attribution required.