Perp Lobster

Trade on Hyperliquid DEX with simple commands. Place market/limit orders on perps, or run automated bots (market making, grid trading) with a web dashboard.

What to consider before installing/using Perp Lobster: - This skill will clone and run code from https://github.com/ThisNewMark/perplobster and asks you to run its setup.sh (which installs packages). Do not run setup.sh without reviewing its contents. - The project requires you to put a private key (HL_SECRET_KEY) into perplobster/.env on your machine. The skill states it will not ask you to paste keys into chat and will not read the .env file; however, the project scripts will access that file when they run. Use an account/subaccount with minimal funds and limited permissions. - Before approving any script execution, inspect the scripts referenced (setup.sh, scripts/trade.py, start.sh, approve_builder_fee.py). The SKILL.md recommends doing this (cat file) — follow that guidance every time. - Prefer running the code in an isolated environment (VM or container) and not on a machine with other sensitive keys or tokens. Consider creating a new wallet/subaccount specifically for bots. - Verify the GitHub repo: check commit history, contributors, and issues to confirm it is the expected project and not a typo-squatted/malicious fork. - If you want stronger safety, avoid enabling autonomous invocation for this skill (require user confirmation for all actions) and do not store high-value keys on the same host. - The registry metadata does not declare the required local .env keys; treat that as a documentation gap and do not assume the skill has no credential needs.

Type: OpenClaw Skill Name: perp-lobster Version: 1.0.7 The skill is classified as suspicious due to its reliance on downloading and executing code from an external GitHub repository (`git clone https://github.com/ThisNewMark/perplobster.git`) for financial trading operations. While the `SKILL.md` includes good security practices like explicit instructions not to handle private keys in chat, requiring user approval for `setup.sh`, and transparent command execution, the fundamental act of fetching and running arbitrary scripts from a remote source introduces a significant supply chain vulnerability and potential for remote code execution if the external repository were compromised. There is no evidence of intentional malicious behavior within the provided skill bundle itself, but the high-risk capabilities and external dependency warrant a 'suspicious' classification.