audience

Turn an idea into an actual audience. Build a list of people — to a size you pick, the widest reach, or the highest-intent few — profile a market to see who's in it and how large it is, read who an audience reaches, or export it as a platform-ready file for Meta, Google, Reddit, or TikTok. Or start from a list you own — match it, expand it to every match, or read who's in it. Start here when you want the people, not just the lay of the land — "build me an audience of …", "the highest-intent people for X", "how many people are in my market", "match my customer list", "who's in this audience", "export this to Meta" — or type /watt:audience.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only router that gives unambiguous routing decisions, named leaf handoffs, and dependency guards without padding. Conciseness is strong but a few parentheticals could be trimmed, and workflow checkpoints are delegated to the leaves rather than spelled out inline.

Suggestions

Tighten the longest Entry clauses (refresh-shaped and list-as-starting-point) by moving the intent-routing detail into a compact table or trimming redundant parentheticals to lift conciseness toward 5.

Add one short explicit validation/checklist note at the door (e.g. 'confirm a built audience or signal pool exists before routing to analyze/activate') so the workflow_clarity checkpoint is inline rather than only implied.

Dimension	Reasoning	Score
Conciseness	Dense routing prose that assumes Claude's competence (no explaining what audiences or platforms are) and gives every clause a routing job, but several elaborate parentheticals (e.g. the refresh and list-intent clauses) could be tightened — efficient with minor over-explanation rather than the lean every-token-earns-its-place anchor at 5.	4 / 5
Actionability	Fully actionable routing: each Entry shape maps to a named leaf with exact handoff content and a concrete fallback question ('What are you trying to do — build … profile … read … or export?'), so the execution path is unambiguous even without code — the instruction-only exception applies.	5 / 5
Workflow Clarity	Clear sequence (one question → route → handoff) with explicit dependency guards ('no built audience and no signal pool → generate first') and a noted confirmation gate on activate, but validation lives in the delegated leaves rather than explicit validate→fix→retry checkpoints here, so it sits at the clear-sequence-most-checkpoints anchor rather than 5.	4 / 5
Progressive Disclosure	A self-contained ~40-line router with clean sections (Purpose, Works with, Entry, How to behave, Refuse cleanly) and no need for external reference files; the simple-skills exception for short, well-organized, reference-free skills applies, so it scores 5 rather than the minor-organization-gaps anchor at 4.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that covers the audience lifecycle comprehensively with concrete actions, platform-specific export targets, and an explicit 'Start here when…' trigger clause plus natural user phrases. Voice is imperative (consistent with the good examples), so no person-penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the full lifecycle — 'Build a list of people', 'profile a market', 'read who an audience reaches', 'export it as a platform-ready file for Meta, Google, Reddit, or TikTok', 'match it, expand it to every match' — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both what (build/profile/read/export/match/expand) and when ('Start here when you want the people, not just the lay of the land — … or type /watt:audience') with concrete trigger phrases, matching the anchor rather than the 4 anchor whose 'when' is only adequate.	5 / 5
Trigger Term Quality	Comprehensive natural phrases users would actually say — 'build me an audience of …', 'the highest-intent people for X', 'how many people are in my market', 'match my customer list', 'export this to Meta' — plus platform synonyms, matching the anchor including synonyms rather than the few-terms-missing anchor at 4.	5 / 5
Distinctiveness Conflict Risk	Clear niche (audience lifecycle on specific platforms) with distinct triggers and a named command, minimal overlap risk — matching the clear-niche anchor rather than the minor-overlap anchor at 4.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wattdata/plugin
Path: skills/audience/SKILL.md
Commit: 880e260

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.