NEXUS Data Validation
v1.1.0Intelligent data quality checks and schema validation
⭐ 0· 260·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (data quality + schema validation) matches the SKILL.md and README: the skill forwards input to an external NEXUS data-validation API. The declared requirement (a payment-proof credential) aligns with the documented paywalled API behavior. Nothing required (binaries/config paths) is unrelated to the stated purpose.
Instruction Scope
The SKILL.md instructs the agent to POST inputs to a remote endpoint and to follow several payment flows (x402, MPP, legacy X-Payment-Proof). It does not direct filesystem access or shell execution. It does require contacting third-party endpoints (ai-service-hub-15.emergent.host) and, in the Stellar sponsorship flow, posting signed XDRs — which could reveal transaction details. These network actions are consistent with a paid external API but mean your data (and potentially payment metadata) will leave the agent.
Install Mechanism
No install spec and no code files — this is instruction-only. That minimizes local write/execution risk. There is no downloading of arbitrary archives or external installers.
Credentials
The skill requires a single environment variable: NEXUS_PAYMENT_PROOF (declared as primaryEnv). That is proportionate for a paywalled API. However, this value is a sensitive payment credential; users should ensure they do not store private keys or account secrets there. The SKILL.md also encourages posting signed Stellar XDRs to a sponsor endpoint — this is not expressed as an env var requirement but is sensitive operationally.
Persistence & Privilege
always is false and the skill is user-invocable; disable-model-invocation is false (normal). The skill does not request persistent installation-wide privileges or attempt to modify other skills or system config. Note: because the agent may invoke the skill autonomously, it could make paid requests if triggered — ensure you control invocation policies if unwanted charges are a concern.
Assessment
This skill is a thin wrapper around a paid third-party API (ai-service-hub-15.emergent.host). Before installing: 1) Confirm you trust that domain and review its documentation. 2) Use the sandbox_test mode to verify behavior without payment. 3) Treat NEXUS_PAYMENT_PROOF as a secret — do not place private keys or wallet seeds there. 4) Be cautious about submitting signed Stellar XDRs to the sponsor endpoint (they may reveal transaction metadata). 5) If you want to avoid accidental charges, restrict autonomous invocation or require manual approval for any payment flow. If any of the above is unacceptable or the service/provider is unfamiliar, do not install.Like a lobster shell, security has layers — review code before you run it.
aivk978pyf5mc67qzb0mm6gkzgne584gbzfcardanovk978pyf5mc67qzb0mm6gkzgne584gbzflatestvk978pyf5mc67qzb0mm6gkzgne584gbzfstellarvk978pyf5mc67qzb0mm6gkzgne584gbzfx402vk978pyf5mc67qzb0mm6gkzgne584gbzf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⚡ Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF