CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-monitoring

Visit each competitor's homepage, features page, pricing page, and blog using Chrome MCP, then write a structured competitive intelligence report saved to Google Drive. Use for a standing weekly competitive pulse or an on-demand deep-dive.

73

Quality

67%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./product-skills/skills/competitor-monitoring/SKILL.md
SKILL.md
Quality
Evals
Security

Competitor Monitoring

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.


Prompt Template

/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

Setup

FieldValue
MCPs requiredGoogle Drive, Chrome / Browser
InputCompetitor list in /Product/Competitors/ or any Drive file named with "competitor"
OutputCompetitor-Report-YYYY-MM-DD.md/Product/Competitors
SchedulerWeekly, Monday 8am

Placeholders to fill in

  • {{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/

Tips

  • Keep a competitors.md in your Competitors folder listing URLs for each competitor's key pages — the skill uses it as a checklist.
  • The "Watch-out" column in the at-a-glance table is the fastest way to scan for urgency in a busy week.
  • Pair with market-research-digest to weave competitor signals into broader market context.
  • If competitors have public changelogs (e.g. Linear, Notion), add the changelog URL to your competitor list for the most reliable feature tracking.
Repository
amplitude/builder-skills
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.