NEXUS Sentiment Intelligence
v1.0.2Analyze text for emotional tone, opinion polarity, subjectivity, intensity, and specific emotions. Returns per-sentence breakdown with sarcasm detection, urg...
⭐ 0· 187·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the instructions: SKILL.md documents a POST to a NEXUS sentiment API that returns multi-dimensional sentiment analysis. There are no unrelated binaries, config paths, or extra credentials requested.
Instruction Scope
Instructions explicitly require network access and to POST the input text to https://ai-service-hub-15.emergent.host with an X-Payment-Proof header. That is coherent with the described purpose, but it means user-provided text (possibly sensitive) is transmitted to a third-party service; SKILL.md claims no filesystem/shell access and does not instruct reading other local files or env vars.
Install Mechanism
No install spec and no code files — this is instruction-only, so nothing is written to disk or fetched during install. This minimizes local install risk.
Credentials
Only one env var is required: NEXUS_PAYMENT_PROOF (declared as primary credential). Requiring a payment-proof token is proportionate to a pay-per-request service. Caveats: this token will be sent to the remote endpoint as X-Payment-Proof, so confirm the token's scope (should not be a private wallet key) and treat it as sensitive. SKILL.md uses placeholder names like <masumi_payment_id> and sandbox_test which are consistent enough but slightly inconsistent in naming.
Persistence & Privilege
always is false and the skill does not request persistent or system-wide privileges. It does not modify other skills or system config.
Assessment
This skill sends input text (the data you give it) to an external service at ai-service-hub-15.emergent.host and includes whatever value is in NEXUS_PAYMENT_PROOF as the X-Payment-Proof header. Before installing: (1) Confirm you are comfortable sending any text you pass to this skill to that third party—avoid sending PII, secrets, or proprietary content. (2) Verify what NEXUS_PAYMENT_PROOF actually is (a short per-request token is safer than a wallet/private-key) and limit its scope; don’t store a full Cardano wallet secret there. (3) Use the sandbox_test value and synthetic data first to confirm behavior. (4) Review the remote service’s privacy/security documentation and the emergent.host domain provenance; if unsure, rotate or revoke the token after testing. (5) Monitor network usage and logs for unexpected data exfiltration. These precautions reduce the main risk (remote data transmission) while the skill itself appears coherent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
aivk977nm2pq7p6q66wfhvrvsjxgh82vm7tcardanovk977nm2pq7p6q66wfhvrvsjxgh82vm7tlatestvk977nm2pq7p6q66wfhvrvsjxgh82vm7t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⚡ Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF
