competitor-watch — Claude Code skill: what it does, how to install
competitor-watch tracks market competitors and new entrants by fusing internal interaction logs with web search results.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install littlebird-toolkit@wasp-nestWhat competitor-watch does
The skill spots competitor momentum inside notes, meeting transcripts, and direct messages. Instead of tracking a pre-selected roster of URLs, it identifies newly surfacing names from conversations. Mentions surging from zero to four count as critical movement, while stagnant high volumes get deprioritized.
Operation relies on Littlebird MCP methods querying context snapshots, meeting summaries, and routine records. When external web retrieval tools exist in the session, it reconciles private signals against public sources. If web tools are missing, it delivers only the internal scan and notes the omission.
Without an active Littlebird Power or Pro plan, the skill halts immediately because the search_user_context tool is mandatory. Routine sweeps run on a weekly schedule, timed before Monday morning calls.
What it helps with
- spot unlisted entrants emerging across team communications
- reconcile sales call transcripts against public web data
- measure mention velocity rather than absolute mention volume
- automate weekly market intelligence briefs
Example prompts for the agent
- Run the weekly competitive digest for market changes since last week
- Deep dive on COMPETITOR across past meetings and messages
- Check our recent call summaries for newly mentioned tools
How to install competitor-watch
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install littlebird-toolkit@wasp-nestThis installs the whole littlebird-toolkit plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill competitor-watch -a claude-code3Manually: put the files in place
~/.claude/skills/competitor-watch/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competitor-watch/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill competitor-watch -a codex2Manually: put the files in place
.agents/skills/competitor-watch/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill competitor-watch -a cursor2Manually: put the files in place
.cursor/skills/competitor-watch/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/littlebird-toolkit/skills/competitor-watch2Manually: put the files in place
.github/skills/competitor-watch/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill competitor-watch -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/littlebird-toolkit/skills/competitor-watchManually: put the files in place
.devin/skills/competitor-watch/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competitor-watch
How to install competitor-watch in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools to register the marketplace catalog. Then install the package by running /plugin install littlebird-toolkit@wasp-nest.
What does competitor-watch do?
It aggregates competitor references from user meetings, messages, and snapshots, pairing them with live web research. The process highlights market shifts and newcomers rather than repeating known enterprise names.
What prerequisites does competitor-watch need?
It requires the Littlebird MCP connected with an active Power or Pro subscription to access search_user_context. Web fetch and search tools in the agent session are also recommended to complete external reconciliation.