Glasser Competitor Research

View saved version →

---
name: competitor-research
description: When the user wants to understand a competitor in depth — who is behind it, how it is funded, what it sells and how it positions itself, what it hires for, where its traffic and search visibility come from, and where it advertises — or to compare several competitors side by side. Also use when the user mentions "competitor research", "competitive analysis", "who are our competitors", "compare us with", "what is [company] doing", "how much has [company] raised", "what is [company] hiring for", or gives competitor names or domains. Input is the competitors by name or domain, optionally the user's own product; output is one profile per competitor and a comparison when there are several. Runs on this plugin's Glasser Competitor Research tools.
metadata:
  version: "0.1.0"
  category: research
---

# Competitor research

This skill uses this plugin's `glasser-competitor` MCP connection. Connect a Glasser account through the host's connection flow if the tools are unavailable. No CLI installation or other plugin is required.

Use the dedicated tools below for all data. If they cannot supply a dimension, record it as missing. Do not require another plugin to complete a step.

## Inputs

- the competitors, by name or domain
- which dimensions matter (see the table below); the core set is the default
- the user's own product, optional — with it the report can say what the findings mean for them; without it the profiles stand alone and the "What this means" sections are omitted

If the user names their own product instead of competitors, the competitor set has to be settled before any research — use `find_similar_companies` for a shortlist and confirm it with the user; research on the wrong set costs more than the shortlist.

## Process

### 1. Resolve each competitor to one entity

For each name, establish the canonical domain, the operating entity, and whether it is independent, a subsidiary, or a renamed or acquired product. Use `search_web` to find the official site and `inspect_company` to confirm the entity. Names collide; do not guess between genuinely ambiguous candidates — every later call keys off this.

### 2. Choose the dimensions

Cost is competitors x dimensions, so do not run everything by default:

- **Core** — positioning, funding, team, hiring. Cheap, high signal.
- **On request** — traffic, SEO, ads, social, history. Estimate-based or priced per row; run when the question needs them.

Before a series of calls, create one stable `task_id`, tell the user what you will run — the competitors, the dimensions and the tools, with their current charging rules from `quote_competitor_calls` — and get their go-ahead. That go-ahead covers the stated scope; ask again only before expanding it.

### 3. Collect, in parallel

Only step 1 is a dependency. Past it every competitor-and-dimension pair stands alone, so fan out as wide as the environment allows.

Settle the tool, provider and parameters once per dimension and apply the same choice to every competitor; different sources or limits make results incomparable.

If a dimension has no tool, or is priced beyond what the user agreed to, record it as missing and move on — never fill a gap from memory. An empty result is not a gap; no funding on record is itself a finding.

## Dimensions and tools

| Dimension | What to pull | Tool | Notes |
|---|---|---|---|
| **Identity** | canonical domain, entity name, status | `search_web`, `inspect_company` | Search listings are leads, not facts; confirm with the company profile. |
| **Positioning** | homepage, pricing, product and customer pages | `read_page` | One URL per call, as markdown. |
| **Funding** | rounds, amounts, dates, investors, total raised | `inspect_funding` | No recorded round is a finding, not proof the company never raised. |
| **Team** | founders, executives, headcount | `list_team_members`, `inspect_company` | Founders by `job_titles`, executives by `seniorities`, as separate cal

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.