Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
HumanNFT
v1.0.0Browse, mint, buy, sell, and trade human NFTs on the HumanNFT marketplace (humannft.ai). Triggers on "human NFT", "mint human", "browse humans", "humannft",...
⭐ 0· 582·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (HumanNFT marketplace: browse, mint, buy, sell) aligns with the API endpoints in SKILL.md and the single declared env var (HUMANNFT_API_KEY). However the SKILL.md repeatedly requires wallet.signMessage and wallet.sendTransaction (i.e., access to a wallet or private key) for on-chain actions while the skill's metadata does not declare any wallet credential or private-key env var. The skill also states agents can act autonomously; without a declared signing credential this is inconsistent (either the agent must prompt a user to sign every tx, or the deployer would need to supply signing material that is not described).
Instruction Scope
The instructions instruct the agent to register agents (wallet signature), create transactions via POST → wallet.sendTransaction → confirm via API, and to register webhooks (/api/webhooks). All of these are within marketplace functionality, but: (1) wallet signing requires interactive user signing or access to a private key that the skill never requests; (2) registering webhooks allows exfiltration of events to arbitrary URLs if misused; (3) the guidance to 'always confirm' and to use /sync/reconcile shows the skill expects the agent to perform state-changing operations, which magnifies the impact of any missing controls. The SKILL.md does not instruct reading unrelated system files or env vars, which is good.
Install Mechanism
There is no install spec (instruction-only), so nothing is written to disk by the skill itself. The docs recommend an npm helper (npx humannft-mcp) for MCP-enabled platforms — this is optional, but running arbitrary npx packages can pull and execute third-party code and should be reviewed before use.
Credentials
The skill declares a single required env var HUMANNFT_API_KEY, which is reasonable for an API-backed marketplace. However, the runtime flow requires signing transactions (wallet access). The skill does not declare any wallet-related env (e.g., PRIVATE_KEY, WALLET_KEY) or explain how signing will be provided in an autonomous agent context. This mismatch can lead to risky ad-hoc behavior (users or operators might supply private keys outside the declared requirements). Also, the example API key format sk_live_... implies a long-lived secret — treat it as sensitive.
Persistence & Privilege
always:false and no install means the skill does not request elevated persistence. The skill can register webhooks via the platform API which creates persistent external callbacks; combined with autonomous invocation (platform default), that could be used to stream events externally if misconfigured. The skill does not attempt to change other skills or system-wide settings.
What to consider before installing
This skill appears to implement a real marketplace API, but there are important mismatches you should consider before installing:
- Understand signing: The skill’s runtime requires wallet signatures (wallet.signMessage and wallet.sendTransaction). The skill does NOT declare any wallet/private-key env var. Ask the author how signing is intended to be provided (interactive user signing vs. an agent-held private key). Never paste your private key into a skill unless you explicitly trust it and understand the consequences.
- Treat HUMANNFT_API_KEY as sensitive: an API key may grant the skill the ability to create transactions and register webhooks. Only install if you trust the HumanNFT service and the skill owner.
- Webhooks and npx: The skill can register webhooks (which could send events out to arbitrary URLs) and recommends running an npx package. If you plan to use those features, audit the registry package and control webhook targets.
- If you expect true autonomous trading: insist the skill author document how signing will be handled securely (hardware wallet, delegated signing service, or never-autonomous flow). If that is not clarified, treat the skill as capable of prompting you to expose highly sensitive secrets.
If you are unsure, ask the skill author for (1) explicit credential requirements for signing transactions, (2) details on what the HUMANNFT_API_KEY can do and how long it lives, and (3) the code or npm package audited before running any recommended installers.Like a lobster shell, security has layers — review code before you run it.
latestvk9702h5j9wh44s1m738bx8x5z981759z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧬 Clawdis
EnvHUMANNFT_API_KEY