ClawHub

NEXUS Schema-Aware SQL Generator

v1.0.3

Schema-aware natural language database querying. Provide your CREATE TABLE definitions, ask questions in English, get executable SQL with JOINs, aggregations...

⭐ 0· 229·1 current·1 all-time
by@cyberforexblockchain
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
The name/description (schema-aware text-to-SQL) match the SKILL.md and the single required env var (NEXUS_PAYMENT_PROOF) which is used as the payment/proof header shown in the examples. No unrelated binaries, files, or credentials are requested.
ℹ
Instruction Scope
Runtime instructions explicitly POST the provided schema and question to https://ai-service-hub-15.emergent.host. That behavior is consistent with the stated purpose but means any schema/question (potentially sensitive) is transmitted off-host. The skill claims no storage, but there is no way to verify that from the instruction-only package.
✓
Install Mechanism
There is no install spec and no code files; this is instruction-only and does not write code to disk. That reduces supply-chain risk compared with arbitrary downloads.
✓
Credentials
Only a single credential-like env var (NEXUS_PAYMENT_PROOF) is required and declared as the primary credential, which maps to the X-Payment-Proof header the service example uses. No unrelated secrets or multiple credentials are requested.
✓
Persistence & Privilege
The skill is not always-enabled, does not request filesystem or shell access, and is network-capable only as needed. It does not request elevated or persistent platform privileges.
Assessment
This skill will send whatever schema text and question you provide to an external service (ai-service-hub-15.emergent.host) and requires a payment-proof secret (NEXUS_PAYMENT_PROOF) to be set. Before installing: (1) verify you trust the external provider and their privacy/retention policy (the package has no homepage/source code to audit), (2) do not include database credentials, PII, or connection strings in the schema input — sanitize or anonymize schemas, (3) treat NEXUS_PAYMENT_PROOF like a secret and ensure it’s stored safely, and (4) consider running an on-prem or self-hosted text-to-SQL alternative if you cannot send schemas off-site. Additional useful information that would raise confidence: a published homepage or source repository, a clear privacy/data-retention policy, or example responses showing that no logs are retained.

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

aivk97a83nrvx3arkpfkqtr4vh9bh82xhe9cardanovk97a83nrvx3arkpfkqtr4vh9bh82xhe9databasevk97a83nrvx3arkpfkqtr4vh9bh82xhe9latestvk97a83nrvx3arkpfkqtr4vh9bh82xhe9sqlvk97a83nrvx3arkpfkqtr4vh9bh82xhe9

License

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

Runtime requirements

\u26a1 Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF

Comments