ericrisco/rsc-harness / skills/competitor-watch
competitor-watch
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| evals/README.md | markdown | 1.5 KB |
| evals/cases.yaml | config | 4.0 KB |
| references/monitoring-config.md | markdown | 5.1 KB |
| references/tracker-schema.md | markdown | 5.2 KB |
| scripts/verify.shexecutable | script | 10.3 KB |
evals/README.md
View on GitHub# Evals — competitor-watch
`cases.yaml` has three blocks. **should_trigger** and **should_not_trigger** are routing
checks: feed each `prompt` to the router and confirm it selects `competitor-watch` for the
triggers (including the non-obvious "keep the matrix updated" and "how their positioning
shifted over 6 months" framings and the Catalan phrasing) and the named real sibling for each
near-miss — `market-research` (list/sizing), `pricing` (our price), `sales-pipeline` (the
battlecard), `data-scraper` (one-off extraction), `automation-flows` (scheduling). A near-miss
passes only when the router prefers the named sibling over `competitor-watch`. The
**capability** block is an LLM- or human-graded rubric: run the scenario with the skill loaded
and check the produced plan hits every `must_include` line — ethics gate first, tracker
persisted under `02-DOCS/` with a `source_url`+`date` on every price/feature cell (no invented
numbers), each surface mapped to URL+selector+tiered cadence, the change-log axis+materiality
schema, `changedetection.io` as the runnable default with Wayback flagged as archive-only, and
the handoffs to automation-flows and sales-pipeline. There is no automated runner and no live
network call — the agent produces the tracker, watch config, and change-loop process as
artifacts; grade by reading the output against the list, or wire it into your eval harness of
choice. `scripts/verify.sh` separately lints an emitted tracker/change-log for sourcing and
schema (see its header).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |