Skip to content
Back to skills

Launch Alert Bot

ASecurity

Build a bot that detects new Solana launches (mints/LPs) and sends safe alerts. Use for discovery and monitoring without shilling scams.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 9, 2026
toolsgodebugging

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill launch-alert-bot --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Launch Alert Bot?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Launch Alert Bot
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-launch-alert-bot/badge)](https://www.skillsdirectory.com/skills/majiayu000-launch-alert-bot)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: launch-alert-bot
description: Build a bot that detects new Solana launches (mints/LPs) and sends safe alerts. Use for discovery and monitoring without shilling scams.
---

# Launch Alert Bot

Role framing: You are a discovery bot operator. Your goal is to surface new launches with context while avoiding amplification of scams.

## Initial Assessment
- Data feeds (Helius token registry events, DEX pool creations, metadata updates)?
- Alert channels and audience? (public vs internal)
- Filters (min liquidity, authority revoked, verified creators)?
- Latency tolerance?

## Core Principles
- Prioritize safety: include risk flags and avoid implicit endorsements.
- Deduplicate across feeds; avoid double alerts for same mint/pool.
- Provide verifiable data: addresses, txids, authority states.

## Workflow
1) Source selection
   - Monitor pool creation events, new mints with metadata, social signals if desired.
2) Filtering and scoring
   - Apply thresholds: liquidity >= X, metadata exists, mint/freeze authority status, creator whitelist/blacklist.
3) Enrichment
   - Fetch metadata, authority info, initial LP stats; compute simple risk score.
4) Alerting
   - Message with mint/pool addresses, tx link, risk flags (authority retained? low LP? unknown metadata). Include "not financial advice".
5) Operations
   - Deduplicate by mint/pool; throttle; monitor error rates.

## Templates / Playbooks
- Alert template: "New pool detected: <mint> on <DEX> at slot <slot>. LP: . Mint authority: revoked/active. Risk flags: ... (tx link)."
- Risk score rubric: authority (revoked=+1 safe, active=-1), LP depth, metadata completeness, blacklist hit.

## Common Failure Modes + Debugging
- False positives from testnet/devnet: filter by cluster.
- Spam/scam alerts: strengthen filters, add manual review mode.
- Rate limits on data providers: cache and backoff.
- Metadata fetch failures: retry and mark partial info.

## Quality Bar / Validation
- Filters tuned to reduce noise; risk flags included.
- No duplicate alerts for same event.
- Clear disclaimer and source links in every alert.

## Output Format
Provide source list, filter rules, risk rubric, alert format, and ops checklist.

## Examples
- Simple: Internal bot watching Raydium pools > liquidity; alerts to Slack with authority status.
- Complex: Public bot combining pool events + social mentions; risk scoring; manual approve queue; sends to X/TG with safe copy and throttling.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.