Kansodata Databricks
v0.1.1Execute conservative read-only Databricks SQL through the Databricks plugin and provide safe planning output for unsupported workflows.
⭐ 1· 112·0 current·0 all-time
byMarcos CF.@kansodata
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (read-only Databricks SQL and planning) match the SKILL.md: it enumerates supported statement shapes, read-only policy, and required inputs (workspace URL, warehouse id, catalog/schema, target tables). Nothing requested (binaries, env vars, or installs) appears extraneous to a read-only SQL helper.
Instruction Scope
SKILL.md limits runtime actions to a specific runtime tool (databricks_sql_readonly), enforces read-only and single-statement constraints, and instructs planning output for unsupported requests. It does not instruct reading unrelated files, environment variables, or transmitting data to external endpoints.
Install Mechanism
No install spec and no code files — this is instruction-only, which minimizes on-disk risk. The skill assumes a runtime tool (databricks_sql_readonly) is available from the platform rather than installing anything itself.
Credentials
The skill declares the logical inputs it needs (workspace URL, environment, SQL warehouse id, catalog/schema, target tables) and requests no environment variables or credentials. This is proportionate for a description-level skill, but in practice executing Databricks SQL requires authentication; the skill relies on the platform's connector/tool to provide credentials. Verify that the platform plugin supplies least-privilege credentials rather than the skill asking for broad secrets.
Persistence & Privilege
always:false and default autonomous invocation are appropriate. The skill does not request persistent system modifications or global config changes.
Assessment
This skill appears coherent and low-risk as an instruction-only, read-only Databricks helper. Before installing: confirm your agent runtime actually provides the referenced databricks_sql_readonly tool and that it will supply authentication (the skill itself doesn't ask for credentials); ensure the platform's Databricks connector is configured with least-privilege, read-only access and auditing enabled; and test the skill in a non-production environment to verify the stated multi-statement/mutation protections and any catalog/schema allowlists behave as documented.Like a lobster shell, security has layers — review code before you run it.
databricksvk9738zbxjazq08azaeredhg0rd84gr8nlatestvk9738zbxjazq08azaeredhg0rd84gr8nopenclawvk9738zbxjazq08azaeredhg0rd84gr8nreadonlyvk9738zbxjazq08azaeredhg0rd84gr8nsqlvk9738zbxjazq08azaeredhg0rd84gr8n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.