LYRA Coin Launch Manager

Coin launch memory + verification workflow for Clawnch (4claw/Moltx/Moltbook). Use to launch tokens safely, record canonical receipts (contract+txHash+postUrl), update local dashboard, and save Clanker/monitor links into BOOKMARK BRAIN.

Security Scan

The skill's code and runtime instructions are consistent with a coin-launch tracking/verification tool; there are no obvious mismatches that suggest intentional misdirection, but some small operational omissions and assumptions increase risk if you install blindly.

Purpose & Capability

Name/description (coin launch memory + verification for Clawnch) align with what the code does: fetching launches from clawn.ch, normalizing receipts, verifying via Blockscout/Dexscreener, and adding bookmark links. The requested resources (none declared) are broadly consistent with this purpose.

Instruction Scope

SKILL.md and the scripts confine their actions to the stated workflow: reading/writing files under the workspace (state/, reference/, brain bookmark paths), calling Clawnch and indexer APIs, and invoking a local bookmarking helper. However the scripts call an external local tool (tools/bookmark_brain_add_url.py) via subprocess without packaging or declaring it; that helper likely requires credentials or other configuration outside the skill's scope. The scripts also perform arbitrary subprocess calls (running other Python scripts) — expected for orchestration but worth auditing the invoked tools and ensuring they are trusted.

Install Mechanism

No install spec (instruction + included scripts only). This is lower-risk than fetching remote archives. The package includes multiple Python scripts (source provided) and does not download code at runtime. Note: the scripts use the 'requests' library but no dependencies are declared; installation will fail if 'requests' isn't present.

Credentials

The skill does not request any environment variables or credentials, and its network calls are to expected endpoints (clawn.ch, clanker.world, base.blockscout.com, api.dexscreener.com). A practical mismatch: adding bookmarks calls tools/bookmark_brain_add_url.py which likely requires bookmark service credentials (e.g., Yandex) that are not declared. If you plan to use the bookmark feature, verify where that tool reads credentials from and whether those credentials are already provisioned in your environment.

Persistence & Privilege

always is false and disable-model-invocation is default; the skill does not attempt to modify other skills or global agent config. It writes files under workspace (state/, reference/) which is expected behavior for this tool.

Assessment

This skill appears to do what it says — fetch Clawnch receipts, normalize them, verify via indexers, and optionally add bookmarks. Before installing or enabling it: 1) Inspect or supply the external helper tools it calls (tools/bookmark_brain_add_url.py) — they may require credentials or have their own behavior; the skill does not declare or manage those secrets. 2) Ensure the Python runtime has the 'requests' package (the scripts will fail otherwise). 3) Review the included scripts to confirm you are comfortable with file writes under workspace/state and workspace/reference and with the network endpoints being contacted (clawn.ch, blockscout, dexscreener, clanker). 4) If you will run this as a cron/monitor, run it in a limited/sandboxed environment first to confirm it behaves as you expect and that no unexpected external endpoints are used. If you need higher assurance, request the source/origin of the skill (homepage/source is unknown) and confirm the bookmark tool's implementation and credential handling before granting it access to bookmark services.

LYRA Coin Launch Manager (Clawnch) — v1

What “done right” means (non-negotiable)

A coin is only considered launched when you have a Clawnch receipt containing at minimum:

• symbol
• contractAddress
• clankerUrl
• postUrl or postId
• txHash (if present in API)
• chainId (Base = 8453)

Never treat a wallet address, thread id, or post id as the contract.

Canonical data sources (priority order)

1. Clawnch API: https://clawn.ch/api/launches (authoritative)
2. Clanker page: https://clanker.world/clanker/<contract> (UI)
3. Indexers (best-effort / laggy): Blockscout, Dexscreener

Workspace conventions (v1)

• State receipts (machine-readable): state/<SYMBOL>_clawnch_receipt.json
• Human receipts: reference/STARCORE_LAUNCH_RECEIPTS_YYYY-MM-DD.md
• Bookmark refs: brainwave/BOOKMARK_BRAIN/refs/<topic>.md

Workflow

0) Preflight

• Decide symbol + trigger surface (4claw | moltx | moltbook).
• Confirm the deployer wallet.

1) Launch trigger post

Post the exact Clawnch format:

!clawnch
name: <token name>
symbol: <SYMBOL>
wallet: <0x...>
description: <...>
image: <https://...>
website: <https://...>   (optional)
twitter: <@handle>       (optional)

2) Pull canonical receipt(s) (Clawnch API)

Use the script:

• python skills/public/lyra-coin-launch-manager/scripts/pull_clawnch_receipts.py --symbols STARCORE,STARCOREX --out state

This writes per-symbol receipts + a combined summary.

3) Save Clanker + monitoring links into BOOKMARK BRAIN

Use existing bookmark tool:

• python tools/bookmark_brain_add_url.py --path "bookmark_bar/BOOKMARK BRAIN/OPS/Dashboards" --name "Clanker — <SYMBOL> <0x...>" --url "<clankerUrl>"

4) Update local dashboard

If using enhanced_coin_dashboard_with_real_data.py, ensure it reads receipts from state/. (Preferred: STARCORE family comes from Clawnch receipts.)

5) Optional: monitoring cron

If you want recurring checks, schedule a cron job that:

• pulls latest receipts
• checks Blockscout/Dexscreener pair existence
• logs changes to daily_health.md

(Keep this low frequency; indexers/API can lag.)

Notes / troubleshooting

• If Moltbook requires verification, complete it; Clawnch may still pick up the post (but posting state can be confusing).
• Indexers can lag: “not a contract” on Blockscout can be temporary.