Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
agent execution market
v1.0.0Manage user intents through submission, validation, lifecycle tracking, cancellation, bidding, execution, and completion with cryptographic verification and...
⭐ 0· 183·0 current·0 all-time
byJustin Liu@zhenstaff
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill advertises a full Agent Execution Market (server endpoints, WebSocket, CLI, TypeScript SDK, Ed25519 key management, Merkle proofs, etc.) but the bundle contains only prose (SKILL.md and readme). There are no binaries, no npm package, no network endpoint configuration, and no declared credentials. A functioning marketplace would legitimately require code, dependencies, network endpoints, and keys — their absence is a significant inconsistency.
Instruction Scope
The SKILL.md describes runtime behaviors (submit intents, verify signatures, run bidding windows, maintain reputations, provide 13 REST endpoints and 11 WebSocket events) but provides no implementation, no base URLs, and no instructions for where to perform these network operations. The docs include examples pointing at 'http://localhost:3000' and CLI commands but the skill does not install or declare those tools. The runtime instructions therefore promise operations the skill cannot actually perform as packaged.
Install Mechanism
There is no install spec (instruction-only). While 'no install' is low risk from a code-execution perspective, here it's notable because the described capabilities would normally require an installable package (npm) or binaries. The lack of any install mechanism is inconsistent with the claimed functionality and suggests this is documentation-only rather than an operational skill.
Credentials
The skill claims cryptographic key management and signing (Ed25519) and operations that would normally require private keys, API endpoints, or service credentials, yet declares no required environment variables, no primary credential, and no config paths. This mismatch means the skill either expects secrets to be supplied ad hoc (not declared) or cannot perform the claimed cryptographic operations — both are red flags.
Persistence & Privilege
The skill does not request 'always: true' and uses default model-invocation settings. It does not declare any system-wide persistence or elevated privileges. On this axis there is no immediate concern.
What to consider before installing
This package reads like full product documentation, not an installable skill. Before using or installing: (1) ask the publisher for the actual code repository or npm package and verify the package contents and install steps; (2) request explicit runtime requirements: which endpoints, which env vars (private keys, service URLs), and what binaries will be installed; (3) do not provide secrets or private keys unless you confirm a trustworthy implementation and review the code; (4) if you expected an operational CLI/SDK, insist on an install spec (npm package, checksums, GitHub release link) and auditable source — otherwise treat this as informational documentation only.Like a lobster shell, security has layers — review code before you run it.
latestvk97ed2k8ecw4kz7t312d50tssx82t00s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.