# AI News Aggregator Sl

> Fetches AI & tech news (default) or any custom topic (crypto, geopolitics, etc.) from RSS feeds, Tavily search, Twitter/X, and YouTube. Writes an English editorial digest using DeepSeek AI and posts it to Discord. Supports any time range (today, last 3 days, last week). Trigger when user asks for news, a digest, trending topics, or YouTube updates on any subject.

- Skill: `dvcrn/ai-news-aggregator-sl` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add dvcrn/ai-news-aggregator-sl`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/ai-news-aggregator-sl/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/dvcrn/ai-news-aggregator-sl

---


# 🦞 AI News Aggregator

Collects news on any topic, writes an English editorial digest via DeepSeek AI, and posts it to Discord.

**Default (AI topic):** TechCrunch · The Verge · NYT Tech (RSS) + curated AI YouTube channels
**Custom topics:** Tavily news search + YouTube topic search (no Shorts, sorted by views)

---

## Network Endpoints

| Endpoint | Purpose | Condition |
|----------|---------|-----------|
| `https://api.deepseek.com/chat/completions` | AI editorial summarisation | Always (required) |
| `https://discord.com/api/webhooks/...` | Post digest to Discord | Always (required) |
| `https://techcrunch.com/.../feed/` | RSS news (AI topic) | Default AI topic only |
| `https://www.theverge.com/rss/...` | RSS news (AI topic) | Default AI topic only |
| `https://www.nytimes.com/svc/collections/...` | RSS news (AI topic) | Default AI topic only |
| `https://api.tavily.com/search` | Custom topic news search | Only if `TAVILY_API_KEY` set |
| `https://api.twitterapi.io/twitter/tweet/advanced_search` | Twitter search | Only if `TWITTERAPI_IO_KEY` set |
| `https://www.googleapis.com/youtube/v3/...` | YouTube search | Only if `YOUTUBE_API_KEY` set |

The script does **not** contact OpenAI endpoints. The `openai` package is used solely as an HTTP client pointed at `https://api.deepseek.com`. `OPENAI_API_KEY` is explicitly removed from the environment at startup.

---

## Usage Examples

- "Get today's AI news"
- "Collect news about crypto"
- "Last week's news about climate change"
- "What's trending in AI today?"
- "Get crypto news from the last 3 days"
- "Show me recent Bitcoin YouTube videos"
- "AI news dry run" *(preview without posting to Discord)*
- "Test my Discord webhook"

---

## Required API Keys

| Key | Required | Where to get it |
|-----|----------|----------------|
| `DEEPSEEK_API_KEY` | ✅ | [platform.deepseek.com/api_keys](https://platform.deepseek.com/api_keys) |
| `DISCORD_WEBHOOK_URL` | ✅ | Discord → Channel Settings → Integrations → Webhooks → Copy URL |
| `TAVILY_API_KEY` | For custom topics | [app.tavily.com](https://app.tavily.com) |
| `TWITTERAPI_IO_KEY` | Optional | [twitterapi.io](https://twitterapi.io) |
| `YOUTUBE_API_KEY` | Optional | [console.cloud.google.com](https://console.cloud.google.com) → YouTube Data API v3 |

---

## Implementation

**IMPORTANT:** Always run `news_aggregator.py` using the steps below. Do NOT search the web manually or improvise a response — the script handles all fetching, summarisation, and Discord posting.

### Step 1 — Locate the script

The script is bundled with this skill. Find it:

```bash
SKILL_DIR=$(ls -d ~/.openclaw/skills/ai-news-aggregator-sl 2>/dev/null || ls -d ~/.openclaw/skills/news-aggregator 2>/dev/null)
SCRIPT="$SKILL_DIR/news_aggregator.py"
echo "Script: $SCRIPT"
ls "$SCRIPT"
```

### Step 2 — Check uv is available

```bash
which uv && uv --version || echo "uv not found"
```

If `uv` is not found, ask the user to install it from their system package manager or from [https://docs.astral.sh/uv/getting-started/installation/](https://docs.astral.sh/uv/getting-started/installation/). Do not run a curl-pipe-sh command on the user's behalf.

### Step 3 — API keys

The env vars `DEEPSEEK_API_KEY` and `DISCORD_WEBHOOK_URL` are passed automatically by OpenClaw from its config. No `.env` file is needed.

Verify they are set (without revealing values):

```bash
[[ -n "$DEEPSEEK_API_KEY" ]] && echo "DEEPSEEK_API_KEY: set" || echo "DEEPSEEK_API_KEY: MISSING"
[[ -n "$DISCORD_WEBHOOK_URL" ]] && echo "DISCORD_WEBHOOK_URL: set" || echo "DISCORD_WEBHOOK_URL: MISSING"
```

If either is missing, ask the user to run:
```
openclaw config set env.DEEPSEEK_API_KEY '<key>'
openclaw config set env.DISCORD_WEBHOOK_URL '<url>'
```

### Step 4 — Parse the request

Extract **topic** and **days** from what the user said:

| User said | --topic | --days |
|-----------|---------|--------|
| "AI news" / "tech news" / nothing specific | *(omit — default AI)* | 1 |
| "crypto news" | `--topic "crypto"` | 1 |
| "news about climate change" | `--topic "climate change"` | 1 |
| "last week's crypto news" | `--topic "crypto"` | 7 |
| "last 3 days of Bitcoin news" | `--topic "Bitcoin"` | 3 |
| "yesterday's AI news" | *(omit topic)* | 1 |
| "this week in AI" | *(omit topic)* | 7 |

For report type:

| User said | flag to add |
|-----------|-------------|
| "news" / "articles" / "digest" | `--report news` |
| "trending" / "Twitter" / "YouTube" | `--report trending` |
| "dry run" / "preview" / "don't post" | `--dry-run` |
| "test Discord" / "test webhook" | `--test-discord` |
| anything else | *(omit — runs all)* |

### Step 5 — Run with uv

`uv run` automatically installs all dependencies from the script's inline metadata — no venv setup needed.

```bash
uv run "$SCRIPT" [--topic "TOPIC"] [--days N] [--report TYPE] [--dry-run]
```

Examples:

```bash
# AI news today (default)
uv run "$SCRIPT"

# Crypto news, last 7 days
uv run "$SCRIPT" --topic "crypto" --days 7

# Trending AI on Twitter and YouTube
uv run "$SCRIPT" --report trending

# Preview without posting to Discord
uv run "$SCRIPT" --topic "Bitcoin" --dry-run

# Test webhook connection
uv run "$SCRIPT" --test-discord
```

### Step 6 — Report back

Tell the user what was posted to Discord, how many items were found per source, and note any skipped sources (e.g. "YouTube skipped — YOUTUBE_API_KEY not set").