---
name: competitor-news-intel
description: Research competitor news, organize developments by company and theme, and produce actionable competitive intelligence with impact assessment and follow-up recommendations. Use when the user asks for competitor monitoring, competitor news tracking, market watch summaries, or business intelligence from external updates. 中文触发词包括：竞品跟踪、竞对情报、竞品新闻、市场监听、舆情观察、竞品周报、最近竞品有什么动作。
category: Search & Intelligence
---

# Competitor News Intelligence

## Overview

This skill monitors and synthesizes competitor-related news into actionable business intelligence.

It is appropriate when the user needs more than a list of links. The output should explain:
- what happened
- why it matters
- who it affects
- what to monitor next

## Quick Start

When the user asks for competitor research or monitoring:

1. Confirm the competitor set
2. Confirm the time range and region
3. Clarify what kinds of events matter
4. Retrieve or review relevant information
5. Organize it into a structured intelligence brief with impact assessment

### 中文任务映射
- “跟踪一下最近竞品动态” → `collect` 或 `run`
- “做一份竞对周报” → `run`
- “最近竞品有什么动作” → `collect`
- “帮我长期监控这几个竞品” → `plan-recurring` + `schedule-job`
- “看下竞品最近有没有融资/发布新产品” → `collect` + category filtering


## Input Requirements

| Field | Required | Description |
|-------|----------|-------------|
| competitors | yes | Company names, brands, or product lines |
| objective | yes | Monitoring, weekly digest, event scan, strategic watch |
| time range | no | Today, past 7 days, month, quarter, custom |
| geography | no | Country, region, or market |
| event categories | no | Product launch, pricing, partnership, hiring, financing, regulation, PR, channel |
| output depth | no | Brief scan / standard intelligence / detailed watch |
| audience | no | Founder, strategy team, sales, product, leadership |

## Workflow Decision Tree

### Quick Monitoring Brief
Use this for short competitor update summaries.

### Standard Intelligence Brief
Use this for grouped event analysis with implications.

### Strategic Watch
Use this when the user wants patterns, momentum, and what to watch next.

### Recurring Monitoring
Use this when the user wants periodic competitor watch outputs. Pair with `schedule-job`.

## Instructions

### Step 1: Define monitoring scope
Clarify:
- which competitors matter most
- which kinds of events matter most
- what decision the monitoring should support

### Step 2: Gather evidence
Use available search skills such as `baidu-search` when current information is needed.

For each relevant update, capture:
- competitor
- date
- event type
- short description
- source

### Step 3: Classify events
Typical categories:
- product / feature launch
- pricing or packaging change
- partnership or channel move
- hiring or org change
- financing or M&A
- regulatory or compliance issue
- brand or PR movement

### Step 4: Assess impact
For each important event, explain:
- likely business impact
- urgency level
- affected function (sales, product, strategy, marketing)
- whether follow-up monitoring is needed

### Step 5: Produce intelligence output
Do not stop at listing news. Synthesize patterns across competitors when possible.

## Scripts

### CLI Usage

Use the following commands when you need stable structured outputs:

```bash
poetry run python skills/competitor-news-intel/scripts/intel_cli.py collect --input-json '<JSON>'
poetry run python skills/competitor-news-intel/scripts/intel_cli.py analyze --input-json '<JSON>' --output json
poetry run python skills/competitor-news-intel/scripts/intel_cli.py run --input-json '<JSON>' --output json
poetry run python skills/competitor-news-intel/scripts/intel_cli.py plan-recurring --input-json '<JSON>'
```

### Recommended Uses
- `collect` - gather candidate competitor developments
- `analyze` - classify, deduplicate, and assess impact from collected events
- `run` - complete end-to-end intelligence generation
- `plan-recurring` - generate a schedule-ready monitoring message for `schedule-job`
- Real-time collection requires `BAIDU_API_KEY`

```markdown
# Competitor News Intelligence Brief

## Summary
[Short overview of the competitive landscape during the period]

## Monitoring Scope
- Competitors:
- Time range:
- Geography:
- Key event categories:

## Key Developments
### [Competitor / Event]
- Date:
- Category:
- What happened:
- Why it matters:
- Impact level: Low / Medium / High
- Suggested follow-up:

## Cross-Competitor Patterns
- [Pattern]

## Risks and Opportunities for Us
- [Implication]

## Watch List
- [Item to keep monitoring]

## Source Log
- [Source] - [Date] - [Competitor] - [Headline or key point]
```

## Quality Checklist

Before finalizing, verify:
- the scope matches the requested competitors and timeframe
- event categories are consistent
- impact labels are justified, not arbitrary
- links or sources are attributable
- repeated news is de-duplicated
- the brief includes implications, not just headlines

## Fallback Strategy

If the evidence is sparse:
- return a lighter monitoring brief
- highlight missing visibility
- recommend additional competitors, keywords, or sources to track

## Related Skills

- `skills/baidu-search/SKILL.md` - retrieve current external information
- `skills/auto-daily-summary/SKILL.md` - condense larger result sets into shorter periodic summaries
- `skills/schedule-job/SKILL.md` - automate recurring competitor monitoring
- `skills/market-academic-insight/SKILL.md` - use when the task broadens into industry or technology research

## Examples

**User**: "帮我跟踪一下最近一周几家竞品的新闻"

Expected output:
- structured competitor brief
- event categorization
- impact assessment
- watch list

**User**: "做一份竞对情报周报"

Expected output:
- weekly summary
- grouped developments
- cross-competitor patterns
- implications for our team

**User**: "最近竞品有什么动作？"

Expected output:
- recent developments
- event categories
- impact notes

**User**: "帮我长期监控这几个竞品"

Expected output:
- monitoring structure
- recommendation to combine with `schedule-job`
- suggested recurring payload

**User**: "看下竞品最近有没有融资或者发新品"

Expected output:
- filtered developments
- impact assessment
- follow-up watch list