DataEngineering

v1.0.0

OpenClaw 数据建表规范与流程指导。当用户需要创建数据仓库表(DDL)时使用,支持 DWS/DWD/DIM/ADS 等层级,引导完成工作空间选择、表命名、字段定义、分区策略、生命周期等完整建表流程。

0· 191·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the SKILL.md provides step-by-step DDL/table-definition guidance (workspace, layer/domain, naming, fields, partitions, TTL, examples). Nothing requested (no env vars, no binaries, no installs) is out of proportion with a documentation/assistant skill. Note: the document prescribes a storage format 'STORED AS ALIORC', which is environment-specific and should be validated against your platform.
Instruction Scope
The instructions are narrowly scoped to collecting table metadata and producing SQL DDL templates; they do not instruct the agent to read local files, environment variables, credentials, or transmit data externally. They do include prescriptive defaults (storage format, TTLs) that may not apply universally—users should confirm these defaults for their environment.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is the lowest-risk install posture (nothing is written to disk or fetched).
Credentials
No environment variables, credentials, or config paths are requested. The lack of secrets or unrelated credentials is proportionate for a documentation/assistant skill.
Persistence & Privilege
always:false and user-invocable: true. The skill does not request persistent/system privileges or modify other skills/configuration.
Assessment
This skill appears to be purely advisory and safe to use, but before applying generated DDL in production: (1) verify that the storage format 'ALIORC' and any other platform-specific defaults exist in your environment, (2) do not paste sensitive PII or secrets into prompts when interacting with the skill, (3) validate naming/partitioning/TTL choices with your DBAs and compliance team, and (4) test generated DDL in a staging environment and ensure you have appropriate permissions to run DDL in the target workspace.

Like a lobster shell, security has layers — review code before you run it.

latestvk97832y28cqbcz6eps5yye10hs830zdk

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments