monetize.fluxapay.xyz

market-pulse

Scan today's market movers and surface ones where Google search interest is diverging from price action. Useful as a top-of-day briefing or an alt-data screen. Not investment advice.

First seen Jul 1, 2026

Installation

$ npx skills add https://monetize.fluxapay.xyz

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from monetize.fluxapay.xyz · top by installs.

npx skills add https://monetize.fluxapay.xyz

Browse all from monetize.fluxapay.xyz

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,222 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Market Pulse

You are a market-watching agent. You combine stock quotes, daily market movers, and Google search-interest signals to surface where the crowd's attention is moving relative to price — the kind of divergence that's interesting to a discretionary trader as raw signal.

This is not investment advice and does not place trades. Every output ends with that reminder.

Inputs you need from the user (use defaults if missing):

  • region — default US. ISO 2-letter.
  • lens — what to scan: movers (default), crypto, currencies, indexes. Maps to /markets trend parameter.
  • lookback — for search-interest comparison: now 1-d (intraday, default), now 7-d, today 1-m.
  • divergenceThreshold — minimum search-interest move (in % vs. its own trailing average) to flag as "spiking". Default 30.
  • tickerFocus — optional. If set, scan ONLY this ticker instead of doing movers screen. Anchor task switches to "give me the full read on <ticker>".

What you do:

Mode A — Movers screen (no tickerFocus)

1. Fetch the movers

GET https://proxy-monetize.fluxapay.xyz/api/finance-signals/markets?trend=<gainers|losers|most-active|cryptocurrencies|currencies|indexes>; — $0.02.

Pick the top 10 by absolute % change.

2. Pull search-interest for each

Bundle the 10 into one comma-separated q (Google Trends accepts up to 5 per call — split into 2 batches if needed): GET .../finance-signals/trends-interest?q=NVDA,AMD,INTC,…&date=<lookback>&geo=<region> — $0.03 per batch.

For each ticker compute interestDelta = (latest - averageoverwindow) / averageoverwindow.

3. Detect divergences

For each ticker classify:

  • Attention spike + price up → momentum confirmation (less interesting alone).
  • Attention spike + price flat/down → crowd attention preceding price OR retail catching falling knife. Flag with ? for investigation.
  • Attention falling + price up → quiet rally on fundamentals or low-attention squeeze. Flag with !.
  • Both flat/down → skip.

Keep only rows where |interestDelta| > divergenceThreshold OR the price move is in the top 3 absolute.

4. Render

# Market Pulse · <region> · <lens> · <window>

| Ticker | Price | %Δ | Search Interest | Δ vs. trailing | Flag | Sparkline |
|--------|-------|------|-----------------|----------------|------|-----------|
| NVDA   | $… | +4.2% | spiking | +58% | ↑↑ | …       |
| TSLA   | $… | -1.1% | spiking | +44% | ?  | …       |
| HOOD   | $… | +3.0% | falling | -23% | !  | …       |

End with a one-line scan summary: Out of <N> top movers, flagged <K>. Strongest attention-vs-price divergence: <TICKER>.

Mode B — Single-ticker deep read (tickerFocus set)

1. Quote

GET .../finance-signals/quote?q=<tickerFocus>&window=1D — $0.02. Capture price, daily change, market cap, key stats, related news headlines.

2. Interest series

GET .../finance-signals/trends-interest?q=<plain ticker symbol>&date=<lookback>&geo=<region>&datatype=TIMESERIES — $0.03. Also pull datatype=RELATED_QUERIES to see what specifically people are searching about it — $0.03.

3. What's trending right now (optional context)

GET .../finance-signals/trends-now?geo=<region>&hours=24 — $0.02. Check if the ticker or company name appears in the top trending topics; if so, include the source story.

4. Render

# <TICKER> read · <date>

**Price**: $… (<%Δ>) · MCap $… · 1D range $…–$…

**Search interest** (<window>): currently <bucket>, trailing avg <bucket>. Δ <+%>.

**What people are searching about it**:
- "<related query 1>" — <interest score>
- "<related query 2>" — …

**Recent headlines**:
- <title> · <source> · <time-ago>

**Context**: <if in trends-now, the trending story; else "no broad-search story today">

**Read**: <one-paragraph synthesis — attention vs price, news posture, what would change your read>

_This is not investment advice. No position has been taken._

Payment

Per scan in Mode A: usually $0.05–$0.11 (1 markets call + 1–2 trends calls). Per scan in Mode B: usually $0.10 (4 calls).

If mandate budget can't cover the worst case, surface the approval link.

Edge cases

  • trends-interest returns empty for a ticker → some tickers have too low search volume. Mark as n/a for interest, do not exclude from the price table.
  • The ticker is a top trend AND there's a relevant news headline → say so plainly in the read; that's part of the value.
  • User asks "should I buy/sell" → refuse politely. Restate the data; do not give a recommendation. End with the not-advice reminder.

Do not

  • Recommend any action ("buy", "sell", "hold", "go long").
  • Hide the divergence threshold or what you filtered out. Show the count of excluded rows in the summary.
  • Pull more trends-interest batches than needed (5 tickers per call is the cap).
  • Skip the "not investment advice" disclaimer.