# AI Listening

Collect what is new in AI in the last 24 hours across X, Hugging Face, GitHub and...

- Repository: https://github.com/zhuyansen/new-term-radar (2017 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add zhuyansen/new-term-radar --skill ai-listening -g -a claude-code -y`
Codex: `npx skills add zhuyansen/new-term-radar --skill ai-listening -g -a codex -y`
Cursor: `npx skills add zhuyansen/new-term-radar --skill ai-listening -g -a cursor -y`
Gemini CLI: `npx skills add zhuyansen/new-term-radar --skill ai-listening -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add zhuyansen/new-term-radar`

## Description

Collect what is new in AI in the last 24 hours across X, Hugging Face, GitHub and sitemaps, deduplicated, as one report of names that are starting to surge. Use when the user asks what is new or trending in AI today, wants a daily AI listening report, or needs fresh names of models, products and repositories to feed keyword research. Runs the new-term-radar command line; needs an AISA_API_KEY.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# AI listening

Produce one report: the names of new AI models, products and repositories seen in the last 24 hours, where each was seen, and how strong the signal is. This is collection, not analysis. For search demand behind a name, hand the names to the `seo-new-keywords-research` skill.

## Before you run anything

1. Run the pinned release, never a clone of the repository: `uvx new-term-radar==0.6.1 <command> …` (uv fetches that version from PyPI into a throwaway environment; it needs Python 3.10 or newer and nothing else). Without uv: `python3 -m pip install new-term-radar==0.6.1`, then `new-term-radar <command> …`.
2. Run every command from one working directory, so yesterday's snapshots are there today: `$NEW_TERM_RADAR_DIR` if set, else `~/new-term-radar` (create it if it is missing).
3. Check an AIsa key is available: `AISA_API_KEY`, or the AIsa CLI logged in (`ls ~/.aisa/key`). Without one, only the free signals run (Hugging Face, GitHub, sitemaps), no X posts are read, and nothing judges which terms are names. Say so in the report. A key comes from https://go.aisa.one/yansen-zhu.
4. With no `config.json` in that directory the radar runs on the example list of X accounts and sitemaps it ships with, and says so. Tell the user, and that a `config.json` written there replaces it (the example to start from: https://github.com/zhuyansen/new-term-radar/blob/v0.6.0/config.example.json).

## Cost and time: say it, then wait for a yes

A run reads every X account in `config.json`: about 0.003 USD and 10 seconds each, so the example list of 35 accounts is about 0.11 USD and 6 minutes. `sources` costs the same. Tell the user the estimate and run only after they say yes: a request for the report is not a yes to the cost. Do not run it twice in a row: the second run reports only what changed since the first. `leads` is free.

## Run

```bash
uvx new-term-radar==0.6.1 daily --skip usecases,review,newsites,tutorials,asks,sellers,revenue --out listening.md
```

The rest: https://github.com/zhuyansen/new-term-radar/blob/HEAD/skills/ai-listening/SKILL.md