apify-competitor-intelligence
Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- apify-competitor-intelligence
- risk
- unknown
- source
- community
- description
- Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.
02 资源文件 1
- 脚本reference/scripts/run_actor.js11.5 KB
03 SKILL.md 正文
Competitor Intelligence
Analyze competitors using Apify Actors to extract data from multiple platforms.
When to Use
- You need competitor benchmarks for content, reviews, pricing, ads, audience, or channel performance.
- The task involves selecting Apify Actors to compare competitors across maps, booking, social, or video platforms.
- You need structured competitor data plus synthesized takeaways for strategy or positioning.
Prerequisites
(No need to check it upfront)
.envfile withAPIFY_TOKEN- Node.js 20.6+ (for native
--env-filesupport) mcpcCLI tool:npm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify competitor analysis 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 Competitor Analysis Type
Select the appropriate Actor based on analysis needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Competitor business data | compass/crawler-google-places |
Location analysis |
| Competitor contact discovery | poidata/google-maps-email-extractor |
Email extraction |
| Feature benchmarking | compass/google-maps-extractor |
Detailed business data |
| Competitor review analysis | compass/Google-Maps-Reviews-Scraper |
Review comparison |
| Hotel competitor data | voyager/booking-scraper |
Hotel benchmarking |
| Hotel review comparison | voyager/booking-reviews-scraper |
Review analysis |
| Competitor ad strategies | apify/facebook-ads-scraper |
Ad creative analysis |
| Competitor page metrics | apify/facebook-pages-scraper |
Page performance |
| Competitor content analysis | apify/facebook-posts-scraper |
Post strategies |
| Competitor reels performance | apify/facebook-reels-scraper |
Reels analysis |
| Competitor audience analysis | apify/facebook-comments-scraper |
Comment sentiment |
| Competitor event monitoring | apify/facebook-events-scraper |
Event tracking |
| Competitor audience overlap | apify/facebook-followers-following-scraper |
Follower analysis |
| Competitor review benchmarking | apify/facebook-reviews-scraper |
Review comparison |
| Competitor ad monitoring | apify/facebook-search-scraper |
Ad discovery |
| Competitor profile metrics | apify/instagram-profile-scraper |
Profile analysis |
| Competitor content monitoring | apify/instagram-post-scraper |
Post tracking |
| Competitor engagement analysis | apify/instagram-comment-scraper |
Comment analysis |
| Competitor reel performance | apify/instagram-reel-scraper |
Reel metrics |
| Competitor growth tracking | apify/instagram-followers-count-scraper |
Follower tracking |
| Comprehensive competitor data | apify/instagram-scraper |
Full analysis |
| API-based competitor analysis | apify/instagram-api-scraper |
API access |
| Competitor video analysis | streamers/youtube-scraper |
Video metrics |
| Competitor sentiment analysis | streamers/youtube-comments-scraper |
Comment sentiment |
| Competitor channel metrics | streamers/youtube-channel-scraper |
Channel analysis |
| TikTok competitor analysis | clockworks/tiktok-scraper |
TikTok data |
| Competitor video strategies | clockworks/tiktok-video-scraper |
Video analysis |
| Competitor TikTok profiles | clockworks/tiktok-profile-scraper |
Profile data |
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., compass/crawler-google-places).
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 competitors analyzed
- File location and name
- Key competitive insights
- Suggested next steps (deeper analysis, benchmarking)
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
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.