rwa-pulse

Collect and rank weekly RWA tokenization developments from web sources.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill rwa-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rwa-pulse
Source: https://github.com/aaronjmars/aeon/tree/main/skills/rwa-pulse
Command: npx skills add https://github.com/aaronjmars/aeon --skill rwa-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RWA tokenization updates are scattered across sources, making it hard to consistently track real momentum like launches, TVL milestones, institutional adoption, and regulatory actions.

Core Features & Use Cases

  • Weekly signal discovery: Finds the most relevant RWA developments from the last 7 days and filters out opinion pieces.
  • Current TVL & protocol stats: Pulls total market figures (when available) and protocol-specific TVL indicators, with fallbacks from fetch to search.
  • Operator memory updates: Appends a new RWA Pulse entry to the protocol memory so the weekly recap stays cumulative and actionable.
  • Use Case: If you manage an RWA research brief, this skill keeps your protocol watchlist current and produces a consistent weekly summary you can reuse for articles or newsletters.

Quick Start

Use the rwa-pulse skill to generate this week’s RWA momentum report and notification based on your existing memory files and the last 7 days of RWA coverage.

Frequently Asked Questions about rwa-pulse

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

FAQPage Schema
How do I track weekly real-world asset tokenization momentum and TVL milestones?

Track real-world asset tokenization momentum by using automated web search filtering to collect, deduplicate, and score weekly protocol launches, TVL milestones, and institutional adoption signals. This generates a structured weekly research digest.

What is the best way to automate recurring RWA research digests for newsletters?

Automate recurring RWA research digests by configuring a protocol watchlist and reading operator memory for last-known TVL baselines. The system fetches recent developments and writes back cumulative weekly summaries for newsletter reuse.

How does TVL tracking work when web fetching fails to retrieve current protocol stats?

TVL tracking implements a fallback mechanism from web fetch to web search when direct protocol stats are unavailable. It compares current total market figures against last-known TVL baselines stored in operator memory.

Can I use a configured protocol watchlist to filter institutional adoption signals?

Yes, you can use a configured protocol watchlist to filter institutional adoption signals. The system reads tracked protocols from operator memory and deduplicates top items based on your predefined watchlist parameters.

Do I need existing memory files to generate a weekly RWA market monitoring report?

Yes, generating a weekly RWA market monitoring report requires reading operator memory for last-known TVL baselines and tracked protocols. This ensures the weekly recap stays cumulative and builds upon prior data.

What limitations exist when filtering regulatory developments for RWA ecosystems?

Filtering regulatory developments is limited by the availability of public web sources over the last 7 days. The system applies time-bounded web search filtering to exclude opinion pieces but cannot synthesize unreported regulatory actions.