Enterprise
v1.0.0Navigate enterprise software development with legacy integration, compliance requirements, stakeholder management, and architectural decisions at scale.
⭐ 0· 589·1 current·1 all-time
byIván@ivangdavila
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 (enterprise guidance on legacy, compliance, architecture) aligns with the provided files (SKILL.md, architecture.md, compliance.md, legacy.md). There are no unrelated env vars, binaries, or install steps required.
Instruction Scope
Runtime instructions are high-level design and process guidance (ADR templates, trade-offs, compliance checklists, integration patterns). They do not instruct the agent to read system files, exfiltrate data, call external endpoints, or access credentials. The guidance is advisory and could influence agent decisions, but it stays within the stated domain.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. The absence of required secrets is proportional to a documentation/decision-support skill.
Persistence & Privilege
always is false and the skill does not request elevated or persistent system privileges. It will not modify other skills or system configuration based on the provided materials.
Assessment
This skill is instruction-only and appears coherent with its stated purpose, but consider these practical checks before installing: 1) Provenance: the owner and homepage are unknown — prefer skills from known sources or review the files yourself. 2) Test in a sandbox: let the agent use the skill in a controlled environment first to observe how its heuristics affect decisions. 3) Monitor actions: because the guidance can influence agent behavior, watch for any agent actions that attempt to access systems or secrets (the skill itself doesn't request them). 4) Align with policy: verify the compliance guidance matches your organization’s legal/regulatory requirements before relying on it. 5) Update process: decide how you will track updates to this skill since there is no homepage or established update channel.Like a lobster shell, security has layers — review code before you run it.
latestvk974k2axe7egqdfyzsbmfnhman8190qd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🏢 Clawdis
OSLinux · macOS · Windows