Etl
v2.0.1Build ETL pipelines with data ingestion, cleaning, and validation steps. Use when ingesting sources, transforming formats, validating data, or scheduling loads.
⭐ 0· 296·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
Name/description match what the code does: a lightweight CLI for recording ETL steps to per-command log files. No unexpected credentials, network access, or unrelated binaries are requested.
Instruction Scope
SKILL.md and the included script limit operations to logging and local exports under $HOME/.local/share/etl. Commands only read/write those files and use standard coreutils. Note: exported JSON/csv construction does not escape special characters in user-supplied values (could produce invalid output if entries contain quotes/newlines) and search uses grep with the raw term (behaves as a local search, not exfiltration).
Install Mechanism
Instruction-only skill with a bundled script; there is no remote download or install step. Nothing is fetched from arbitrary URLs and no archives are extracted.
Credentials
No required environment variables or credentials are declared. The script uses HOME to determine the data directory (expected). It does not read other environment secrets or external config paths.
Persistence & Privilege
Does not request permanent/always-on inclusion. It stores logs under ~/.local/share/etl (user-writable area) and does not modify other skills or global agent configuration.
Assessment
This skill appears to do exactly what it says: a local logger for ETL activity. Before installing or running: (1) Inspect the script and ensure you are comfortable placing/adding it to your PATH; (2) be aware all entries are stored as plain-text under ~/.local/share/etl — do not log secrets (API keys, passwords, sensitive data) into these files; (3) exported JSON/csv may be malformed if entries contain quotes or newlines — avoid logging raw sensitive payloads or sanitize inputs; (4) set appropriate filesystem permissions on the data directory if others share the machine; and (5) if you plan to automate (cron), ensure the cron environment and output handling meet your security needs.Like a lobster shell, security has layers — review code before you run it.
latestvk975mrf56a0dnx7dc7jk4r2f99835t6z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.