From awesome-skills
Tracks reviews, ratings, sentiment, and brand mentions across Google Maps, Booking.com, TripAdvisor, Facebook, Instagram, YouTube, TikTok using Apify Actors. Useful for monitoring brand reputation and analyzing customer feedback.
npx claudepluginhub apify/awesome-skills --plugin apify-ecommerceThis skill uses the workspace's default tool permissions.
Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.
Scrapes reviews, ratings, and brand mentions from Google Maps, Facebook, Instagram, TripAdvisor, and other platforms using Apify Actors for reputation monitoring.
Scrapes data from Instagram, Facebook, TikTok, YouTube, LinkedIn, Google Maps, Reddit, and 15+ platforms using Apify CLI actors for lead generation, monitoring, analysis, and extraction tasks.
Conducts market research via Apify Actors scraping Google Maps, Facebook, Instagram, Booking.com, TripAdvisor for market density, pricing, consumer behavior, and geographic opportunities.
Share bugs, ideas, or general feedback.
Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.
(No need to check it upfront)
.env file with APIFY_TOKEN--env-file support)Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Determine data source (select Actor)
- [ ] Step 2: Fetch Actor schema
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the monitoring script
- [ ] Step 5: Summarize results
Select the appropriate Actor based on user needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Google Maps reviews | compass/crawler-google-places | Business reviews, ratings |
| Google Maps review export | compass/Google-Maps-Reviews-Scraper | Dedicated review scraping |
| Booking.com hotels | voyager/booking-scraper | Hotel data, scores |
| Booking.com reviews | voyager/booking-reviews-scraper | Detailed hotel reviews |
| TripAdvisor reviews | maxcopell/tripadvisor-reviews | Attraction/restaurant reviews |
| Facebook reviews | apify/facebook-reviews-scraper | Page reviews |
| Facebook comments | apify/facebook-comments-scraper | Post comment monitoring |
| Facebook page metrics | apify/facebook-pages-scraper | Page ratings overview |
| Facebook reactions | apify/facebook-likes-scraper | Reaction type analysis |
| Instagram comments | apify/instagram-comment-scraper | Comment sentiment |
| Instagram hashtags | apify/instagram-hashtag-scraper | Brand hashtag monitoring |
| Instagram search | apify/instagram-search-scraper | Brand mention discovery |
| Instagram tagged posts | apify/instagram-tagged-scraper | Brand tag tracking |
| Instagram export | apify/export-instagram-comments-posts | Bulk comment export |
| Instagram comprehensive | apify/instagram-scraper | Full Instagram monitoring |
| Instagram API | apify/instagram-api-scraper | API-based monitoring |
| YouTube comments | streamers/youtube-comments-scraper | Video comment sentiment |
| TikTok comments | clockworks/tiktok-comments-scraper | TikTok sentiment |
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., compass/crawler-google-places).
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