← Back to list
🎨
social-pulse-monitor ✓ Security reviewed
Use when the user asks to "monitor brand mentions", "set up social listening", "did anything spik…
🎨 Design & Creative By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.7Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "social-pulse-monitor" skill by following the instructions at https://skill123.me/install/social-pulse-monitor.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/social-pulse-monitor.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB

About this skill

Overview

Use when the user asks to "monitor brand mentions", "set up social listening", "did anything spike about us this week", or "watch these accounts for buying triggers"; runs always-on keyless listening — a versioned listening-query architecture (brand variants incl. misspellings and 中文 names, exclusion terms, per-source syntax for HN Algolia / Bluesky / GDELT / Tavily), a mention sweep with six-class triage (crisis / bug / lead / praise / question / spam) each routed with an SLA, a 7-day rolling baseline with spike flags (the crisis trigger input), a B2B trigger watchlist (funding / hiring / launch signals), and an explicit coverage disclosure where X/IG/TikTok/LinkedIn/小红书 numbers are proxy-labeled, never Measured. Not for launch-window telemetry (T-0→T+30 rank and review polling) — use launch-monitor. 舆情监听/品牌提及监测/基线突刺/触发信号

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: social/observe/social-pulse-monitor

Evaluation

AI-evaluated 2026-09-03: Very precise workflow: versioned query sets with misspellings and exclusion terms, six-class triage with routing and SLAs, 7-day baseline spike math, coverage disclosure table, and clear scope guards. Heavy dependence on the sibling-skill ecosystem, connector scripts, and memory/registry infrastructure limits drop-in usability, but it solves a real common need (brand listening) with strong untrusted-input and no-automation safeguards.

Score breakdown

Quality
8.0
Usability
6.0
Security
9.0
Popularity
7.0