Visits competitors' homepages, features, pricing, and blogs via Chrome MCP, generates structured Markdown competitive intelligence reports with summaries, snapshots, table, and actions, and saves to Google Drive for weekly pulses or deep dives.
From product-skillsnpx claudepluginhub amplitude/builder-skills --plugin product-skillsThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
A weekly competitive intelligence analyst — reads your competitor list, visits their sites, and writes you a report.
Staying on top of competitors manually means visiting dozens of pages, taking notes, and writing a summary — every week. This skill does all of it: pulls your competitor list from Drive, browses each competitor's key pages, and produces a structured Markdown report with a per-competitor snapshot and a recommended actions section.
/schedule Act as a competitive intelligence analyst for {{COMPANY_NAME}}, {{COMPANY_DESCRIPTION}}.
### Step 1 — Load the competitor list
Pull the competitor list from Google Drive. Check {{COMPETITORS_FOLDER}} and any file with
"competitor" or "landscape" in the name. If no list is found, note it and stop.
### Step 2 — Research each competitor
Use the Chrome MCP to visit each competitor's:
- Homepage — messaging, positioning, headline value prop
- Product / features page — new or changed capabilities
- Pricing page — tier names, price points, packaging changes
- Blog or changelog — recent posts, announcements, release notes
For each competitor, capture:
- Any messaging changes since the prior report (if available)
- New features or capabilities announced or shipped
- Pricing changes or new tiers
- Recent blog posts or announcements worth noting
- One "watch-out" — the single most important signal for us
### Step 3 — Write the report
## Executive Summary
2–3 sentences on the most important competitive development this week and what it means for us.
## Competitor Snapshots
One section per competitor:
**[Competitor Name]**
- Headline: One sentence on their current positioning
- New features: What they shipped or announced
- Pricing: Any changes, or "no change"
- Recent content: Blog posts or announcements worth reading
- Watch-out: The single thing we should pay attention to
## At-a-Glance Table
| Competitor | Biggest move this week | Pricing change | Watch-out |
|---|---|---|---|
## Recommended Actions
3–5 concrete things our team should do in response to this week's findings. Start each with a verb.
### Rules
- Save the report as Competitor-Report-YYYY-MM-DD.md to Google Drive at {{OUTPUT_FOLDER}}
- Return the Drive link when done
- If a competitor's site is unavailable, note it and skip — do not fabricate
- Keep the executive summary to 3 sentences maximum
| Field | Value |
|---|---|
| MCPs required | Google Drive, Chrome / Browser |
| Input | Competitor list in /Product/Competitors/ or any Drive file named with "competitor" |
| Output | Competitor-Report-YYYY-MM-DD.md → /Product/Competitors |
| Scheduler | Weekly, Monday 8am |
{{COMPANY_NAME}} — Your company name{{COMPANY_DESCRIPTION}} — One sentence on what you do and who you serve{{COMPETITORS_FOLDER}} — Drive path to your competitors folder, e.g. /Product/Competitors/{{OUTPUT_FOLDER}} — Where to save reports, e.g. /Product/Competitors/competitors.md in your Competitors folder listing URLs for each competitor's key pages — the skill uses it as a checklist.market-research-digest to weave competitor signals into broader market context.