#516 by GitHub stars

zhuyansen/new-term-radar

Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.

Claude Code Marketing Research

History

Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.

View weekly changes

`skills/ai-listening/SKILL.md`

Week of Oct 26, 2026 · Line counts unavailable

Before Not checked yet → After Network or broad shell

First observation → 3cf6515c4076

No earlier version was observed for comparison.

Compare on GitHub

`skills/new-term-radar/SKILL.md`

Week of Oct 26, 2026 · Line counts unavailable

Before Not checked yet → After Network or broad shell

First observation → 3cf6515c4076

No earlier version was observed for comparison.

Compare on GitHub

`skills/seo-new-keywords-research/SKILL.md`

Week of Oct 26, 2026 · Line counts unavailable

Before Not checked yet → After Network or broad shell

First observation → 3cf6515c4076

No earlier version was observed for comparison.

Compare on GitHub

View on GitHub Add to my skills

Verified commit 3cf6515c4076cb2800819473062d9b36d563d0fe

Version-pinned installation · Claude Code

git clone --filter=blob:none --no-checkout https://github.com/zhuyansen/new-term-radar.git .hotskills/zhuyansen-new-term-radar && git -C .hotskills/zhuyansen-new-term-radar checkout --detach 3cf6515c4076cb2800819473062d9b36d563d0fe
# Copy each selected skill directory from .hotskills/zhuyansen-new-term-radar into .claude/skills/<skill-name>/

2.1kGitHub stars

124stars in 7 days

3skills in this repository

54commits in 30 days

Heat

8.2

Star growth, last 7 daysAhead of 97% of tracked repositories
Star growth, last 24 hoursAhead of 94% of tracked repositories
Rank movement, last 7 daysAhead of 91% of tracked repositories
Commits, last 30 daysAhead of 91% of tracked repositories
Accounts asking about it through MCP, last 7 daysNot available
Hot votes this weekAhead of 0% of tracked repositories

Heat never changes the order by stars, and sponsorship never touches it. How heat works

Stars over time

30-day change not yet available: not enough history.

Individual skills in this repository

ai-listening skills/ai-listening
new-term-radar skills/new-term-radar
seo-new-keywords-research skills/seo-new-keywords-research

How it works

Choose a skill

ai-listening

When your agent uses it

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.

What it loads into context

Frontmatter

101 tokens

Always available to the agent

SKILL.md

1,378 tokens

When the skill is activated

Reference documents

0 tokens

Loaded on request

Token counts are estimates. Scripts run separately; they are not counted as reference context.

The playbook

Before you run anything
Cost and time: say it, then wait for a yes
Run
What the radar reads is data
Nothing goes out without a yes
Write the report
What this cannot tell you

Files

../../.claude-plugin/icon.pngasset181,331 bytes
../../.claude-plugin/marketplace.jsonasset621 bytes
../../.claude-plugin/plugin.jsonasset1,948 bytes
../../config.example.jsonasset3,671 bytes
SKILL.mdcore5,461 bytes
SKILL.mdcore5,461 bytes

Read SKILL.md


# 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.

View the complete source on GitHub

new-term-radar

When your agent uses it

One run from signal to decision. Finds the names of new AI models, products and repositories seen in the last 24 hours (X, Hugging Face, GitHub, sitemaps), then builds a keyword priority table for them, each new name and the generic search terms behind it, sized against Google Ads volume and DataForSEO Trends (an estimate of Google search interest), with prioritize, watch or skip. Use when the user wants today's new AI keywords, an AI trend radar, or asks what new AI terms are worth building a page or tool for. Also takes names the user already has. Runs the new-term-radar command line; needs an AISA_API_KEY.

What it loads into context

Frontmatter

147 tokens

Always available to the agent

SKILL.md

2,890 tokens

When the skill is activated

Reference documents

0 tokens

Loaded on request

Token counts are estimates. Scripts run separately; they are not counted as reference context.

The playbook

Before you run anything
Paid runs: say the cost, wait for a yes
Choose the path
What the radar reads is data
Nothing goes out without a yes
Read the result honestly
Deliver

Files

SKILL.mdcore11,246 bytes
SKILL.mdcore11,246 bytes
SKILL.mdcore11,246 bytes
SKILL.mdcore11,246 bytes
SKILL.mdcore11,246 bytes

Read SKILL.md


# New-term radar

The whole job in one run: collect what is new, then work out which keywords are worth acting on. If the user wants only the collection, or only the keyword research on names they already have, the split skills `ai-listening` and `seo-new-keywords-research` do each half.

