LYRA Coin Launch Manager
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches its stated coin-launch purpose, but it includes instructions that could cause an agent to publish a launch-triggering post for a token without a clear final human approval gate.
Before installing or invoking this skill, decide whether you want an agent to assist with token-launch posting at all. Do not allow it to publish a !clawnch launch post unless you have reviewed and approved the exact wallet, symbol, token details, account, and trigger surface. Enable the cron monitor only if you want recurring checks and local file/bookmark updates.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent has access to a posting surface, it could publish a token-launch trigger using the user's chosen wallet and token details.
This instructs the agent how to publish a launch-triggering post for a token. Because token launches and public posts can have irreversible financial/public impact, the workflow should require explicit final user approval before posting.
### 1) Launch trigger post Post the exact Clawnch format: ``` !clawnch name: <token name> symbol: <SYMBOL> wallet: <0x...>
Require an explicit user confirmation step before any !clawnch post, including the exact token name, symbol, wallet, image, trigger surface, and destination account.
If enabled, the monitor may keep running periodically, updating local receipts, verification files, bookmarks, and logs.
The skill documents an optional recurring monitor. It is disclosed and user-scheduled, but it creates ongoing background network checks and local writes.
Schedule (suggested low frequency to avoid timeouts/indexer lag): every **15 minutes**. If using OpenClaw cron tool, wrap these commands in a script and call that script from the job.
Only schedule the cron job deliberately, keep the frequency low, and review what files it writes before enabling it.
External launch data and monitoring URLs may become part of the local bookmark memory used later.
The skill persists launch and monitoring links into a local bookmark/memory area that future workflows or agents may reuse.
- Bookmark refs: `brainwave/BOOKMARK_BRAIN/refs/<topic>.md` ### 3) Save Clanker + monitoring links into BOOKMARK BRAIN
Review saved bookmarks periodically and avoid treating bookmarked external data as authoritative without re-checking the source.
The skill may fail or behave differently depending on the local Python environment and whether the referenced bookmark tool exists.
The registry describes no install spec while bundled Python scripts require runtime dependencies and a local bookmark helper. This is not evidence of malicious behavior, but it means setup expectations are not fully declared in metadata.
Install specifications No install spec — this is an instruction-only skill. Code file presence 5 code file(s)
Inspect the scripts and make sure required Python packages and local tools are present before running them.