跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

competitor-watch

Track competitors from Littlebird sightings and public sources. Use for watchlists, new entrants, or weekly market deltas. Read README.md for the guide map.

Mario Aldayuz / Littlebird · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add legioncodeinc/vibe-coding-tools --skill competitor-watch

技能说明


name: competitor-watch description: "Track competitors from Littlebird sightings and public sources. Use for watchlists, new entrants, or weekly market deltas. Read README.md for the guide map." license: AGPL-3.0-or-later compatibility: Claude Cowork, Claude Code 2.1 or newer, Cursor 2.4 or newer, Codex metadata: hive-tier: standalone version: "1.0.0" author: "Mario Aldayuz / Littlebird" requires: "Littlebird MCP (Power or Pro plan), plus any web search and fetch tools available in the session"

Competitor watch

Start with README.md for the workflow map and detailed references.

Competitive and market intelligence built from what actually crossed your screen, fused with external monitoring.

The thing this does that nothing else does. Every competitive intelligence product in the category monitors a supplied list of names and URLs, and two of them literally bill per competitor tracked. That model cannot surface a name nobody typed in, and it cannot tell you what your market is talking about this week. This skill reads your own field of view. A competitor that turns up three times in one week across a client call, a community thread, and a friend's screenshot is a signal no URL monitor produces. That is the spine of the skill, and the sightings log, the velocity ranking, and the new-entrant detection all exist to serve it.

It is not another news digest. If the external half is all that runs, say so and say why.

Purpose

Keep a named set of competitors and market shifts under observation on a weekly beat, built first from what actually crossed the user's screen and only then from external monitoring, so the output is what moved in this user's market rather than what a press release said.

Three failures it exists to prevent:

  1. The list nobody can leave. URL monitors only see names somebody already typed in. A competitor entering the field of view for the first time is invisible to them, so new-entrant detection is a first-class output here rather than a feature.
  2. Volume mistaken for velocity. Ten steady mentions is not news. Zero to four is. Ranking by raw count produces a digest that reports the same three incumbents forever.
  3. The manufactured week. A recurring digest that invents analysis to fill a quiet period earns its way into the ignored pile. A quiet week gets one line.

Capability gate

List the tools available in this session and use the real tool names. Do not assume the names in this file are spelled the way your session spells them, and do not assume a tool exists because it is named here.

  • Required: the Littlebird MCP, on a Power or Pro plan. If search_user_context is not available, the MCP is not connected. Stop and tell the user. There is no degraded mode worth shipping: without the internal half this is a web search with extra ceremony, and the user deserves to be told that rather than handed one.
  • Expected: whatever web search and fetch tools the session carries. Sessions differ. List them and use the real names. If none are present, produce the internal half in full, mark the external and reconciliation sections as unrun with the reason, and say plainly that reconciliation is the section that needed both halves.
  • Plan check: LB_INTERNAL_GET_SUBSCRIPTION_STATUS when you need to explain a routine limit or a capability gate to the user.

Littlebird MCP calls used

CallUsed for
search_user_context with filters: {"data_source": "snapshots"}Pass 1, one query per Tier 1 entity: primary name plus strongest alias plus the disambiguation term. Pass 2, category-shaped queries that name no entity, which is what surfaces untracked names
search_user_context with filters: {"data_source": "messages"} via search_queries_messagesPass 3. The same entity names, against what people are telling the user directly
search_user_context with filters: {"data_source": "summaries"}Pass 5, optional. The compressed day view, used to find windows worth sweeping in detail on a backfill
LB_INTERNAL_SEARCH_MEETINGS with queryPass 4. Competitor names as topic queries, plus shortlist language: also looking at, who else are you talking to, currently using. Topic lookup, not name lookup
LB_INTERNAL_GET_MEETING with meeting_idThe structured summary for any meeting hit, read before the transcript. Attribution comes from the owner-tagged Decisions and Action Items blocks, never from chunks tagged [Others]
LB_INTERNAL_GET_MEETING_TRANSCRIPT with meeting_idWording only, for a line the summary already located and already attributed
LB_INTERNAL_GET_ROUTINE_REPORTS with routine_id and limitThe weekly routine's own past reports. Read before any sweep, by the routine and by the on-demand deep dive alike, so neither restates what the user already read
LB_INTERNAL_CREATE_ROUTINE with title, prompt, schedule, notifications_enabled, email_notifications_enabledCreates the weekly digest, from an interactive session, after the user approves the prompt text
LB_INTERNAL_GET_ROUTINE_CONFIG then LB_INTERNAL_UPDATE_ROUTINE with routine_idEditing the routine. prompt and schedule each replace the whole value, so always read the current config first
LB_INTERNAL_GET_SUBSCRIPTION_STATUSPlan check before offering to create the routine. Routine count is plan-limited

Every search_user_context call carries date_range: week by week for the digest, month by month for a backfill. At most 7 queries per call, split across parallel calls rather than widened into one.

External monitoring runs on whatever web search and fetch tools the session actually carries. There is no Littlebird web search tool. List the session's tools and use their real names.

Trigger

  • "competitive intelligence", "what are our competitors doing", "competitor tracking"
  • "weekly competitive digest", "what move
阅读完整来源 ↗