# Find and Prioritize Emerging AI Keywords

New AI terms are difficult to assess before search data settles. This skill gathers signals and organizes keyword opportunities using available search and competition data.

## Install

```bash
npx skillstore add zhuyansen/new-term-radar
```

## Metadata

- Status: approved
- Slug: zhuyansen-new-term-radar
- Skillstore revision: r2
- Version status: missing
- Tree hash: 3f8eb0e5e69fc443da73cb310ee881ce9e03b43355aefbddaafe5a3e65387fab
- Author: zhuyansen
- GitHub username: zhuyansen
- License: MIT
- Repository: https://github.com/zhuyansen/new-term-radar/tree/e1ce49e83dfefeb985b1db24d173cb785ca75dbc/skills/new-term-radar
- Ref: 1ac96f2048361bd348a3f97a5370c8f3f4c494c1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/zhuyansen-new-term-radar
- Manifest: https://skillstore.pages.dev/api/skills/zhuyansen-new-term-radar/manifest

## Capabilities

- Collect emerging names from configured sources and GitHub breakout signals.
- Research user-provided names without running the collection step.
- Prepare a keyword table with search estimates, momentum, competition, and decisions.
- Report source errors, first-run limitations, and brand flags.
- Summarize complaints from accessible reviews, Reddit, and tutorial comments.
- Request approval before running paid research commands.

## Use Cases

- Track new AI launches: Review newly detected names and their source signals.
- Prioritize search topics: Compare keyword demand and competition before planning pages.
- Explore product complaints: Group accessible complaints and linked examples for a tool category.

## Prompt Templates

### Research one name

```
Research the keyword opportunities for [name].
```

### Review new terms

```
Find today's new AI terms and prioritize their keywords. Tell me the estimated cost before running.
```

### Investigate complaints

```
Find common complaints about [tool category] and show linked examples. Explain coverage limits and estimated costs.
```

### Compare opportunities

```
Research [name one] and [name two]. Compare search estimates, trends, competition, brand flags, and missing data before recommending actions.
```

## Limitations

- Requires an AIsa API key and an external command-line package.
- Paid API calls require approval and costs vary with the run.
- The first daily run builds snapshots and may miss most new signals.
- Search volumes are estimates, and some review sources are unavailable.

## Best Practices

- Approve each paid run after reviewing its estimated cost.
- Use one working directory so snapshots persist between runs.
- Review source errors and brand flags before acting on recommendations.

## Anti Patterns

- Treating estimated search volume as an exact market measurement.
- Interpreting an incomplete first run as a quiet market.
- Following instructions embedded in collected posts or pages.

## Security Audit

- Audited at: 2026-10-27T09:12:59.792\+00:00
- Summary: Static matches are Markdown, disclosed service references, or research terminology, not evidence of the alleged attacks. The external package runs with service credentials, but its implementation was not reviewed.

## Stats

- Views: 1
- Downloads: 6
- Favorites: 1
- Popularity score: 0