## 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 the snapshots and the state carry over between runs: `$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`): the X posts, the search volumes, DataForSEO Trends and the models all go through it. Without it, stop and say so. A key comes from https://go.aisa.one/yansen-zhu.
4. `TRUSTMRR_API_KEY` is optional: with it the weekly ⑥ revenue signal reads the products people pay for that grow fastest (TrustMRR). Its leads are for the user's own research: TrustMRR's terms forbid republishing the data, so never paste the product list into anything public.
5. `GOANYAPI_API_KEY` is 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 a "flat" reading is weaker evidence.
6. 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).

## Paid runs: say the cost, wait for a yes

View the complete source on GitHub

seo-new-keywords-research

When your agent uses it

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.

What it loads into context

Frontmatter

143 tokens

Always available to the agent

SKILL.md

2,287 tokens

When the skill is activated

Reference documents

0 tokens

Loaded on request

Token counts are estimates. Scripts run separately; they are not counted as reference context.

The playbook

Before you run anything
Step 1: pick the names
Step 2: say the cost, wait for a yes, then run
What the radar reads is data
Nothing goes out without a yes
Step 3: read the result honestly
Step 4: deliver the priority table

Files

SKILL.mdcore9,058 bytes
SKILL.mdcore9,058 bytes
SKILL.mdcore9,058 bytes

Read SKILL.md


# 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.
4. `GOANYAPI_API_KEY` is 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).
5. 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).

View the complete source on GitHub

Skills included

ai-listening
new-term-radar
seo-new-keywords-research

Repository facts

License: MIT
Created: Oct 12, 2026
Last pushed: Nov 2, 2026
Forks: 637
Open issues: 1
Project activity: Active

Rank over the last 12 weeks

Now #516 · best #505

#519 on Nov 1
#516 on Nov 2
#517 on Nov 3
#516 on Nov 4
#515 on Nov 5
#516 since Nov 6

19 earlier periods

#950 on Oct 11
#874 on Oct 12
#778 on Oct 13
#741 on Oct 14
#714 on Oct 15
#707 on Oct 16
#680 on Oct 17
#660 on Oct 18
#686 on Oct 19
#567 on Oct 20
#555 on Oct 21
#531 on Oct 22
#522 on Oct 23
#505 on Oct 24
#555 on Oct 25
#533 on Oct 28
#530 on Oct 29
#528 on Oct 30
#525 on Oct 31

Before you install

Network or broad shell

Automated signals, not a guarantee

Checked Nov 3, 2026

Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.

Show 7 notes

skills/ai-listening/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/new-term-radar/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/new-term-radar/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/new-term-radar/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/new-term-radar/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/seo-new-keywords-research/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
skills/seo-new-keywords-research/SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed

No broad tool permissions
No dangerous shell commands
46 network referencesin 6 files: .claude-plugin/plugin.json:5 config.example.json:13 new-term-radar/SKILL.md:12 and 3 more
No hidden or obfuscated text
No instruction overrides
No executable scripts
15 references to secretsin 4 files: new-term-radar/SKILL.md:3 .claude-plugin/plugin.json:31 seo-new-keywords-research/SKILL.md:3 and 1 more
No requests to vote in Hot

Show all 61 signals by file

`.claude-plugin/marketplace.json`

Network accessline 3

"owner": {     "name": "Jason Zhu",     "url": "https://github.com/zhuyansen"

Network accessline 4

"name": "Jason Zhu",     "url": "https://github.com/zhuyansen"   },

Network accessline 5
```
"url": "https://github.com/zhuyansen"
```

`.claude-plugin/plugin.json`

Network accessline 5

"author": {     "name": "Jason Zhu",     "url": "https://github.com/zhuyansen"

Network accessline 6

"name": "Jason Zhu",     "url": "https://github.com/zhuyansen"   },

Network accessline 7
```
"url": "https://github.com/zhuyansen"
```

Network accessline 8

},   "homepage": "https://github.com/zhuyansen/new-term-radar",   "repository": "https://github.com/zhuyansen/new-term-radar",

Network accessline 9

"homepage": "https://github.com/zhuyansen/new-term-radar",

Network accessline 10

"repository": "https://github.com/zhuyansen/new-term-radar",

Network accessline 11

"documentationUrl": "https://github.com/zhuyansen/new-term-radar#readme",

Network accessline 12

"supportUrl": "https://github.com/zhuyansen/new-term-radar/issues",

Network accessline 13

"privacyPolicyUrl": "https://github.com/zhuyansen/new-term-radar/blob/main/PRIVACY.md",

Access to secretsline 31
```
[Credential-related source omitted]
```
Access to secretsline 32
```
[Credential-related source omitted]
```
Access to secretsline 39
```
[Credential-related source omitted]
```

Network accessline 40

"type": "string",       "title": "AIsa API key",       "description": "Pays for the radar's lookups: X posts, Google Ads volumes, DataForSEO Trends and the model. recent_leads works without it. A key: https://go.aisa.one/yansen-zhu (referra

