Microservice Granularity Optimizer
v1.0.0Right-size microservice boundaries using granularity disintegrators (forces to split: service scope, code volatility, scalability, fault tolerance, security,...
⭐ 0· 59·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (microservice granularity optimization) match the SKILL.md: it asks for service boundaries, communication patterns, transaction needs, and codebase scans when available. Nothing requested (no env vars, no binaries, no installs) is out of scope for the declared purpose.
Instruction Scope
The runtime instructions are focused on architecture analysis: asking for service definitions, inter-service call patterns, transaction requirements, and—optionally—scanning repo artifacts (Docker/K8s configs, API gateway routes, directories). These file reads are appropriate for the stated task. The SKILL.md does not ask the agent to read unrelated secrets or system files, nor to exfiltrate data to external endpoints.
Install Mechanism
No install spec or code is provided (instruction-only). This minimizes risk; nothing will be downloaded or written to disk by an installer.
Credentials
The skill requires no environment variables, credentials, or config paths. It may read repository files if available (which is reasonable for codebase analysis) but does not request unrelated sensitive access.
Persistence & Privilege
always is false and the skill is user-invocable only. It does require Read/Write tools (so the agent can read project files and write recommendations), which is appropriate for an architecture analysis skill and does not elevate system-wide privileges.
Assessment
This skill is coherent and appears to do what it says: analyze service boundaries and recommend splits/merges and communication/transaction patterns. Before installing/use: ensure you understand that the agent may read your repository files (Docker/K8s manifests, source directories) if you provide them—don’t expose secrets or production credentials in the input. Review any recommendations before applying changes, and consider running the analysis on a sanitized or access-limited copy of your codebase. If you rely on other skills (component-identifier, architecture-style-selector), verify those skills' trustworthiness because this skill may reference or call them for preparatory work.Like a lobster shell, security has layers — review code before you run it.
architecturevk979vhn458vbq6a0yahzfn8m9n84pg3bbookforgevk979vhn458vbq6a0yahzfn8m9n84pg3bbounded-contextvk979vhn458vbq6a0yahzfn8m9n84pg3bchoreographyvk979vhn458vbq6a0yahzfn8m9n84pg3bdisintegratorsvk979vhn458vbq6a0yahzfn8m9n84pg3bdistributed-transactionsvk979vhn458vbq6a0yahzfn8m9n84pg3bgranularityvk979vhn458vbq6a0yahzfn8m9n84pg3bintegratorsvk979vhn458vbq6a0yahzfn8m9n84pg3blatestvk979vhn458vbq6a0yahzfn8m9n84pg3bmicroservicesvk979vhn458vbq6a0yahzfn8m9n84pg3borchestrationvk979vhn458vbq6a0yahzfn8m9n84pg3bsagavk979vhn458vbq6a0yahzfn8m9n84pg3bsoftware-architecturevk979vhn458vbq6a0yahzfn8m9n84pg3b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis