ClawHub

Kansodata Databricks Authoring

v0.1.1

Skill para generar y refactorizar SQL y notebooks Databricks como texto revisable, sin ejecución ni integración con APIs o persistencia.

⭐ 0· 67·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Databricks authoring-only) match the declared footprint: no binaries, no env vars, no install steps. All required capabilities are content generation/refactor and are plausible without external access.
✓
Instruction Scope
SKILL.md is detailed and bounds behavior tightly (no execution, no API calls, no persistence, degrade/reject when schema missing). It does not instruct reading system files, secrets, or contacting external endpoints.
✓
Install Mechanism
No install spec (instruction-only), so nothing is written to disk or downloaded. This is the lowest-risk option and is proportionate for an authoring skill.
✓
Credentials
The skill declares no environment variables, credentials, or config paths — appropriate for a purely authoring/refactor tool that explicitly avoids integration with Databricks APIs.
✓
Persistence & Privilege
always is false and the skill does not request special persistent presence or cross-skill configuration. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill appears coherent and low-risk because it only describes how to generate/refactor SQL and notebook source as text and explicitly forbids execution or API integration. Before installing, note two practical cautions: (1) provenance — the registry entry has no homepage and unknown source, so you should be comfortable installing instruction-only skills from this publisher; (2) content risk — outputs may contain sensitive column/table names if you provide them as input, and generated queries should always be reviewed by a human before execution to avoid logic bugs or high-cost queries. If you rely on supply-chain provenance, prefer skills with a verifiable homepage or published source repository.

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

latestvk976a6hddqpk6e7fd0mv1t126184pqp5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments