cc-skill:pricing-and-monetization

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you set up payment systems and pricing tiers for Jay's six products. It tells you which payment provider to use (Stripe, Paystack, or both), what price points work best for each product, and how to structure trials, subscriptions, and credits based on what customers actually buy.

who it is for

Founders, product managers, and anyone deciding how to charge customers or integrate payments into a product.

when it fires

You mention pricing, subscription tiers, payment methods, Stripe, Paystack, billing, trials, monetization models, freemium plans, or ask 'how should I charge for this'.

say something like

"What pricing should we use for ArbiCall in Nigeria?"
"How do I set up payments for SwarmTrade?"
"Should we use Stripe or Paystack for our next launch?"

what you might get back

For ArbiCall, use Paystack as your primary payment method because your users are Nigerian and prefer OPay and PalmPay wallets. Offer a free tier with 3 calls per week, credit packs (10 calls for 500 naira), and a 2,500 naira monthly subscription for unlimited calls. This hybrid model beats a subscription-only approach because Nigerians prefer prepaid buying.

how to know it worked

You will know it worked correctly because the skill recommends a specific payment provider (Stripe, Paystack, or both) matched to your customer location, and suggests concrete price points tied to one of Jay's six existing products.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/pricing-and-monetization/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when working on pricing tiers, payment integrations, monetization models, billing systems, payment provider choices, trial logic, freemium decisions, or revenue strategy for any of Jay's products. Triggers on "pricing", "monetization",

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/pricing-and-monetization/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when working on pricing tiers, payment integrations, monetization models, billing systems, payment provider choices, trial logic, freemium decisions, or revenue strategy for any of Jay's products. Triggers on \"pricing\", \"monetization\", \"tiers\", \"subscription\", \"Stripe\", \"Paystack\", \"billing\", \"trial\", \"freemium\", \"credits\", \"payment\", \"revenue model\", or \"how should I charge for this\"."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/pricing-and-monetization/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.