agentsclimarketplace

Newsletter audience intelligence

Skill Get-Maito/newsletter-skills/skills/newsletter/newsletter-audience-intelligence

Open-source agent skills for newsletter operators.

Install
npx -y skills add Get-Maito/newsletter-skills --skill newsletter-audience-intelligence

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user asks to understand newsletter audience quality, segment readers, summarize survey/reply/click data, prove sponsor value, create media-kit proof points, compare subscriber source quality, or decide what audience data to collect next.

SKILL.md

2.6 KB, as published. Nobody here has run it

Newsletter Audience Intelligence

Turn subscriber, reply, survey, source, and click data into sponsor-ready audience proof and operating decisions.

Core Rule

Use connected analytics, subscriber data, source attribution, survey answers, replies, sponsor history, and issue history when available. Do not invent audience metrics, demographics, reader quotes, locations, job titles, or intent signals.

Inputs

  • Newsletter name, category, audience, geography or market
  • Current subscriber count, opens, clicks, replies, source attribution, and survey data if available
  • Reader segments or tags already used
  • Sponsor, paid conversion, growth, or content-quality goal
  • Known acquisition sources: Meta, Reddit, X, LinkedIn, TikTok, referrals, swaps, events, search, or organic
  • Connected workspace, analytics export, or manual data if available

Workflow

  1. Separate known data from assumptions and missing data.
  2. Identify useful audience segments by source, geography, role, interest, behavior, lifecycle, or purchase intent.
  3. Compare segment quality using engagement, clicks, replies, conversions, and sponsor fit.
  4. Extract sponsor-proof bullets without overclaiming attribution.
  5. Flag weak or missing proof needed before selling sponsors or scaling acquisition.
  6. Recommend 3-7 survey, onboarding, reply, or tagging improvements.
  7. Save or hand off audience insights, segment notes, and next data collection steps for the connected workspace.

Output Format

When a reusable artifact is useful, follow templates/audience-proof.md.

Include:

  • Audience-quality summary
  • Known data vs missing data
  • Segment table
  • Sponsor-proof bullets
  • Weak proof or risk notes
  • Data collection plan
  • Connected-workspace handoff notes

Segment table columns:

SegmentEvidenceValue to operatorSponsor relevanceConfidenceNext data to collect

Guardrails

  • Do not infer demographics from stereotypes or category assumptions.
  • Do not treat subscriber count as sponsor proof by itself.
  • Keep exact metrics separate from qualitative signals.
  • If data is thin, output a collection plan instead of pretending there is a strong audience story.
  • Do not export, delete, tag, or modify subscribers without explicit approval and an available workspace/API tool.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.