seo-new-keywords-research SKILL.md skillA
seo-new-keywords-research from zhuyansen/new-term-radar is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zhuyansen/new-term-radar/seo-new-keywords-research@git:20261028.3cf6515Pins git:20261028.3cf6515 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zhuyansen/new-term-radar
- Path
skills/seo-new-keywords-research/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.3cf6515, committed Oct 28, 2026
- First version recorded
- Oct 24, 2026
- Size
- 9,058 bytes
- Repository stars
- 2,125
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
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: `$NEW_TERM_RADAR_DIR` if set, else `~/new-term-radar` (create it if it is missing).
3. An AIsa key must be available, as `AISA_API_KEY` or from the AIsa CLI (`aisa login` stores 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.
…Read the whole file at its exact version.
How to install
mdr add zhuyansen/new-term-radar/seo-new-keywords-research@sha256:5a16b1372d1ce3a9The line at the top of this page pins the label git:20261028.3cf6515, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3zzozhw5e6lplysx)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 24, 2026 and Oct 28, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3cf6515 latest | 2026-10-28 | 3cf6515 | 9,058 B | A | view · diff |
| git:20261027.e1ce49e | 2026-10-27 | e1ce49e | 8,582 B | A | view · diff |
| git:20261027.399feef | 2026-10-27 | 399feef | 7,035 B | A | view · diff |
| git:20261026.97271eb | 2026-10-26 | 97271eb | 6,910 B | A | view · diff |
| git:20261024.4fd9a0d | 2026-10-24 | 4fd9a0d | 6,910 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9058 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zhuyansen/new-term-radar · 2,125 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3zzozhw5e6lplysx GET https://markdownregistry.com/api/v1/resolve?ref=zhuyansen/new-term-radar/seo-new-keywords-research GET https://markdownregistry.com/api/v1/blob/5a16b1372d1ce3a9572af42800667f2de8a790ba44aec3d65c20c8a2a013aa0c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.