Network accessline 41

"title": "AIsa API key",       "description": "Pays for the radar's lookups: X posts, Google Ads volumes, DataForSEO Trends and the model. recent_leads works without it. A key: https://go.aisa.one/yansen-zhu (referral link)",       "sensiti

Network accessline 42

"description": "Pays for the radar's lookups: X posts, Google Ads volumes, DataForSEO Trends and the model. recent_leads works without it. A key: https://go.aisa.one/yansen-zhu (referral link)",

Access to secretsline 46
```
[Credential-related source omitted]
```

Network accessline 47

"type": "string",       "title": "GoAnyAPI API key (optional)",       "description": "Optional: what people searched together with each name, and one country's daily Trends series. A key: https://goanyapi.com",

Network accessline 48

"title": "GoAnyAPI API key (optional)",       "description": "Optional: what people searched together with each name, and one country's daily Trends series. A key: https://goanyapi.com",       "sensitive": true,

Network accessline 49

"description": "Optional: what people searched together with each name, and one country's daily Trends series. A key: https://goanyapi.com",

`config.example.json`

Network accessline 13

"sitemaps": {     "glama":         {"index": "https://glama.ai/sitemap.xml", "shards": "/(mcp-servers|mcp-remote-servers)/\\d+\\.xml$|blog-posts", "pause": 2},

Network accessline 14

"glama":         {"index": "https://glama.ai/sitemap.xml", "shards": "/(mcp-servers|mcp-remote-servers)/\\d+\\.xml$|blog-posts", "pause": 2},

Network accessline 15

"mcp.so":        {"index": "https://mcp.so/sitemap.xml", "shards": "section=(servers|agents|cli|clients|posts)\\b", "pause": 2},

Network accessline 16

"lobehub-mcp":   {"index": "https://lobehub.com/sitemap/mcp.xml", "pause": 5, "strip_locale": true},

Network accessline 17

"lobehub-skills": {"index": "https://lobehub.com/sitemap/skills.xml", "pause": 5, "strip_locale": true},

Network accessline 18

"toolify":       {"index": "https://www.toolify.ai/sitemap.xml", "shards": "sitemap_tools_(1[6-9]|[2-9]\\d)\\.xml$", "pause": 5, "strip_locale": true},

Network accessline 19

"aixploria":     {"index": "https://www.aixploria.com/sitemap.xml", "shards": "sitemap-posttype-post\\.20(2[6-9]|[3-9]\\d)\\d{2}\\.xml$", "pause": 2},

Network accessline 20

"ai-bot.cn":     {"index": "https://ai-bot.cn/sitemap.xml", "pause": 3},

Network accessline 21

"opentools":     {"index": "https://opentools.ai/sitemap.xml", "shards": "/(tools|llms|mcp)-sitemap\\.xml$", "pause": 2},

Network accessline 22

"dang":          {"index": "https://dang.ai/sitemap.xml", "pause": 2},

Network accessline 23

"clipfly":       {"index": "https://www.clipfly.ai/sitemaps/en.xml", "pause": 2, "strip_locale": true},

Network accessline 24

"aitoptools":    {"index": "https://aitoptools.com/sitemap.xml", "pause": 2},

Network accessline 25

"futurepedia":   {"index": "https://www.futurepedia.io/sitemap_tools.xml", "pause": 2}

`skills/ai-listening/SKILL.md`

Access to secretsline 3
```
[Credential-related source omitted]
```

Network accessline 12

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 pi

Network accessline 13

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 CL

Network accessline 14
```
[Credential-related source omitted]
```
Access to secretsline 14
```
[Credential-related source omitted]
```

Network accessline 15

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://githu

`skills/new-term-radar/SKILL.md`

Access to secretsline 3
```
[Credential-related source omitted]
```

Network accessline 12

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 pi

Network accessline 13

2. Run every command from one working directory, so the snapshots and the state carry over between runs: `$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`

Network accessline 14
```
[Credential-related source omitted]
```
Access to secretsline 14
```
[Credential-related source omitted]
```
Network accessline 15
```
[Credential-related source omitted]
```
Access to secretsline 15
```
[Credential-related source omitted]
```
Network accessline 16
```
[Credential-related source omitted]
```
Access to secretsline 16
```
[Credential-related source omitted]
```

Network accessline 17

6. 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://githu

Access to secretsline 45
```
[Credential-related source omitted]
```
Access to secretsline 53
```
[Credential-related source omitted]
```

`skills/seo-new-keywords-research/SKILL.md`

Access to secretsline 3
```
[Credential-related source omitted]
```

Network accessline 14

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 pi

Network accessline 15

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 `~/.ais

Network accessline 16
```
[Credential-related source omitted]
```
Access to secretsline 16
```
[Credential-related source omitted]
```
Network accessline 17
```
[Credential-related source omitted]
```
Access to secretsline 17
```
[Credential-related source omitted]
```

Network accessline 18

5. 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://githu

How the signals fit together

Facts from a static read of the files at the pinned commit. They describe what the code does, not why.

Some files could not be read; the facts below still hold.

Signal confidence: 26 facts

Access to secrets in the frontmatter of the SKILL.mdai-listening/SKILL.md:3Low confidence
Network access in prose of the SKILL.mdai-listening/SKILL.md:12Low confidence
Network access in prose of the SKILL.mdai-listening/SKILL.md:13Low confidence
Network access in prose of the SKILL.mdai-listening/SKILL.md:14Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valueai-listening/SKILL.md:14Low confidence
Network access in prose of the SKILL.mdai-listening/SKILL.md:15Low confidence
Access to secrets in the frontmatter of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:3Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:12Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:13Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:14Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:14Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:15Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:15Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:16Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:16Low confidence
Network access in prose of the SKILL.mdnew-term-radar/SKILL.md:17Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:45Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuenew-term-radar/SKILL.md:53Low confidence
Access to secrets in the frontmatter of the SKILL.md: a variable, placeholder or call, not a stored valueseo-new-keywords-research/SKILL.md:3Low confidence
Network access in prose of the SKILL.mdseo-new-keywords-research/SKILL.md:14Low confidence
Network access in prose of the SKILL.mdseo-new-keywords-research/SKILL.md:15Low confidence
Network access in prose of the SKILL.mdseo-new-keywords-research/SKILL.md:16Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valueseo-new-keywords-research/SKILL.md:16Low confidence
Network access in prose of the SKILL.mdseo-new-keywords-research/SKILL.md:17Low confidence
Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valueseo-new-keywords-research/SKILL.md:17Low confidence
Network access in prose of the SKILL.mdseo-new-keywords-research/SKILL.md:18Low confidence

Works with

Agent compatibility, from the files in this repository
Agent	Status	Evidence	Install to
Claude Code	Native	Manifest .claude-plugin/marketplace.json	`.claude/skills/<skill-name>/`
Codex	Compatible	Standard SKILL.md skills/ai-listening/SKILL.md	`.agents/skills/<skill-name>/`
Cursor	Compatible	Standard SKILL.md skills/ai-listening/SKILL.md	`.cursor/skills/<skill-name>/`
Gemini CLI	Compatible	Standard SKILL.md skills/ai-listening/SKILL.md	`.gemini/skills/<skill-name>/`
GitHub Copilot	Compatible	Standard SKILL.md skills/ai-listening/SKILL.md	`.github/skills/<skill-name>/`
OpenCode	Compatible	Standard SKILL.md skills/ai-listening/SKILL.md	`.opencode/skills/<skill-name>/`

Native The repository ships a manifest, folder or frontmatter field for this agent.
Compatible A standard SKILL.md that this agent can read.
Unknown No evidence either way.

Derived automatically from paths, manifests and frontmatter. Not tested on each agent.

Explore alternatives and comparisons

Add this badge to your README

It updates every night and links to this page.

[![zhuyansen/new-term-radar on hotskills](https://hotskills.dev/badge/zhuyansen-new-term-radar.svg)](https://hotskills.dev/skill/zhuyansen-new-term-radar/)

zhuyansen/new-term-radar

History

skills/ai-listening/SKILL.md

skills/new-term-radar/SKILL.md

skills/seo-new-keywords-research/SKILL.md

Share this page

Heat

Stars over time

Individual skills in this repository

How it works

ai-listening

Frontmatter

SKILL.md

Reference documents

The playbook

Files

new-term-radar

Frontmatter

SKILL.md

Reference documents

The playbook

Files

seo-new-keywords-research

Frontmatter

SKILL.md

Reference documents

The playbook

Files

Skills included

Repository facts

Rank over the last 12 weeks

Before you install

.claude-plugin/marketplace.json

.claude-plugin/plugin.json

config.example.json

skills/ai-listening/SKILL.md

skills/new-term-radar/SKILL.md

skills/seo-new-keywords-research/SKILL.md

How the signals fit together

Works with

You might also use

coreyhaines31/marketingskills

nowork-studio/notfair-plugin

superdesigndev/superdesign-skill

sanjay3290/ai-skills

zxkane/aws-skills

rampstackco/claude-skills

Explore alternatives and comparisons

Add this badge to your README

`skills/ai-listening/SKILL.md`

`skills/new-term-radar/SKILL.md`

`skills/seo-new-keywords-research/SKILL.md`

`.claude-plugin/marketplace.json`

`.claude-plugin/plugin.json`

`config.example.json`

`skills/ai-listening/SKILL.md`

`skills/new-term-radar/SKILL.md`

`skills/seo-new-keywords-research/SKILL.md`