From BenAI Marketing
Build and weekly-refresh a branded HTML "Competitor Radar" dashboard that tracks a roster of competitors across YouTube, Instagram, LinkedIn, TikTok, community, and SEO. Use when the user wants to track competitors, monitor competitor socials/engagement/subscribers, build a competitor dashboard, or refresh the weekly competitor report. Gathers real data via connectors (YouTube, Apify, Firecrawl), renders a two-tab (Demo/Actual) dashboard in Ben AI branding, deploys it to a stable Vercel URL via git push, and posts the link to Slack.
How this skill is triggered — by the user, by Claude, or both
Slash command
/benai-marketing:competitor-radarThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Tracks a fixed roster of competitors weekly and renders one branded HTML dashboard: follower counts, posting cadence, median engagement, week-over-week subscriber growth, standout post of the week, and SEO, per platform. Two tabs: **Demo** (a sample niche) and **Actual** (real competitors, with a focus/blur toggle so only "you" shows on camera).
Tracks a fixed roster of competitors weekly and renders one branded HTML dashboard: follower counts, posting cadence, median engagement, week-over-week subscriber growth, standout post of the week, and SEO, per platform. Two tabs: Demo (a sample niche) and Actual (real competitors, with a focus/blur toggle so only "you" shows on camera).
config.json: the stable roster (who to track, handles per platform, platforms to include, Apify actor ids). Edit to add/remove competitors.radar_data.js: the weekly artifact. WEEK_ENDING, AV (base64 avatars, stable), and DATA ({demo, actual}). The refresh step rewrites this.assets/template.html: the fixed dashboard shell (CSS, render logic, tabs, focus mode). Never regenerate; carries a single /*__RADAR_DATA__*/ marker.scripts/build_dashboard.py: deterministic build (template + radar_data.js to index.html). No network.config.json (roster) and the current radar_data.js (last week's numbers, needed for week-over-week deltas).references/data-sources.md. Do NOT fabricate; mark missing as null.references/data-sources.md.radar_data.js with the new WEEK_ENDING and refreshed DATA. Handle avatars per references/data-sources.md.python3 scripts/build_dashboard.py <skill_dir> ../index.html.references/deploy.md.This skill is never finished. Improve it as you use it.
references/data-sources.md, references/deploy.md) or this SKILL.md so the correction sticks. Do not just fix it for this run.references/examples/ so it becomes a model for future runs.null and move on.radar_data.js (and config.json when the roster changes).npx claudepluginhub naveedharri/benai-skills --plugin benai-marketingSet someone up, from scratch, with their own weekly Competitor Radar dashboard. Use when a user wants to start tracking competitors, build their own competitor dashboard, monitor rivals' socials/SEO/subscribers, or "set me up with something like the competitor radar." Runs an interactive Q&A (niche, competitors, which platforms), can auto-discover and recommend competitors, wires up Apify + Firecrawl connectors, builds a branded HTML dashboard, deploys it to a stable Vercel URL, and schedules a weekly/monthly cloud routine to refresh and Slack it. This is the giveaway companion to the `competitor-radar` skill.
Scrapes and monitors competitors across web, SEO, and social channels, then synthesizes battle cards and digests. Use for competitor research or weekly monitoring.
Configures ongoing competitor monitoring across content, pricing, ads, social, SEO, and SERP dimensions with per-dimension scan frequencies and change detection alerts.