airdrop-monitor-cn_skill

Overview

This skill monitors airdrop announcement and documentation pages to turn ad-hoc "airdrop hunting" into a repeatable monitoring workflow. It detects page content changes, extracts deadline clues, flags high-risk keywords and suspicious links, and produces a concise daily action list you can run locally or with optional pay-per-call gating.

How this skill works

The skill periodically fetches configured announcement and docs URLs, computes diffs, and highlights which sources changed. It uses lightweight NLP to extract deadline and eligibility clues from updated text and scans for risky patterns such as seed/privkey mentions and dangerous URLs. Outputs include a ranked set of actionable items for the day, risk alerts, and an archive of change history. Optional SkillPay integration enforces per-call billing and returns a payment URL when balance is insufficient.

When to use it

• You want automated monitoring of project announcement or docs pages for airdrop-related changes.
• You need fast detection of newly posted deadlines or eligibility rules.
• You want to spot phishing links or accidental secret leaks in public docs.
• You need a daily action list to coordinate manual claiming or bot tasks.
• You want local-first operation with optional per-call billing for shared access.

Best practices

• Run the monitor locally in a virtualenv and keep configuration files out of public repos.
• Schedule checks regularly (every 10–30 minutes) with cron or a task runner to catch time-sensitive updates.
• Audit flagged risky content manually before taking action; the tool highlights clues but does not make financial decisions.
• Never store or submit private keys or seed phrases to the tool; the monitor only detects and warns about them.
• Protect billing keys and raw user IDs as environment variables, and test billing with the provided verification script.

Example use cases

• Track a project's announcement page for a sudden airdrop eligibility update and receive a prioritized claim checklist.
• Detect a suspicious redirect or external link introduced into docs that could indicate a phishing attempt.
• Maintain an archive of announcement diffs to prove timing of published eligibility criteria.
• Integrate with a team channel (Discord) to gate monitoring via optional micro-payments and prevent abuse.
• Automate routine checks before manual claim runs to focus time on high-value targets.