Skip to content
Back to skills

Trend Spotter

ASecurity

Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score.

  • 200 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsgoapi

Works with

  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 26, 2026

npx -y skills add sandbaseai/sandbase-skills --skill trend-spotter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Trend Spotter?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Trend Spotter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sandbaseai-trend-spotter/badge)](https://www.skillsdirectory.com/skills/sandbaseai-trend-spotter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: trend-spotter
description: "Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score."
---

# Trend Spotter

Identify emerging trends early by monitoring signals across Twitter trending, TikTok viral content, YouTube rising videos, Google News velocity, and Reddit community buzz. Combines platform-specific trend indicators into a unified trend confidence score. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

## Capability identifiers

- `twitter_web_trending`
- `tiktok_app_v3_home_feed`
- `youtube_web_v2_general_search`
- `google_news_bulk_articles`
- `reddit_app_popular_feed`
- `weibo_web_hot_search`

## Workflow

1. Understand the user's research question, target, and context.
2. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.
3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- Always call `sandbase_inspect` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.

Files in this skill

  • SKILL.md1.8 KB
  • references/sandbase-api-map.md766 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…