Monolith Modularization
v1.0.0Deep workflow for evolving monoliths—mapping domains, defining module seams, strangler patterns, data ownership, incremental extraction, and testing/deployme...
⭐ 0· 65·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: the file is a step-by-step workflow for mapping domains, defining module seams, migration patterns, and validation. There are no unrelated requested binaries, environment variables, or config paths.
Instruction Scope
The instructions are high-level process guidance (six stages, checklists, tooling suggestions) and do not instruct the agent to read system files, export secrets, or call external endpoints. Note: to actually execute this workflow an agent or user would typically need access to the code repository and CI configuration, but the skill itself does not request or assume those accesses.
Install Mechanism
No install spec and no code files—this is instruction-only, so nothing is written to disk or downloaded during install.
Credentials
The skill declares no environment variables, credentials, or config paths. There are no disproportionate or unexplained secret requests.
Persistence & Privilege
always is false and the skill does not request persistent presence or system-level modifications. Autonomous invocation is allowed by platform default but is not combined here with elevated privileges or broad credential access.
Assessment
This skill is a coherent, read-only set of best-practice instructions and does not itself request secrets or install code. Before using it in an automated agent, consider: (1) the guidance is high-level — if you want automation the agent will need repository and CI access, so grant only minimal, audited permissions; (2) any implementation that executes commands or modifies CI should be reviewed by an engineer to avoid accidental data exposure; (3) prefer manual review of proposed module boundaries and migration steps in sensitive systems; and (4) request the author or publisher information if you need provenance or compliance evidence (the skill's source/homepage is unknown). If you want stricter safeguards, do not allow autonomous agent runs against your codebase without human approval.Like a lobster shell, security has layers — review code before you run it.
latestvk9769r9fxe0j5jg1rfpeqvyva583kwtj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.