NEXUS Error Explain

v1.1.0

Explain error messages and suggest fixes

0· 256·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (explain errors + suggest fixes) match the SKILL.md: the runtime instructions call an external NEXUS AI endpoint that performs the work. The declared primaryEnv (NEXUS_PAYMENT_PROOF) and payment-focused protocol details align with a paid third-party API.
Instruction Scope
Instructions are scoped to network calls to a single external host (https://ai-service-hub-15.emergent.host) and to supplying payment headers/proofs. The skill will send your input text to that service and expects a payment credential; this is expected for a paid, hosted AI API but means your inputs and the payment proof header are transmitted off-host.
Install Mechanism
No install spec or code is included (instruction-only). Nothing is written to disk or fetched at install time, which is the lowest-risk model and consistent with the skill's description.
Credentials
Only one required env var (NEXUS_PAYMENT_PROOF / primaryEnv) is declared and used in examples. That credential is directly relevant to the documented payment/proof flow. No unrelated credentials or filesystem paths are requested.
Persistence & Privilege
always is false and the skill does not request persistent or elevated system privileges. It does require network access in its protocol metadata (expected for a hosted API).
Assessment
This skill forwards any input you send to the external NEXUS service (https://ai-service-hub-15.emergent.host) and expects a payment proof credential. Only install if you trust that service. Treat NEXUS_PAYMENT_PROOF like a secret (store it in a secure agent vault, not in plain text). Try the sandbox mode (X-Payment-Proof: sandbox_test) first to verify behavior. Verify the endpoint URL and service terms on the provider site, and be aware that your inputs will be processed off-host and may be subject to their retention/usage policy.

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

aivk9792c00z2vvdb6ejtajwtasrh84hztjcardanovk9792c00z2vvdb6ejtajwtasrh84hztjlatestvk9792c00z2vvdb6ejtajwtasrh84hztjstellarvk9792c00z2vvdb6ejtajwtasrh84hztjx402vk9792c00z2vvdb6ejtajwtasrh84hztj

License

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

Runtime requirements

Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF

Comments