apify-competitor-intelligence — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited apify-competitor-intelligence (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Analyze competitors using Apify Actors to extract data from multiple platforms.
(No need to check it upfront)
.env file with APIFY_TOKEN--env-file support)mcpc CLI tool: npm install -g @apify/mcpcCopy 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 findingsSelect 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 |
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:
Before running, ask:
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 csvJSON:
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 jsonAfter completion, report:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.