XPR NFT (AtomicAssets)
v0.2.11Manage the full AtomicAssets NFT lifecycle on XPR Network including creation, minting, selling, auctioning, transferring, and burning NFTs.
⭐ 0· 546·0 current·0 all-time
by@paulgnz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Functionality (create/mint/transfer/burn NFTs on XPR) matches the skill name and description. Requiring a private key, account, and RPC endpoint for write operations is expected for signing transactions. However, the skill.json declares no required env vars while the implementation demands XPR_PRIVATE_KEY, XPR_ACCOUNT, and XPR_RPC_ENDPOINT at runtime — an inconsistency between claimed requirements and actual needs.
Instruction Scope
SKILL.md stays within NFT lifecycle responsibilities (create templates, mint, list, auction, transfer, burn) and calls out IPFS usage and safety rules (e.g., avoid A2A messages). It instructs auto-transfer on delivery and to always mint to the agent's own account first — these are within scope. The doc does not ask the agent to read unrelated files or exfiltrate data.
Install Mechanism
There is no install spec (instruction-only), reducing install-time risk. However, the runtime code dynamically imports '@proton/js' for signing; dependencies are not declared in metadata. That means the runtime environment must provide this package or the skill will fail, and it's unclear what node packages will be required when this skill is loaded.
Credentials
The source code requires sensitive env vars (XPR_PRIVATE_KEY, XPR_ACCOUNT, XPR_RPC_ENDPOINT) for write operations. These are proportionate to NFT signing/transactions, but the skill's manifest (skill.json) lists no required env vars and SKILL.md does not document them — creating a mismatch that could cause users to accidentally provide secrets without proper warning. No alternative signing options (e.g., external signer or ephemeral keys) are documented.
Persistence & Privilege
The skill does not request always:true and is user-invocable only; it doesn't modify other skills or system-wide settings based on the provided files. Autonomous invocation is allowed (platform default) but not combined with any other high privilege here.
What to consider before installing
This skill implements expected NFT operations and legitimately needs a signing key and account to perform writes — but it fails to declare those requirements in its manifest or document them clearly. Before installing or providing credentials: (1) Ask the author to update skill.json and SKILL.md to list required env vars (XPR_PRIVATE_KEY, XPR_ACCOUNT, XPR_RPC_ENDPOINT) and explain the required permission level. (2) Prefer using a restricted or ephemeral key (and least-privilege permission) or an external signing service/hardware key rather than a long-lived private key in environment variables. (3) Verify the runtime will provide the '@proton/js' dependency or bundle it from a trusted source. (4) For production use, review the full src/index.ts to ensure there are no hidden endpoints or unexpected network calls and test initially on testnet with non-sensitive keys. If the author cannot justify the missing metadata and dependency documentation, treat the skill as untrusted and do not supply your private key.Like a lobster shell, security has layers — review code before you run it.
atomicassetsvk97fe68tjd4gncpyz1axfnee75813ta2blockchainvk97fe68tjd4gncpyz1axfnee75813ta2latestvk97fe68tjd4gncpyz1axfnee75813ta2nftvk97fe68tjd4gncpyz1axfnee75813ta2xprvk97fe68tjd4gncpyz1axfnee75813ta2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.