Skip to content

ericrisco/rsc-harness / skills/competitor-watch

competitor-watch

Verified

Use when an already-named set of rivals is watched on a cadence — pricing, features, positioning and changelog diffed into a maintained tracker plus an append-only, classified change log. NOT sizing the market or choosing who the rivals are (that is `market-research`), NOT one-off page extraction (that is `data-scraper`).

FileKindSize
SKILL.mdskill md12.3 KB
evals/README.mdmarkdown1.5 KB
evals/cases.yamlconfig4.0 KB
references/monitoring-config.mdmarkdown5.1 KB
references/tracker-schema.mdmarkdown5.2 KB
scripts/verify.shexecutablescript10.3 KB

references/tracker-schema.md

View on GitHub
# Tracker schema + a filled example

The tracker of record is three structured files under `02-DOCS/wiki/competitors/`. Raw
captures (the diffed HTML/JSON snapshots) go under `02-DOCS/raw/competitors/<rival>/`. The
rule that overrides everything: **a price or feature cell without a `source_url` + `date` is
not knowledge — leave it blank and say so.**

`02-DOCS/wiki/` is an OKF v0.1 bundle, so the one `.md` file here (the competitor profile)
carries YAML frontmatter with a non-empty `type:`; the two CSVs are data files, not OKF
documents. Any cross-references in the profile body use **standard markdown links** (e.g.
`[Beta](./beta.md)`), never wikilinks. See `../../harness/references/wiki-protocol.md`
"## Conventions".

## 1. Competitor profile (one file per rival)

Markdown front-matter + body. One per rival, named `02-DOCS/wiki/competitors/<rival>.md`.
The frontmatter is OKF v0.1 conformant: `type:` is the only required field (non-empty);
`title`/`description`/`tags`/`timestamp` are the recommended standard surface. All the
domain keys below (`name`, `positioning_source.date`, every `pricing_tiers[].date`, …) are
kept verbatim — OKF allows any extra key and `verify.sh` reads them, so adding the OKF
fields is purely additive.

```yaml
---
type: competitor
title: Acme
description: "Tracker of record for Acme — positioning, pricing tiers, and watched surfaces."
tags: [competitor, pricing-watch, feature-watch]
timestamp: 2026-05-28T00:00:00Z
name: Acme
positioning_line: "The all-in-one workspace for remote-first teams"
positioning_source: { url: "https://acme.com", date: "2026-05-28" }
segment: "SMB / mid-market SaaS"
watched_urls:
  - { axis: pricing,       url: "https://acme.com/pricing",   selector: ".price-amount",        cadence: "10m" }
  - { axis: feature,       url: "https://acme.com/changelog", selector: ".changelog li:first-child", cadence: "daily" }
  - { axis: positioning,   url: "https://acme.com",           selector: "h1.hero-title",        cadence: "weekly" }
  - { axis: team,          url: "https://acme.com/careers",   selector: ".jobs-count",          cadence: "weekly" }
pricing_tiers:
  - { tier: "Starter", amount: 0,  currency: USD, period: mo, source_url: "https://acme.com/pricing", date: "2026-05-28" }
  - { tier: "Pro",     amount: 59, currency: USD, period: mo, source_url: "https://acme.com/pricing", date: "2026-05-28" }
  - { tier: "Team",    amount: 99, currency: USD, period: mo, source_url: "https://acme.com/pricing", date: "2026-05-28" }
---

## Notes
Repositioned from "project tool" to "workspace" in Q2 2026 — see change log 2026-05-12.

## Related
- [Beta](./beta.md) — closest competing positioning; cross-watch their pricing moves.
```

Every `pricing_tiers` row and any feature claim must carry `source_url` + `date`. If you only
have the tier name but not a confirmed price, omit `amount` rather than guess.

## 2. Feature matrix (CSV)

Rows = features, columns = competitors, plus a sourcing column pair per competitor so
`verify.sh` can confirm each asserted cell is dated. Keep it at `02-DOCS/wiki/competitors/feature-matrix.csv`.

```csv
feature,acme_value,acme_source_url,acme_date,beta_value,beta_source_url,beta_date
SSO (SAML),Team plan,https://acme.com/pricing,2026-05-28,Enterprise only,https://beta.io/security,2026-05-29
API rate limit,1000 req/min,https://acme.com/docs/limits,2026-05-28,,,
Audit log,yes,https://acme.com/security,2026-05-28,yes,https://beta.io/security,2026-05-29
```

A blank `*_value` with blank source is honest ("we haven't confirmed it"). A non-blank value
with a blank source is a violation — that's an invented fact and `verify.sh` fails it.

## 3. Change log (CSV, append-only)

The time series. Never overwrite a row; each pass appends. Keep it at
`02-DOCS/wiki/competitors/change-log.csv`.

```csv
date,competitor,axis,url,old_value,new_value,materiality,action
2026-05-12,Acme,positioning,https://acme.com,"project tool","remote-first workspace",high,"flag to brand-voice — they moved into our lane"
2026-05-20,Acme,pricing,https://acme.com/pricing,$49/mo,$59/mo,high,"revisit our mid-tier vs theirs (route to pricing)"
2026-05-22,Acme,feature,https://acme.com/changelog,,"SSO on Team plan",medium,"note for product"
2026-05-29,Beta,team,https://beta.io/careers,12 roles,19 roles,low,"hiring sales — watch for go-to-market push"
```

Field rules (these are what `verify.sh` enforces):

- `axis` ∈ `{pricing, feature, positioning, messaging, team, other}` — exactly one.
- `materiality` ∈ `{high, medium, low}`.
- `url` and `date` are required on every row (the change is unverifiable without them).
- `old_value` may be blank for a *new* surface (first capture); `new_value` should not be blank.
- `action` is the next step or the route — empty action on a `high` row is a smell.

## End-to-end: one rival, one pass

1. Orient: Acme is in our vital-few list. Watch pricing (10m), changelog (daily), hero (weekly), careers (weekly).
2. Gather: capture `.price-amount` → reads `$59/mo` on the Pro tier.
3. Analyze: diff vs last stored capture (`$49/mo`) → changed.
4. Classify: `pricing`. Score: `high` (it's our competing tier).
5. Log: append the `2026-05-20` pricing row above.
6. Flag + route: high → route the pricing implication to `../pricing/SKILL.md`; you don't set our price.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall