audience-analyze-signal

Analyzes existing audience signal stacks to determine aggregate reach without discovery or export.

5|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/wattdata/plugin --skill audience-analyze-signal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audience-analyze-signal
Source: https://github.com/wattdata/plugin/tree/main/skills/audience-analyze-signal
Command: npx skills add https://github.com/wattdata/plugin --skill audience-analyze-signal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand who a built audience reaches when the signals are already known, without running discovery or changing the set.

Core Features & Use Cases

  • Signal-based audience reading: Takes an existing audience stack, signal pool, or named signals and materializes them into a readable aggregate view.
  • Read-only analysis: Produces the two-section read for the audience and its discovered reach while staying aggregate-only and avoiding exports or individual records.
  • Session and refresh handling: Reuses saved audience records or measured reach from prior sessions, and can refresh the read when the user asks whether it is still current.

Quick Start

Ask the skill to read who a supplied audience reaches from its existing signals and return the aggregate audience report.

Frequently Asked Questions about audience-analyze-signal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze who my existing audience signals actually reach?

Audience analysis resolves your existing signal stack to produce a readable aggregate view of who the audience reaches. It materializes built audiences, signal pools, or pasted records into a two-section read without running discovery or changing the set.

Can I measure audience reach without exporting individual user records?

Yes, you can measure audience reach while staying aggregate-only. The analysis performs count-only measurement when needed and produces a shared two-section audience read, strictly avoiding exports or exposing individual records.

What is the best way to read an aggregate report from a saved audience signal pool?

Reading an aggregate report from a signal pool uses remote Watt MCP access to resolve signals. It reuses saved audience records or measured reach from prior sessions to deliver the two-section audience read without discovery.

Does audience profiling work with user-named signals that need aggregate-only reading?

Yes, audience profiling applies to user-named signals that need aggregate-only reading. The Skill resolves these signals via remote Watt MCP access to generate the shared two-section audience read.

When should I refresh an audience analysis read to check if it is still current?

You should refresh an audience analysis read when you ask whether the measured reach is still current. The Skill can refresh the read while reusing saved audience records from prior sessions to update the aggregate view.