Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
QuantumForge
v1.0.0Decentralized AI platform using simulated quantum algorithms on Nostr for real-time swarm collaboration, tokenized compute exchange, and multi-chain AI asset...
⭐ 0· 1.5k·0 current·0 all-time
by@kosasih
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The SKILL.md describes a large decentralized quantum/blockchain system and instructs cloning a GitHub repo and installing Node/Python dependencies, but the registry metadata declares no code, no install spec, and no required env vars. The manifest and metadata do not align with the heavy capabilities described (multi-chain minting, cash zaps, network relays). The instructions also rely on external services (relay.quantumforge.org, GitHub repo) that are not validated or declared in the registry metadata.
Instruction Scope
The runtime instructions tell the agent to: git clone an external repository, run npm/pip installs, export a NOSTR_PRIVATE_KEY and RELAY_URL environment variables, initialize and bootstrap into a swarm, publish events to relays, and perform zaps/minting. These are network- and key-sensitive operations that go beyond a simple instruction-only skill. The JS example wrongly uses the private-key env var as the event 'pubkey' (which could leak a private key if used as-is). The instructions implicitly require crypto wallet operations (minting, zaps) but do not declare or justify the needed credentials. Overall the instructions ask the agent to read/set/transmit secrets and to perform network actions not represented in the declared requirements.
Install Mechanism
There is no declared install spec in the registry, but SKILL.md instructs cloning https://github.com/quantumforge/quantumforge.git and running npm/pip installs and init scripts. Downloading and executing code from an external GitHub repo is an implicit install mechanism and introduces risk because the repository and its contents are not included in the package, not pinned, and not validated. The relay URL is a project-owned domain (wss://relay.quantumforge.org) rather than a well-known public endpoint; that increases trust burden.
Credentials
Declared requirements list no env vars or credentials, yet SKILL.md explicitly requires NOSTR_PRIVATE_KEY and RELAY_URL and implies further crypto keys for multi-chain minting and zaps. Requiring a private key in an environment variable is sensitive and should be declared and justified. The mismatch between declared and required credentials is disproportionate and risky. The example code also mishandles keys (using a private key as the pubkey), increasing the chance of accidental key exposure.
Persistence & Privilege
The skill does not request always:true and is user-invocable (normal). It enables autonomous invocation by default (disable-model-invocation: false), which is standard, but combined with the above concerns (network commands, key usage, external code execution) means an autonomously-invoked agent could perform network actions and transactions. The skill does not request modifying other skill configs or system-wide settings.
What to consider before installing
This skill is inconsistent and potentially risky. Before installing or running it: 1) Do not export or use a private key (NOSTR_PRIVATE_KEY) until you have audited the code — the SKILL.md even shows an incorrect example that could leak keys. 2) Verify the GitHub repo (https://github.com/quantumforge/quantumforge.git) exists, inspect its code, and ensure dependencies and init scripts are safe; do not run npm/pip installs blindly. 3) Treat the relay domain (wss://relay.quantumforge.org) as untrusted until you can confirm ownership and behavior; publishing events there could leak identity or keys. 4) Expect additional undisclosed credentials for minting/zaps (wallet/private keys); require explicit listing and least-privilege tokens, not full private keys. 5) If you want to test, do so in an isolated environment with ephemeral keys and read-only configurations. 6) Prefer to see the skill include an explicit install spec, declared required env vars, and a clear privacy/security section; absence of those is a red flag. If you cannot review the external repo and init scripts yourself, avoid installing or running this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk978q7zqr4b5faxbwv1qt0f8s580kfq4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.