* 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.
132 lines
5.2 KiB
Markdown
132 lines
5.2 KiB
Markdown
---
|
|
name: apify-competitor-intelligence
|
|
description: Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.
|
|
---
|
|
|
|
# Competitor Intelligence
|
|
|
|
Analyze competitors 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 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:
|
|
|
|
```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., `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:
|
|
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 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`
|