From awesome-skills
Scrapes and analyzes audience demographics, preferences, behavior patterns, and engagement quality from Facebook, Instagram, YouTube, and TikTok using Apify Actors.
npx claudepluginhub apify/awesome-skills --plugin apify-ecommerceThis skill uses the workspace's default tool permissions.
Analyze and understand your audience using Apify Actors to extract follower demographics, engagement patterns, and behavior data from multiple platforms.
Analyzes audience demographics, engagement patterns, and behavior on Facebook, Instagram, YouTube, TikTok using Apify Actors and mcpc CLI. Useful for extracting social media insights via targeted scrapers.
Tracks engagement metrics, ROI, and content performance across Instagram, Facebook, YouTube, TikTok using Apify Actors. Guides scraper selection, schema fetching, and Node.js-based analysis workflows.
Analyzes audience demographics, engagement patterns, and follower behavior on Instagram, YouTube, LinkedIn via anysite MCP server. Useful for influencer validation, content optimization, and target audience profiling.
Share bugs, ideas, or general feedback.
Analyze and understand your audience using Apify Actors to extract follower demographics, engagement patterns, and behavior data from multiple platforms.
(No need to check it upfront)
.env file with APIFY_TOKEN--env-file support)Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify audience analysis type (select Actor)
- [ ] Step 2: Fetch Actor schema
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findings
Select the appropriate Actor based on analysis needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Facebook follower demographics | apify/facebook-followers-following-scraper | FB followers/following lists |
| Facebook engagement behavior | apify/facebook-likes-scraper | FB post likes analysis |
| Facebook video audience | apify/facebook-reels-scraper | FB Reels viewers |
| Facebook comment analysis | apify/facebook-comments-scraper | FB post/video comments |
| Facebook content engagement | apify/facebook-posts-scraper | FB post engagement metrics |
| Instagram audience sizing | apify/instagram-profile-scraper | IG profile demographics |
| Instagram location-based | apify/instagram-search-scraper | IG geo-tagged audience |
| Instagram tagged network | apify/instagram-tagged-scraper | IG tag network analysis |
| Instagram comprehensive | apify/instagram-scraper | Full IG audience data |
| Instagram API-based | apify/instagram-api-scraper | IG API access |
| Instagram follower counts | apify/instagram-followers-count-scraper | IG follower tracking |
| Instagram comment export | apify/export-instagram-comments-posts | IG comment bulk export |
| Instagram comment analysis | apify/instagram-comment-scraper | IG comment sentiment |
| YouTube viewer feedback | streamers/youtube-comments-scraper | YT comment analysis |
| YouTube channel audience | streamers/youtube-channel-scraper | YT channel subscribers |
| TikTok follower demographics | clockworks/tiktok-followers-scraper | TT follower lists |
| TikTok profile analysis | clockworks/tiktok-profile-scraper | TT profile demographics |
| TikTok comment analysis | clockworks/tiktok-comments-scraper | TT comment engagement |
Fetch the Actor's input schema and details:
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/fetch_actor_details.js --actor "ACTOR_ID"
Replace ACTOR_ID with the selected Actor (e.g., apify/facebook-followers-following-scraper).
This returns:
Skip this step for simple lookups (e.g., "what's Nike's follower count?", "find me 5 coffee shops in Prague") — just use quick answer mode and move to Step 4.
For larger scraping tasks, ask:
Cost safety: Always set a sensible result limit in the Actor input (e.g., maxResults, resultsLimit, maxCrawledPages, or equivalent field from the input schema). Default to 100 results unless the user explicitly asks for more. Warn the user before running large scrapes (1000+ results) as they consume more Apify credits.
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
After completion, report:
APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_token
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