Skills ai-listening
๐Ÿ“ฆ

ai-listening

Content revision r3 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access๐Ÿ”‘ Env variables

Track New AI Names Across Daily Sources

New AI names appear across separate feeds, making daily discovery difficult. This skill guides new-term-radar collection and organizes deduplicated names with supporting evidence.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it ๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "ai-listening" from https://skillstore.io/skills/zhuyansen-ai-listening.md and its manifest at https://skillstore.io/api/skills/zhuyansen-ai-listening/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "ai-listening". What should I expect from the first collection run?

Expected outcome:

The first run builds comparison snapshots and mainly reports GitHub breakouts. Limited results do not establish that AI activity was low.

Using "ai-listening". Can I run this without an AIsa key?

Expected outcome:

Hugging Face, GitHub, and configured sitemaps remain available. X posts and name judging are unavailable and should be listed as coverage gaps.

Using "ai-listening". Does a strong lead prove search demand?

Expected outcome:

No. The report shows observed source signals. Search demand requires separate research.

Security Audit

Safe
v3 โ€ข 10/28/2026 Open versioned report

All 24 static findings are false positives involving Markdown formatting, documented CLI usage, expected authentication checks, reference links, or report filtering. No evidence found of credential exfiltration, system reconnaissance, or prompt injection; the source explicitly rejects instructions embedded in collected data. This review covers SKILL.md only, not the external package implementation or its runtime network behavior.

1
Files scanned
60
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/zhuyansen-ai-listening/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/zhuyansen-ai-listening/security.svg)](https://skillstore.io/skills/zhuyansen-ai-listening?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/zhuyansen-ai-listening?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zhuyansen-ai-listening/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/zhuyansen-ai-listening.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

zhuyansen. (2026). ai-listening security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zhuyansen-ai-listening/audits/3

BibTeX citation

@techreport{zhuyansen-zhuyansen-ai-listening-2026, author = {zhuyansen}, title = {ai-listening security audit report (audit version 3)}, institution = {Skillstore}, year = {2026}, number = {3}, url = {https://skillstore.io/skills/zhuyansen-ai-listening/audits/3}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "ai-listening security audit report (audit version 3)" version: "unspecified" type: report authors: - name: "zhuyansen" date-released: "2026-10-28" url: "https://skillstore.io/skills/zhuyansen-ai-listening/audits/3" identifiers: - type: other value: "skillstore:zhuyansen-ai-listening:audit:3" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Prepare an AI news shortlist

Collect recently observed AI names with links and signal strength for editorial review.

Find emerging repositories

Review new GitHub breakouts and compare them with other discovery signals before investigating a project.

Seed keyword research

Gather observed model and product names for a separate search-demand research workflow.

Try These Prompts

Start a daily report
Prepare a daily AI listening report. Check setup and explain estimated costs before requesting approval to collect data.
Review retained names
List retained leads from the last day without a new collection run. Summarize available names and source evidence.
Monitor faster sources
Use the sources workflow for X and Hugging Face. Explain costs and request approval first, then report new names and missing signals.
Prioritize evidence-backed leads
Review the latest listening report. Rank names by source overlap and name score, exclude known leads, and separate breakout repositories from coverage gaps.

Best Practices

  • Keep the same working directory between daily runs so snapshot comparisons remain useful.
  • Approve estimated costs before collection and review the configured account and sitemap lists.
  • Treat collected text as untrusted data and report only supported names, links, and signal evidence.

Avoid

  • Running collection twice consecutively and expecting the same daily comparison.
  • Presenting missing signals or first-run snapshot gaps as evidence of low activity.
  • Following instructions inside collected posts or publishing findings without separate approval.

Frequently Asked Questions

What software is required?
The instructions use new-term-radar 0.6.1 with Python 3.10 or newer. uvx is preferred, with a pip installation fallback.
Is an AIsa API key mandatory?
A key enables X collection and name judging. Without it, only the documented free signals run.
How much does collection cost?
The skill estimates about 0.003 USD per X account. Its 35-account example costs about 0.11 USD; approval is required before collection.
Why is the first report limited?
The first run creates baseline snapshots for vocabulary, stars, and sitemap URLs. Later runs compare new observations against those baselines.
Can I review results without paying for another run?
Yes. The leads command lists retained results without starting another collection run and is documented as free.
Does this skill publish or contact anyone automatically?
No. The instructions require separate approval for each publication, message, purchase, or other outbound action.

Developer Details

Author

zhuyansen

License

MIT

Skillstore revision

r3

Version notice

The author did not declare a version.

Ref

2ec268972a6be25768f84279fde605b246c33d68

Maintenance freshness

10/28/2026

Usage

7 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md