legacy modernization
v1.0.0Comprehensive legacy system modernization from assessment and strategy to monolith decomposition and cloud migration for any tech stack and scale.
⭐ 0· 455·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (legacy modernization methodology) matches the provided materials (assessment templates, decision matrices, strangler-fig guidance). The skill requests no binaries, env vars, or filesystem paths, which is proportionate for a guidance-only skill. Minor provenance note: the owner ID and source are unknown and no homepage is provided, so trust of the publisher cannot be independently verified.
Instruction Scope
SKILL.md is a detailed step-by-step methodology with YAML templates, decision trees, and migration patterns. It does not instruct the agent to read system files, access environment variables, or send data to external endpoints other than optional informational links. It expects user-provided inputs (system attributes, inventories) which is appropriate for an advisory skill.
Install Mechanism
No install spec and no code files are included — this is instruction-only. That minimizes on-disk risk and there are no download URLs or packages to evaluate.
Credentials
The registry metadata and SKILL.md declare no required credentials, env vars, or config paths. Nothing in the content demands unrelated secrets or elevated access.
Persistence & Privilege
always:false and the default model-invocation behavior applies. The skill does not request permanent presence or modify other skills. Because it is instruction-only and requires user input, it has limited autonomous impact.
Assessment
This skill is a methodology pack (no code) and looks internally consistent. Consider these practical precautions before use: (1) provenance — the owner and homepage are not provided; only install if you trust the source. (2) Do not paste secrets, credentials, or PII into the agent when answering assessment prompts — the skill may ask for architecture or code samples to analyze. (3) If you plan to grant the agent repo or cloud access to perform assessments, review and limit those permissions first (use read-only scopes, short-lived tokens). (4) The README links to paid 'context packs' hosted on an external site — be cautious before following external purchase links. Overall the skill itself does not request extra privileges, but follow standard hygiene around sharing sensitive artifacts and verifying publisher trust.Like a lobster shell, security has layers — review code before you run it.
latestvk9799rppvv1hx3h79q3zyhm40581fveelegacy-modernizationvk9799rppvv1hx3h79q3zyhm40581fvee
License
MIT-0
Free to use, modify, and redistribute. No attribution required.