apify-competitor-intelligence
Original:🇺🇸 English
Not Translated
2 scripts
Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.
1installs
Sourceapify/awesome-skills
Added on
NPX Install
npx skill4agent add apify/awesome-skills apify-competitor-intelligenceSKILL.md Content
Competitor Intelligence
Analyze competitors 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
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify competitor 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 findingsStep 1: Identify Competitor Analysis Type
Select the appropriate Actor based on analysis needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Competitor business data | | Location analysis |
| Competitor contact discovery | | Email extraction |
| Feature benchmarking | | Detailed business data |
| Competitor review analysis | | Review comparison |
| Hotel competitor data | | Hotel benchmarking |
| Hotel review comparison | | Review analysis |
| Competitor ad strategies | | Ad creative analysis |
| Competitor page metrics | | Page performance |
| Competitor content analysis | | Post strategies |
| Competitor reels performance | | Reels analysis |
| Competitor audience analysis | | Comment sentiment |
| Competitor event monitoring | | Event tracking |
| Competitor audience overlap | | Follower analysis |
| Competitor review benchmarking | | Review comparison |
| Competitor ad monitoring | | Ad discovery |
| Competitor profile metrics | | Profile analysis |
| Competitor content monitoring | | Post tracking |
| Competitor engagement analysis | | Comment analysis |
| Competitor reel performance | | Reel metrics |
| Competitor growth tracking | | Follower tracking |
| Comprehensive competitor data | | Full analysis |
| API-based competitor analysis | | API access |
| Competitor video analysis | | Video metrics |
| Competitor sentiment analysis | | Comment sentiment |
| Competitor channel metrics | | Channel analysis |
| TikTok competitor analysis | | TikTok data |
| Competitor video strategies | | Video analysis |
| Competitor TikTok profiles | | Profile data |
Step 2: Fetch Actor Schema
Fetch the Actor's input schema and details:
bash
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/fetch_actor_details.js --actor "ACTOR_ID"Replace with the selected Actor (e.g., ).
ACTOR_IDcompass/crawler-google-placesThis returns:
- Actor info (title, description, URL, categories, stats, rating)
- README summary
- Input schema (required and optional parameters)
Step 3: Ask User Preferences
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:
- 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
Cost safety: Always set a sensible result limit in the Actor input (e.g., , , , 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.
maxResultsresultsLimitmaxCrawledPagesStep 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 csvJSON:
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 jsonStep 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.envAPIFY_TOKEN=your_tokenActor not foundRun FAILEDTimeout--timeout