XMoney

Turn messy monetization ideas into clearer revenue decisions. Analyze pricing, payout logic, conversion friction, and revenue model fit for creators, operato...

Security Scan

The skill is an instruction-only monetization advisor whose requested permissions, files, and runtime instructions are consistent with its stated purpose.

Purpose & Capability

Name, description, and declared capabilities (monetization analysis, pricing design, payout logic review) align with the provided SKILL.md and README; there are no unrelated required binaries, env vars, or config paths.

Instruction Scope

SKILL.md contains step-by-step guidance for analyzing monetization (parsing context, scoring friction, comparing options). It does not instruct the agent to read unexpected files, access external endpoints, exfiltrate secrets, or perform payment execution. It also includes appropriate guardrails (no tax/legal/transaction execution).

Install Mechanism

Instruction-only skill with no install spec and no code files that would be written to disk—minimal installation risk.

Credentials

The skill declares no required environment variables, credentials, or config paths and the runtime instructions do not reference hidden secrets; requested inputs are business context only (audience, product, pricing, constraints).

Persistence & Privilege

always is false and autonomous invocation defaults are normal. The skill does not request permanent presence or to modify other skills or system-wide settings.

Assessment

This skill appears coherent and limited to providing monetization advice. Before installing: (1) Don’t provide real credentials or sensitive financial data—this skill doesn’t need them. (2) Remember it will not execute payments or provide legal/tax compliance—use specialists for those. (3) Treat recommendations as advisory: validate suggested pricing/payout changes with real-world tests and professionals. (4) If you plan to allow autonomous agent actions platform-wide, be aware the agent could call this skill when monetization topics arise (this is normal but worth knowing).

Turn messy monetization ideas into clearer revenue decisions.

XMoney is a monetization and revenue-logic skill for creators, operators, and internet businesses.

Here, X is the variable inside the monetization equation: the missing logic, friction, pricing gap, or offer weakness that prevents revenue from flowing cleanly.

Use this skill when you need to:

• improve monetization strategy
• compare pricing models
• simplify payout logic
• diagnose conversion friction
• design cleaner offers
• turn audience, traffic, or product attention into a clearer revenue path

This skill does NOT:

• process payments
• move real money
• replace accounting, tax, or legal advice
• provide regulated financial, banking, or compliance sign-off

---

What This Skill Does

XMoney helps:

• analyze monetization models
• compare revenue structures
• identify conversion friction
• clarify payout logic
• detect value-price mismatch
• improve monetization clarity before execution
• turn vague money ideas into decision-ready monetization plans

---

Best Use Cases

• creator monetization strategy
• pricing model redesign
• payout structure analysis
• subscription vs one-time comparison
• offer engineering
• revenue audit for digital businesses
• creator economy monetization planning
• platform earnings logic review

---

What to Provide

Useful input includes:

• business model
• audience type
• product or offer
• current monetization method
• price points
• conversion or payout pain points
• platform constraints
• revenue goal
• known risks or tradeoffs

If information is incomplete, this skill should identify what is missing before overconfident recommendations are made.

---

Standard Output Format

XMONEY ASSESSMENT
━━━━━━━━━━━━━━━━━━━━━━━━━━ Revenue Model: [Current / Proposed]
Main Monetization Goal: [What money decision is being improved]

CORE ISSUES
━━━━━━━━━━━━━━━━━━━━━━━━━━ Monetization Friction Score: [1-10]
Value-Price Gap: [Overpriced / Underpriced / Balanced]

• [Pricing issue]
• [Payout issue]
• [Conversion issue]
• [Revenue logic issue]

MODEL OPTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━

1. [Option A] — [why it may fit]
2. [Option B] — [why it may fit]
3. [Option C] — [why it may fit]

TRADEOFFS
━━━━━━━━━━━━━━━━━━━━━━━━━━ ⚠️ [Risk or downside] ⚠️ [Complexity or dependency] ⚠️ [Constraint or unknown]

RECOMMENDED NEXT STEP
━━━━━━━━━━━━━━━━━━━━━━━━━━

• [What to test, simplify, or change next]

---

Revenue Principles

• price should match value logic
• payout rules should be understandable
• monetization should reduce friction, not add hidden complexity
• revenue design should reflect audience behavior
• unclear commercial structure slows growth
• complexity is the tax on conversion
• never confuse revenue potential with monetization fit

---

Friction Review

When analyzing monetization, check for:

Pricing Friction

• price feels arbitrary
• value is unclear
• anchor or benchmark is missing
• offer tiers create confusion rather than clarity

Offer Friction

• buyer does not understand what they are paying for
• too many options
• weak packaging
• weak differentiation between free and paid value

Payout Friction

• earnings logic is hard to understand
• incentives are mismatched
• creator or partner payout feels opaque
• payout timing creates distrust

Conversion Friction

• too many steps before payment
• audience intent does not match offer design
• monetization path is unclear
• monetization logic depends on unrealistic user behavior

---

Pricing Anchor Check

Before recommending or evaluating a price, ask:

• Is there a useful reference point?

  • market benchmark
  • cost of alternative
  • internal build cost
  • competitor anchor

• Is there a value-to-price ratio?

  • what result or leverage does the buyer get relative to price?

• Is there a cost-of-inaction anchor?

  • what is lost by waiting, delaying, or keeping the current setup?

Do not present price as a naked number if a clearer commercial frame is available.

---

Execution Protocol (for AI agents)

When user asks about monetization or payout logic, follow this sequence:

Step 1: Parse business context

Extract:

• who is earning
• what is being sold
• how money currently flows
• what constraints exist
• what outcome the user wants

Step 2: Identify monetization problem

Classify the main issue:

• weak pricing
• weak conversion
• weak monetization fit
• payout complexity
• incentive mismatch
• unclear offer ladder
• poor value communication

Step 3: Score friction

Estimate:

• Monetization Friction Score (1-10)
• Value-Price Gap (Overpriced / Underpriced / Balanced)

Use these as judgment tools, not fake precision.

Step 4: Compare options

Evaluate realistic alternatives such as:

• subscription
• one-time purchase
• commission
• usage-based
• tiered pricing
• hybrid models

Step 5: Show tradeoffs

Explain:

• upside
• downside
• complexity
• operational friction
• dependency risk

Step 6: Recommend next move

Return:

• clearest monetization path
• what to test next
• what to simplify
• what assumptions still need validation

Step 7: Guardrails

If tax, regulated payments, custody, or legal obligations are central:

• say so clearly
• do not fake certainty
• recommend specialist review

---

Activation Rules (for AI agents)

Use this skill when the user asks about:

• monetization strategy
• pricing logic
• payout structure
• creator revenue
• subscription models
• revenue model fit
• offer design
• conversion logic
• revenue audit
• creator economy monetization

Do NOT use this skill when:

• user needs formal tax advice
• user needs legal or compliance sign-off
• user needs live payment execution
• user wants banking, treasury, or regulated financial setup
• user wants pure investment advice rather than monetization design

If context is ambiguous

Ask: "Do you want help with monetization strategy and pricing logic, or with accounting / legal / payment execution?"

---

Works Well With

• @ethagent/content for content monetization systems
• @ethagent/brand for offer positioning
• @ethagent/launch for monetization rollout planning

---

Boundaries

This skill supports monetization strategy, pricing logic, payout clarity, and revenue-model analysis.

It does not replace:

• accounting advice
• tax advice
• legal review
• payment processor compliance
• banking or treasury functions

Use outputs as commercial analysis, not regulated sign-off.