Crypto Engine Agent Signal
v0.1.1Buy the latest machine-readable BTC directional signal from Crypto Engine through a Tempo MPP-enabled endpoint.
⭐ 2· 39·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (buying a paid BTC directional signal) lines up with the runtime actions described: discovering product metadata, calling the paid endpoint, handling Tempo MPP 402 challenges, and retrying with payment credentials. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md is instruction-only and narrowly scoped to HTTP discovery and POST to the paid endpoint, parsing 402 challenges, and completing Tempo MPP payments. It does not direct the agent to read local files or unrelated system state. Note: the instructions require the runtime to perform financial actions (complete MPP payment challenges) — this is expected for the skill but is a sensitive capability and the skill correctly adds guardrails (require explicit user request, don't leak wallet secrets).
Install Mechanism
There is no install spec and no code files; the skill is instruction-only, so nothing is written to disk or installed by the skill itself.
Credentials
The skill declares no environment variables or credentials, which is proportionate. However, successful execution requires a runtime that holds or can sign payments (wallet/payment middleware). Those runtime-held secrets are outside the skill but are required to complete the flow — only enable this skill where you control or trust payment approval and secret handling.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide config changes or persistent privileges. Autonomous invocation is permitted by default but not combined with other elevated privileges here.
Assessment
This skill is coherent for its purpose but it performs paid requests: only enable it in agents/runtimes that you trust to handle payments. Before using, verify the endpoint (https://cryptoengine.club) and the discovery document yourself, require explicit user confirmation before any payment, set limits or require manual wallet approval, and ensure your runtime does not leak wallet secrets or auto-approve payments. If your agent cannot complete Tempo MPP flows, do not enable this skill — it will simply be unable to work. If you are unsure about the endpoint's reputation, treat the first use as a manual step (inspect the 402 challenge and merchant identity) rather than an automatic payment.Like a lobster shell, security has layers — review code before you run it.
bitcoinvk9774yt18npe2memdnxcbrd92d8439sycryptovk9774yt18npe2memdnxcbrd92d8439syfinancevk9774yt18npe2memdnxcbrd92d8439sylatestvk9774yt18npe2memdnxcbrd92d8439symppvk9774yt18npe2memdnxcbrd92d8439sysignalsvk9774yt18npe2memdnxcbrd92d8439sytempovk9774yt18npe2memdnxcbrd92d8439sytradingvk9774yt18npe2memdnxcbrd92d8439sy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.