ClawHub

NEXUS document-extract

v1.0.1

Extract structured data (names, dates, amounts, entities) from unstructured text documents using AI. Returns clean JSON with extracted fields.

⭐ 0· 170·0 current·0 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
high confidence
✓
Purpose & Capability
Name and description (document extraction) match the instructions: the SKILL.md tells the agent to POST text to a document-extract API. Requiring a payment/proof token (NEXUS_PAYMENT_PROOF) as the primary credential is consistent with a paid API.
ℹ
Instruction Scope
Instructions limit operations to network calls (permissions: network=true, filesystem/shell=false) and explicitly direct requests to a single external endpoint. The skill transmits user-provided text to https://ai-service-hub-15.emergent.host; the doc claims no permanent storage but that is unverifiable from the skill alone. Do not assume privacy guarantees without reviewing the provider.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files. This minimizes local risk (nothing written to disk or executed locally by the skill itself).
ℹ
Credentials
Only one env var is required: NEXUS_PAYMENT_PROOF (primary credential). That aligns with the SKILL.md which requires an X-Payment-Proof header. The variable is sensitive (payment/proof token), so ensure it is stored and provided securely. No unrelated credentials are requested.
✓
Persistence & Privilege
always is false and the skill does not request elevated or persistent privileges. Autonomous invocation is allowed (platform default) but not combined with other privilege concerns.
Assessment
This skill appears coherent, but it will send any text you provide to an external service and requires a payment-proof token. Before installing: (1) Confirm you trust https://ai-service-hub-15.emergent.host and read its privacy/terms, (2) avoid submitting highly sensitive or regulated data unless you have explicit assurances, (3) store NEXUS_PAYMENT_PROOF securely (treat it like a secret) and use the sandbox_test value for non-sensitive testing, and (4) monitor and rotate the token if you suspect misuse. The skill has no local install footprint, so the main risk is data exposure to the remote API and misuse of the payment credential.

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

aivk97cq9aetxmn4e1dbp90hghead82tn11cardanovk97cq9aetxmn4e1dbp90hghead82tn11latestvk97cq9aetxmn4e1dbp90hghead82tn11

License

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

Runtime requirements

⚡ Clawdis
EnvNEXUS_PAYMENT_PROOF
Primary envNEXUS_PAYMENT_PROOF

Comments