---
name: trend-discovery
description: Use when the user wants to discover trending social topics, hashtags, sounds, posts, reels, shorts, creators, or formats in a niche. Searches public trend and discovery endpoints, ranks evidence, and turns trends into practical content angles.
allowed-tools: Bash, Read, Write, WebFetch

version: 1.0.0
author: ScrapeCreators
license: MIT
homepage: https://scrapecreators.com
repository: https://github.com/ScrapeCreators/social-media-research-skills
metadata:
  openclaw:
    requires:
      env:
        - SCRAPECREATORS_API_KEY
    primaryEnv: SCRAPECREATORS_API_KEY
    homepage: https://scrapecreators.com
    tags:
      - social-media
      - research
      - scrapecreators
title: trend-discovery
canonical_url: https://skilld.dev/gh/scrapecreators/social-media-research-skills/trend-discovery
last_updated: 2026-10-23T07:46:32.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install scrapecreators/social-media-research-skills/trend-discovery`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/trend-discovery`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/scrapecreators/social-media-research-skills/trend-discovery) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/trend-discovery`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/trend-discovery --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/trend-discovery --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Trend Discovery

## Overview

Find trends worth acting on. This skill is for social media trend research across TikTok, Instagram, YouTube, Reddit, Pinterest, and other public sources. The output should separate real evidence from vague "this is trending" claims.

## When to Use

Use this skill when the user asks to:

- find trends in a niche or category
- discover trending TikTok sounds, hashtags, creators, or videos
- find trending Instagram Reels or YouTube Shorts ideas
- build a weekly trend brief
- decide what content formats or angles to jump on

## Useful Sources

| Signal | Endpoint examples |
|---|---|
| TikTok trending feed | `/v1/tiktok/get-trending-feed` |
| TikTok popular hashtags/songs/videos/creators | `/v1/tiktok/hashtags/popular`, `/v1/tiktok/songs/popular`, `/v1/tiktok/videos/popular`, `/v1/tiktok/creators/popular` |
| TikTok search | `/v1/tiktok/search/top`, `/v1/tiktok/search/keyword`, `/v1/tiktok/search/hashtag` |
| Instagram trends/search | `/v1/instagram/reels/trending`, `/v2/instagram/reels/search`, `/v1/instagram/search/hashtag` |
| YouTube | `/v1/youtube/shorts/trending`, `/v1/youtube/search`, `/v1/youtube/search/hashtag` |
| Reddit | `/v1/reddit/search`, `/v1/reddit/subreddit`, `/v1/reddit/subreddit/search` |
| Pinterest | `/v1/pinterest/search` |

## Workflow

1. Define niche, country/region, platform, and time sensitivity.
2. Pull trend/discovery/search results from 2-4 relevant sources.
3. Normalize evidence: post URL, creator, metric, date, topic, sound/hashtag if present.
4. Cluster into trends by topic, format, hook, sound, meme, or audience problem.
5. Rank trends by evidence strength and relevance, not raw views alone.
6. Translate each trend into content ideas the user can actually make.

## Output Format

```markdown
# Trend Discovery Brief: {niche}

## Trends Worth Acting On
| Trend | Platforms | Evidence | Why it matters | Content angle |
|---|---|---|---|---|

## Sounds / Hashtags / Formats
- ...

## Example Posts to Study
- [title/hook](url) — why it matters

## Content Ideas
1. ...
2. ...

## Caveats
- Public data only.
- Trend evidence is directional unless repeated across sources.
```

## Common Pitfalls

- Do not call something a trend from one post unless the user only asked for examples.
- Do not ignore region. TikTok trends can be highly country-specific.
- Do not recommend jumping on trends that do not fit the user's brand or audience.
