Individual skill

social-pulse-monitor

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. 舆情监听/品牌提及监测/基线突刺/触发信号

social/observe/social-pulse-monitor/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,134
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Social Pulse Monitor

Always-on brand and community listening — the ears of the ECHO **Observe** phase. It maintains the listening-query architecture, sweeps the keyless public surfaces for mentions, triages each one to an owner with an SLA, and keeps the 7-day rolling baseline whose spike flag is the trigger input for [crisis-response-planner](../../host/crisis-response-planner/SKILL.md). It feeds three ECHO `O` sub-items directly: *7-day listening baseline maintained with spike thresholds set*, *listening-query architecture current (brand variants incl. 中文 names and misspellings, exclusion terms, per-source syntax)*, and *community-health metrics employee-excluded* (see [echo-benchmark.md](../../../references/echo-benchmark.md)). Only [social-quality-auditor](../../host/social-quality-auditor/SKILL.md) computes the ECHO profile result and runs the vetoes; this skill supplies the listening facts.

**Scope guard**: this skill listens and routes — it never responds. Drafting replies and UGC rights collection stay with [engagement-inbox-manager](../../host/engagement-inbox-manager/SKILL.md); declaring a crisis and pausing the queue stay with [crisis-response-planner](../../host/crisis-response-planner/SKILL.md) (this skill only raises the spike flag); the locked-panel competitive trend stays with [share-of-voice-tracker](../share-of-voice-tracker/SKILL.md); launch-window telemetry (T-0→T+30) stays with [launch-monitor](../../../launch/prove/launch-monitor/SKILL.md). No posting, reply, or DM automation anywhere — closed platforms (X/IG/TikTok/LinkedIn/小红书/微信公众号/视频号/抖音) are read via user exports or proxy-labeled signals only, and automating them is a hard red line (风控/封号). Registry-grade mention lines go only to `memory/events/channels.ndjson` via an authorized `operation: propose` request to `registry-events.py` — [channel-registry](../../../protocol/channel-registry/SKILL.md) is the sole writer of `memory/channels/`.

## Quick Start

```
Set up listening for [brand]. Name variants: [misspellings, 中文名, product names, exec handles]. Build the query set and run today's sweep.
```

```
Run this week's pulse: compare mention volume to the 7-day baseline, flag any spike, and give me the triaged routing queue.
Back to top