Microservice Patterns
v1.0.0Provides guidance and patterns for decomposing monoliths, inter-service communication, data management, and resilience in microservice architectures.
⭐ 2· 984·1 current·1 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, README, and SKILL.md all describe microservice design patterns and include illustrative code samples; there are no required binaries, env vars, or other resources that are inconsistent with that purpose.
Instruction Scope
SKILL.md provides architecture guidance and sample code (Python snippets for HTTP clients, Kafka producer, sagas, etc.). It does not instruct the agent to read system files, access secrets, call external endpoints at runtime, or exfiltrate data. Code examples reference service URLs and bootstrap servers only as illustrative placeholders.
Install Mechanism
There is no formal install spec in the registry (lowest risk). README includes example commands (an npx add pointing to a GitHub tree and cp into local skill folders). Those are documentation examples — they are not executed by the platform — but as with any copy/paste install command, users should exercise typical caution before running npx or copying from an unknown source.
Credentials
The skill declares no required environment variables or credentials. Some code examples would, in real deployments, need configuration (e.g., Kafka bootstrap servers, service URLs) — but those are illustrative and do not appear in the skill as required secrets.
Persistence & Privilege
The skill is not always-enabled and does not request system or cross-skill configuration changes. It is instruction-only and does not request persistent privileges.
Assessment
This skill appears to be a documentation/cheatsheet for microservice patterns and is internally consistent. Before installing or running any commands shown in the README: (1) verify the skill source/owner (there's no homepage and the owner ID is unfamiliar), (2) don't run the example npx/cp commands unless you trust the remote repository, (3) treat code snippets as examples — they reference external services (Kafka, service URLs) and will need proper credentials/config if you copy them into a real project, and (4) review any copied code for network calls or credential use before executing. If you want extra assurance, ask the author for a homepage/repo link or run the snippets in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97e50qjq2vfbmrsj03s75nkyd80wmf6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.