maintain-curators

Audit curator feeder YAML files for stale social and RSS error markers and repair or tombstone entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curator feed configuration files accumulate error and death markers (dead Twitter handles, stale RSS feeds, disabled LinkedIn bridges) stamped by an automated scanner, and someone must verify whether each marker still reflects reality and repair the entry without breaking the strict YAML schema.

Core Features & Use Cases

  • Marker Auditing: Inventories every curator YAML file carrying twitter-dead-at, twitter-handle-resolved-unknown-at, linkedin-rss-hub-disabled-at, rss-dead-at, or rss-failure markers and verifies each against live evidence via WebSearch, curl, and nslookup.
  • Guided Repair Actions: Clears false-positive markers, repoints renamed handles and migrated feeds, or tombstones genuinely defunct entities, always leaving a dated audit comment.
  • Schema-Safe Verification: Validates every edited file against the strict strictyaml mapping schema and reloads all feed sources to confirm nothing broke.
  • Use Case: Run a monthly maintenance pass over eth_defi/data/feeds/curators/ to clear a stale twitter-dead-at marker on an active account, repoint a blog that migrated from Medium to Substack, and tombstone a curator whose domain no longer resolves.

Quick Start

Audit all curator feeder YAML files in eth_defi/data/feeds/curators for stale error markers, verify each against live sources, and clear, repoint, or tombstone entries with dated audit comments.

Frequently Asked Questions about maintain-curators

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

FAQPage Schema
How do I audit curator feed YAML files for dead Twitter and RSS sources?

Grep the curator directory for marker fields like twitter-dead-at and rss-dead-at, then verify each with WebSearch for social liveness and curl for RSS feed freshness. Clear false positives, repoint moved sources, or leave markers with a dated audit comment.

What is the difference between twitter-dead-at and twitter-handle-resolved-unknown-at?

twitter-handle-resolved-unknown-at means the handle could not be resolved to an account and is refuted by a live, correctly-named profile. twitter-dead-at is a recency signal from the collector database and can only be cleared with a concrete post dated within the 180-day window.

Why does WebFetch fail when checking Twitter or LinkedIn liveness?

X and LinkedIn return HTTP 402 or 403 to nearly all automated fetchers, so a failed fetch proves nothing about account health. Use WebSearch instead, which surfaces indexed profiles and dated post snippets.

Can I add new marker fields to curator YAML files?

No. The strictyaml _MAPPING_SCHEMA in eth_defi/feed/sources.py is strict, and any unknown top-level key makes the file fail to load. Record website deadness and tombstones as YAML comments instead.

When should I tombstone a curator entity instead of clearing markers?

Tombstone only on positive evidence the organisation is gone, such as an NXDOMAIN website plus suspended socials with no successor. Never tombstone on inconclusive evidence; leave the markers and record the finding in a dated comment.