check-stablecoins

Audit stablecoin YAML files for Twitter activity and domain availability.

823|187|Updated Jan 30, 2022
One-click install
npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill check-stablecoins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-stablecoins
Source: https://github.com/tradingstrategy-ai/web3-ethereum-defi/tree/main/.claude/skills/check-stablecoins
Command: npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill check-stablecoins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining a large registry of stablecoin metadata files makes it hard to know which projects are still active, which websites are down, and which entries need manual review.

Core Features & Use Cases

  • Liveness Auditing: Checks Twitter/X account activity and homepage domain reachability for every stablecoin YAML file in the registry.
  • Automated Enrichment: Searches for missing Twitter and homepage links, and appends wind-down status notes to long descriptions when shutdown news is found.
  • Structured Output: Adds a standardized checks section with dates for last Twitter post, domain confirmation, dead marking, and missing-information flags.
  • Use Case: Run a periodic audit across roughly 188 stablecoin YAML files using parallel subagents, then receive a summary table of active, dead, and unverifiable projects.

Quick Start

Run the check-stablecoins skill to audit all stablecoin YAML files and add checks sections to each one.

Frequently Asked Questions about check-stablecoins

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if stablecoin projects in YAML files are still active?

Run the skill against the stablecoins directory; it fetches each project's Twitter/X profile and homepage, then records the last post date and domain status in a checks section added to every YAML file.

How does the skill decide a stablecoin is dead?

A stablecoin is marked dead only with strong evidence: a known-good homepage domain is confirmed down, or a known-good Twitter account has not posted in over six months. Missing information alone never triggers the dead flag.

Can it handle YAML files with multiple stablecoin entries?

Yes. Multi-entry files with an entries list are supported; each entry is checked independently and receives its own checks block indented at the entry level, while single-entry files get a top-level checks key.

What happens when Twitter/X blocks web requests?

The skill falls back to web searches for recent handle activity and Nitter mirrors such as nitter.net. If all attempts fail inconclusively, the file is flagged with information_found_missing_at for later manual review.

Does a 403 Cloudflare response mean the domain is down?

No. If the response contains Cloudflare challenge content such as a browser-check page, the domain is treated as up and domain_up_at is set to the current date.