2f55f046b9
* feat: add 12 official Apify skills for web scraping and data extraction Add the complete Apify agent-skills collection as official vendor skills, bringing the total skill count from 954 to 966. New skills: - apify-actor-development: Develop, debug, and deploy Apify Actors - apify-actorization: Convert existing projects into Apify Actors - apify-audience-analysis: Audience demographics across social platforms - apify-brand-reputation-monitoring: Track reviews, ratings, and sentiment - apify-competitor-intelligence: Analyze competitor strategies and pricing - apify-content-analytics: Track engagement metrics and campaign ROI - apify-ecommerce: E-commerce data scraping for pricing intelligence - apify-influencer-discovery: Find and evaluate influencers - apify-lead-generation: B2B/B2C lead generation from multiple platforms - apify-market-research: Market conditions and geographic opportunities - apify-trend-analysis: Discover emerging trends across platforms - apify-ultimate-scraper: Universal AI-powered web scraper Existing skill fixes: - design-orchestration: Add missing description, fix markdown list spacing - multi-agent-brainstorming: Add missing description, fix markdown list spacing Registry and documentation updates: - Update skill count to 966+ across README.md, README.vi.md - Add Apify to official sources in SOURCES.md and all README variants - Register new skills in catalog.json, skills_index.json, bundles.json, aliases.json - Update CATALOG.md category counts (data-ai: 152, infrastructure: 95) Validation script improvements: - Raise description length limit from 200 to 1024 characters - Add empty description validation check - Apply PEP 8 formatting (line length, spacing, trailing whitespace) * refactor: truncate skill descriptions in SKILL.md files and revert description length validation to 200 characters. * feat: Add `apify-ultimate-scraper` to data-ai and move `apify-lead-generation` from business to general categories.
123 lines
4.1 KiB
Markdown
123 lines
4.1 KiB
Markdown
---
|
|
name: apify-trend-analysis
|
|
description: Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
|
|
---
|
|
|
|
# Trend Analysis
|
|
|
|
Discover and track emerging trends using Apify Actors to extract data from multiple platforms.
|
|
|
|
## Prerequisites
|
|
(No need to check it upfront)
|
|
|
|
- `.env` file with `APIFY_TOKEN`
|
|
- Node.js 20.6+ (for native `--env-file` support)
|
|
- `mcpc` CLI tool: `npm 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 | `apify/google-trends-scraper` | Google Trends data |
|
|
| Hashtag tracking | `apify/instagram-hashtag-scraper` | Hashtag content |
|
|
| Hashtag metrics | `apify/instagram-hashtag-stats` | Performance stats |
|
|
| Visual trends | `apify/instagram-post-scraper` | Post analysis |
|
|
| Trending discovery | `apify/instagram-search-scraper` | Search trends |
|
|
| Comprehensive tracking | `apify/instagram-scraper` | Full data |
|
|
| API-based trends | `apify/instagram-api-scraper` | API access |
|
|
| Engagement trends | `apify/export-instagram-comments-posts` | Comment tracking |
|
|
| Product trends | `apify/facebook-marketplace-scraper` | Marketplace data |
|
|
| Visual analysis | `apify/facebook-photos-scraper` | Photo trends |
|
|
| Community trends | `apify/facebook-groups-scraper` | Group monitoring |
|
|
| YouTube Shorts | `streamers/youtube-shorts-scraper` | Short-form trends |
|
|
| YouTube hashtags | `streamers/youtube-video-scraper-by-hashtag` | Hashtag videos |
|
|
| TikTok hashtags | `clockworks/tiktok-hashtag-scraper` | Hashtag content |
|
|
| Trending sounds | `clockworks/tiktok-sound-scraper` | Audio trends |
|
|
| TikTok ads | `clockworks/tiktok-ads-scraper` | Ad trends |
|
|
| Discover page | `clockworks/tiktok-discover-scraper` | Discover trends |
|
|
| Explore trends | `clockworks/tiktok-explore-scraper` | Explore content |
|
|
| Trending content | `clockworks/tiktok-trends-scraper` | Viral content |
|
|
|
|
### Step 2: Fetch Actor Schema
|
|
|
|
Fetch the Actor's input schema and details dynamically using mcpc:
|
|
|
|
```bash
|
|
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:
|
|
1. **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
|
|
2. **Number of results**: Based on character of use case
|
|
|
|
### Step 4: Run the Script
|
|
|
|
**Quick answer (display in chat, no file):**
|
|
```bash
|
|
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
|
|
--actor "ACTOR_ID" \
|
|
--input 'JSON_INPUT'
|
|
```
|
|
|
|
**CSV:**
|
|
```bash
|
|
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:**
|
|
```bash
|
|
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`
|