Data Engineering
v1.0.0Design and operate scalable data pipelines and architectures using best-fit patterns, tools, and modeling methodologies without external dependencies.
⭐ 0· 665·4 current·4 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 (data engineering guidance and patterns) aligns with the provided SKILL.md and README content. The skill is purely advisory (templates, decision matrices, runbooks) and does not require unrelated credentials, binaries, or config paths.
Instruction Scope
SKILL.md is a large methodology and template document. The visible content stays within advisory/design scope (architecture, tooling choices, modeling templates). There is no instruction to read system files, exfiltrate data, or call external endpoints. Caveat: if you use the skill to perform live operations, the agent or user will need to supply external credentials (not declared here) — the skill itself does not provide or request those.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes on-disk persistence and arbitrary code execution risk.
Credentials
The skill declares no required environment variables, credentials, or config paths, which is proportionate for a purely advisory methodology pack. The README links to external paid 'context packs' (external URLs), but those are optional marketing links and not required by the skill.
Persistence & Privilege
always is false and the skill is user-invocable. The skill does not request persistent privileges or modify other skills. Autonomous invocation is allowed by default but does not by itself increase risk here because the skill has no code and no declared secrets.
Assessment
This skill appears to be an advisory methodology pack (decision matrices, templates, runbooks) and is internally consistent with that purpose. Because it is instruction-only and requires no environment variables, it cannot by itself access your systems or secrets. However, if you or an autonomous agent follow its guidance to implement pipelines, you will inevitably need to provide external credentials (databases, cloud providers, warehouses). Do not paste secrets or credentials into chat — instead use the platform's secure credential mechanisms. Also note the README links to external paid 'context packs' hosted on a third-party site; those are optional and external. If you intend to let an agent act on your behalf (provision resources, run migrations, or connect to production systems), restrict autonomous invocation or review every action before execution.Like a lobster shell, security has layers — review code before you run it.
analyticsvk97b4n8n1knxmg0z6saxptzrpn81c669datavk97b4n8n1knxmg0z6saxptzrpn81c669engineeringvk97b4n8n1knxmg0z6saxptzrpn81c669etlvk97b4n8n1knxmg0z6saxptzrpn81c669latestvk97b4n8n1knxmg0z6saxptzrpn81c669pipelinevk97b4n8n1knxmg0z6saxptzrpn81c669
License
MIT-0
Free to use, modify, and redistribute. No attribution required.