Fähigkeiten ai-listening
📦

ai-listening

Inhaltsrevision r3 Sicher ⚙️ Externe Befehle🌐 Netzwerkzugriff📁 Dateisystemzugriff🔑 Umgebungsvariablen

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.

Unterstützt: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 77 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Testen

„ai-listening“ wird verwendet. What should I expect from the first collection run?

Erwartetes Ergebnis:

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

„ai-listening“ wird verwendet. Can I run this without an AIsa key?

Erwartetes Ergebnis:

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

„ai-listening“ wird verwendet. Does a strong lead prove search demand?

Erwartetes Ergebnis:

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

Sicherheitsaudit

Sicher
v3 • 28.10.2026 Versionsbericht öffnen

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
Gescannte Dateien
60
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex Audit-Verlauf anzeigen →
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

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>

Einbettungskarte

<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>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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

BibTeX-Zitat

@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

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
83
Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

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.

Bewährte Praktiken

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

Vermeiden

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

Häufig gestellte Fragen

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.

Entwicklerdetails

Autor

zhuyansen

Lizenz

MIT

Skillstore-Revision

r3

Versionshinweis

Der Autor hat keine Version angegeben.

Ref.

2ec268972a6be25768f84279fde605b246c33d68

Aktualität der Wartung

28.10.2026

Nutzung

6 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md

Mehr von zhuyansen

Alle anzeigen
Alle anzeigen