Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Choose Monetization Mix

ASecurity

Decide which revenue lines a creator should run and in what order — grounded in audience size × engagement × buying-intent, weighted toward recurring revenue and away from single-platform/single-sponsor concentration. Reach for this at the START of monetizing an audience, or when income is volatile/over-concentrated. Driven by creator-business-strategist.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentsrustaws

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill choose-monetization-mix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Choose Monetization Mix?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Choose Monetization Mix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-choose-monetization-mix/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-choose-monetization-mix)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: choose-monetization-mix
description: "Decide which revenue lines a creator should run and in what order — grounded in audience size × engagement × buying-intent, weighted toward recurring revenue and away from single-platform/single-sponsor concentration. Reach for this at the START of monetizing an audience, or when income is volatile/over-concentrated. Driven by creator-business-strategist."
---

# Skill: Choose the Monetization Mix

The binding inputs are audience size × engagement × buying-intent — not follower
count. This skill produces a prioritized revenue mix. Driven by
`creator-business-strategist`.

## Step 1 — Characterize the audience honestly

- **Buying-intent**: do they spend in this niche (gear, courses, tools, services) or
  are they here to be entertained? This splits the whole tree.
- **Engagement**: comments/saves/shares/email-open, not just followers. Engaged-small
  beats passive-large for direct monetization.
- **Size + platform**: what payout programs and sponsor interest does the size unlock?

## Step 2 — Traverse the tree

Walk [`../../knowledge/monetization-mix-decision-tree.md`](../../knowledge/monetization-mix-decision-tree.md):

- **High intent** → lead with what they buy (products / courses / services /
  memberships); layer sponsorships selectively.
- **Low intent, large** → ad revenue + sponsorships; layer products carefully.
- **Low intent, small** → grow reach + start an email list; affiliate as a bridge.

## Step 3 — Weight toward recurring

Ads and sponsorships are volatile. Wherever the audience supports it, move toward
**memberships/subscriptions** for a stable MRR base. Name the recurring-revenue target.

## Step 4 — Check concentration

- What fraction of revenue depends on **one platform**? On **one sponsor**?
- What fraction of *audience* is on one rented platform with no owned channel?
- If either is catastrophic-to-lose, the top priority becomes diversification +
  owned-audience capture, ahead of squeezing more from the concentrated line.

## Step 5 — Protect trust

Order the mix so trust-spending lines (heavy sponsorship, aggressive affiliate) don't
outpace trust-building. Over-monetization draws down the only compounding asset.

## Step 6 — Output

A prioritized mix: **the revenue lines to start now vs later, the recurring-revenue
target, the concentration/platform-risk call, and the 1–2 conditions that would change
the mix.** Hand sponsorship pricing to [`price-a-brand-deal`](../price-a-brand-deal/SKILL.md)
and audience growth to [`plan-content-and-audience-growth`](../plan-content-and-audience-growth/SKILL.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →