SEO New Keywords Research
Turn new AI names or unstructured AI market signals into a keyword priority table.
Install
npx skills add zhuyansen/new-term-radar --skill seo-new-keywords-research -g -a claude-code -y- Repository
- zhuyansen/new-term-radar2k
- Category
- Git and review
- Updated
- 7d ago
- License
- MIT
- Context cost
- Mediumabout 2,094 tokens
- Runs scripts
- No, instructions only
What it does
Turn new AI names or unstructured AI market signals into a keyword priority table. For each name it finds the generic search terms downstream of it, screens them for relevance, and checks novelty, demand size and momentum against Google Ads volume and DataForSEO Trends (an estimate of Google search interest), ending in prioritize, watch or skip. Use when the user has new model, product or repository names (or an AI listening report, a batch of posts, a changelog) and asks which keywords to build pages or tools for. Runs the new-term-radar command line; needs an AISA_API_KEY, and a GOANYAPI_API_KEY improves it.
SEO new-keywords research
Input: names of new AI things, or raw text that mentions them. Output: one table, names and the generic terms behind them, each with a decision.
A name ("SynthID Detector") has a short life as a keyword and belongs to someone. The job it does ("ai image detector") is what people keep searching, and nobody owns it. You need both in the same table.
Before you run anything
- 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, thennew-term-radar <command> …. - Run every command from one working directory:
$NEW_TERM_RADAR_DIRif set, else~/new-term-radar(create it if it is missing). - An AIsa key must be available, as
AISA_API_KEYor from the AIsa CLI (aisa loginstores it in~/.aisa): every lookup here is paid through it. Without it, stop and say so. A key comes from https://go.aisa.one/yansen-zhu. GOANYAPI_API_KEYis optional (a key comes from https://goanyapi.com/r/ga-95708898fb). With it the table also holds what people really searched together with each name, and reads the bigger rows from one country's settled series. Without it, tell the user that a "flat" reading is weaker evidence (see below).- With no
config.jsonin 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 aconfig.jsonwritten there replaces it (the example to start from: https://github.com/zhuyansen/new-term-radar/blob/v0.6.0/config.example.json).
Step 1: pick the names
If the user gave names, use them. If they gave text (a listening report, posts, release notes), extract the names yourself:
