Skillshub apify-trend-analysis
Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/apify/agent-skills/apify-trend-analysis" ~/.claude/skills/comeonoliver-skillshub-apify-trend-analysis && rm -rf "$T"
manifest:
skills/apify/agent-skills/apify-trend-analysis/SKILL.mdsource content
Trend Analysis
Discover and track emerging trends using Apify Actors to extract data from multiple platforms.
Prerequisites
(No need to check it upfront)
file with.envAPIFY_TOKEN- Node.js 20.6+ (for native
support)--env-file
CLI tool:mcpcnpm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress: - [ ] Step 1: Identify trend type (select Actor) - [ ] Step 2: Fetch Actor schema via mcpc - [ ] Step 3: Ask user preferences (format, filename) - [ ] Step 4: Run the analysis script - [ ] Step 5: Summarize findings
Step 1: Identify Trend Type
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Search trends | | Google Trends data |
| Hashtag tracking | | Hashtag content |
| Hashtag metrics | | Performance stats |
| Visual trends | | Post analysis |
| Trending discovery | | Search trends |
| Comprehensive tracking | | Full data |
| API-based trends | | API access |
| Engagement trends | | Comment tracking |
| Product trends | | Marketplace data |
| Visual analysis | | Photo trends |
| Community trends | | Group monitoring |
| YouTube Shorts | | Short-form trends |
| YouTube hashtags | | Hashtag videos |
| TikTok hashtags | | Hashtag content |
| Trending sounds | | Audio trends |
| TikTok ads | | Ad trends |
| Discover page | | Discover trends |
| Explore trends | | Explore content |
| Trending content | | Viral content |
Step 2: Fetch Actor Schema
Fetch the Actor's input schema and details dynamically using mcpc:
export $(grep APIFY_TOKEN .env | xargs) && mcpc --json mcp.apify.com --header "Authorization: Bearer $APIFY_TOKEN" tools-call fetch-actor-details actor:="ACTOR_ID" | jq -r ".content"
Replace
ACTOR_ID with the selected Actor (e.g., apify/google-trends-scraper).
This returns:
- Actor description and README
- Required and optional input parameters
- Output fields (if available)
Step 3: Ask User Preferences
Before running, ask:
- Output format:
- Quick answer - Display top few results in chat (no file saved)
- CSV - Full export with all fields
- JSON - Full export in JSON format
- Number of results: Based on character of use case
Step 4: Run the Script
Quick answer (display in chat, no file):
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \ --actor "ACTOR_ID" \ --input 'JSON_INPUT'
CSV:
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \ --actor "ACTOR_ID" \ --input 'JSON_INPUT' \ --output YYYY-MM-DD_OUTPUT_FILE.csv \ --format csv
JSON:
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \ --actor "ACTOR_ID" \ --input 'JSON_INPUT' \ --output YYYY-MM-DD_OUTPUT_FILE.json \ --format json
Step 5: Summarize Findings
After completion, report:
- Number of results found
- File location and name
- Key trend insights
- Suggested next steps (deeper analysis, content opportunities)
Error Handling
APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_token
mcpc not found - Ask user to install npm install -g @apify/mcpc
Actor not found - Check Actor ID spelling
Run FAILED - Ask user to check Apify console link in error output
Timeout - Reduce input size or increase --timeout