← Back to Skills Marketplace
freeman14

Newsletter Growth Ops

by Dmitriy · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
41
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install newsletter-growth-ops
Description
Use when the user asks to grow newsletter subscribers, evaluate acquisition channels, convert social followers to email, re-engage inactive readers, analyze...
README (SKILL.md)

Newsletter Growth Ops

Plan practical subscriber and revenue growth experiments.

Core Rule

Use connected analytics, subscriber data, source attribution, issue history, and survey notes when available. Do not invent metrics.

Inputs

  • Growth goal: subscribers, revenue, paid members, sponsors, events, or content quality
  • Current audience metrics and source attribution, if available
  • Existing channels: search, Instagram, LinkedIn, X, referrals, paid ads, events, partnerships, or surveys
  • Monetization model: sponsors, membership, paid subscriptions, events, directory, or deals
  • Constraints: budget, time, audience trust, excluded channels

Workflow

  1. Identify the growth constraint: acquisition, activation, retention, monetization, or conversion.
  2. Review what has already been tried and what it cost.
  3. Choose 1-3 small experiments with clear success metrics.
  4. Add tracking requirements: signup source, survey question, tag, segment, CTA, or sponsor attribution.
  5. Save or hand off analytics notes and experiment setup for the connected workspace.

Routing

  • Audience quality, segments, media-kit proof, survey/reply/click insights, or sponsor proof: newsletter-audience-intelligence
  • General sponsor prospecting, sponsor packages, rate cards, media-kit bullets, outreach, IOs, asset collection, or payment follow-up: newsletter-sponsor-ops
  • Monetization model selection across sponsors, paid subscriptions, affiliates, products, services, events, directories, or lead gen: newsletter-monetization-strategy
  • Platform cost, ad profitability, tool upgrades, CAC/LTV, downstream business attribution, or keep/pause/sell decisions: newsletter-roi-dashboard
  • Local sponsor lead generation where geography is the main constraint: local-sponsor-sales
  • Post-campaign sponsor reporting or renewal emails: newsletter-sponsor-recap

Output Format

Include:

  • Growth diagnosis
  • Experiment table
  • Tracking or survey changes
  • Connected-workspace handoff notes
  • Stop/continue criteria

Experiment table columns:

Experiment Goal Audience Channel Metric Cost or effort Decision rule

Guardrails

  • Do not recommend scaling paid acquisition without a retention or monetization check.
  • Separate subscriber growth from revenue growth.
  • Protect reader trust when recommending sponsorship, membership, or paywall experiments.
Usage Guidance
Install this if you want help planning newsletter subscriber or revenue growth experiments. Review what connected analytics, subscriber, budget, sponsor, and revenue data you provide, and approve any saved workspace handoff notes before relying on them.
Capability Assessment
Purpose & Capability
The skill's purpose is clear and coherent: diagnose newsletter growth constraints, plan subscriber or revenue experiments, define tracking, and route related sponsor, monetization, ROI, or audience tasks to other named skills.
Instruction Scope
Instructions stay within newsletter growth operations and include appropriate guardrails such as not inventing metrics, separating subscriber growth from revenue growth, and protecting reader trust.
Install Mechanism
The artifact contains only a single SKILL.md markdown file, with no executable scripts, dependencies, package install hooks, or API key requirement.
Credentials
The skill may use analytics, subscriber data, attribution, issue history, survey notes, budget, and monetization context when available; this can be sensitive, but it is disclosed and proportionate to the stated growth-planning purpose.
Persistence & Privilege
The workflow says to save or hand off analytics notes and experiment setup for a connected workspace, but this is visible, user-relevant behavior and there is no evidence of background execution, credential persistence, or autonomous external action.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install newsletter-growth-ops
  3. After installation, invoke the skill by name or use /newsletter-growth-ops
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of newsletter-growth-ops skill. - Enables planning and execution of newsletter subscriber and revenue growth experiments. - Uses analytics, subscriber data, attribution, and survey notes for informed recommendations. - Provides a structured workflow for diagnosing growth constraints, reviewing past efforts, and designing tractable experiments. - Includes a routing system to connect with skills for audience insights, sponsor ops, monetization strategy, ROI analysis, and local sponsor sales. - Delivers output with a growth diagnosis, experiment table, tracking recommendations, and handoff notes.
Metadata
Slug newsletter-growth-ops
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Newsletter Growth Ops?

Use when the user asks to grow newsletter subscribers, evaluate acquisition channels, convert social followers to email, re-engage inactive readers, analyze... It is an AI Agent Skill for Claude Code / OpenClaw, with 41 downloads so far.

How do I install Newsletter Growth Ops?

Run "/install newsletter-growth-ops" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Newsletter Growth Ops free?

Yes, Newsletter Growth Ops is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Newsletter Growth Ops support?

Newsletter Growth Ops is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Newsletter Growth Ops?

It is built and maintained by Dmitriy (@freeman14); the current version is v1.0.0.

💬 Comments