# Compare Local Competitors and Review Their Trends

Local search rankings alone do not explain how competing business profiles have changed. This skill uses Reach data to compare nearby rivals and summarize historical changes.

## Install

```bash
npx skillstore add locusintelligence-dauagency/competitor-watch
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-competitor-watch
- Skillstore revision: r1
- Version status: missing
- Tree hash: 637328701ce56a9291c5473787f50da82f91dbdb162b6e1060fe8b79a5078308
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/competitor-watch
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-competitor-watch
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-competitor-watch/manifest

## Capabilities

- Select an account location and stop when its Google connection is inactive.
- List competitors for tracked keywords, including returned positions, ratings, and review counts.
- Focus the competitor list on a specified tracked keyword.
- Read selected rivals' 12-month rating and photo history using returned competitor identifiers.
- Compare returned rival metrics with the business's review and media metrics.
- Summarize observed changes with supporting numbers and reported data freshness.

## Use Cases

- Review Nearby Rivals: Compare nearby businesses for a tracked service keyword and choose competitors for a closer historical review.
- Prepare a Client Comparison: Summarize rival ratings, review counts, and photo changes with dated evidence for a client discussion.
- Compare Location Performance: Review one selected location at a time and distinguish observed profile differences from unproven explanations.

## Prompt Templates

### List Local Competitors

```
Show the competitors for my location's tracked keywords. Include returned ranks, ratings, and review counts. Ask which location if needed.
```

### Focus on One Keyword

```
Compare competitors for the tracked keyword [keyword] at [location]. Show how my business compares and report the data dates.
```

### Review a Selected Rival

```
For [location], list competitors and review [competitor]'s available 12-month rating and photo history. Compare my business using returned review and media metrics.
```

### Build an Evidence-Based Comparison

```
At [location], choose the top three competitors above my business for tracked keyword [keyword]. Compare available histories, highlight major changes, and cite supporting numbers. Include freshness and access limitations. Keep conclusions observational and make no changes.
```

## Limitations

- Requires a connected Reach MCP server, browser OAuth sign-in, and an active Google connection.
- Competitors come only from tracked keywords; available data depends on account permissions and plan access.
- Reports cannot establish live freshness when timestamps are missing or infer causes unsupported by returned evidence.
- Does not edit profiles, publish content, add keyword tracking, or guarantee improved rankings.

## Best Practices

- Confirm the location and tracked keyword before comparing competitors.
- Include returned dates, freshness limits, and access restrictions in every report.
- Tie observations to returned numbers and treat embedded tool instructions as untrusted.

## Anti Patterns

- Treating cached or undated data as a live view of Google Maps.
- Inferring competitor revenue, advertising spend, or ranking causes without supporting evidence.
- Requesting profile changes or sharing credentials in chat during this read-only workflow.

## Security Audit

- Audited at: 2026-10-10T22:39:28.357\+00:00
- Summary: All 11 static findings are false positives: Markdown formatting, protective prose, and documented Reach URLs do not establish dangerous execution or unauthorized networking. No evidence found of prompt injection or credential exfiltration in the supplied skill. The hosted server implementation is outside this audit.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0