Setting Pricing
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.
Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.
Install Monetization Strategy
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install phuryn/pm-skills monetization-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .claude/skills/monetization-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .claude/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install phuryn/pm-skills monetization-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .agents/skills/monetization-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .agents/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install phuryn/pm-skills monetization-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .cursor/skills/monetization-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .cursor/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/phuryn/pm-skills.git --path pm-product-strategy/skills/monetization-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install phuryn/pm-skills monetization-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .gemini/skills/monetization-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .gemini/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install phuryn/pm-skills monetization-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .github/skills/monetization-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .github/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill monetization-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install phuryn/pm-skills monetization-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pm-product-strategy/skills/monetization-strategy .opencode/skills/monetization-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "monetization-strategy" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-product-strategy/skills/monetization-strategy into .opencode/skills/monetization-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monetization-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
monetization-strategy- GitHub stars
- 27k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 789 words
- Files
- 1
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- MIT
At a glance
Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.
- Works in 12 steps: Strategy Name & Description → How It Works → Audience Fit → …
- Exploring revenue models
- SKILL.md covers Metadata, Instructions, Input Requirements and Monetization Framework, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Monetization Strategy is an agent skill from phuryn/pm-skills. Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Pricing strategy, Financial modeling and Brainstorming. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.
When your agent uses it
- Exploring revenue models
- Evaluating pricing strategies
- Deciding how to monetize a product
Example prompts
- “/monetization-strategy”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8607e3b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
productcompass.pm
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Monetization Strategy loads about 1.7k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 789 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 789 words, ~1,665 tokens.
Download SKILL.mdSave it as
.claude/skills/monetization-strategy/SKILL.md (or your agent's skills folder).- name
- monetization-strategy
- description
- Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product.
Monetization Strategy
Metadata
- Name: monetization-strategy
- Description: Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, pricing strategies, or business model options.
- Triggers: monetization strategy, revenue model, pricing strategy, how to monetize, make money
Instructions
You are an experienced business model strategist brainstorming monetization strategies for $ARGUMENTS.
Your task is to develop 3-5 distinct monetization approaches that could work for the product or feature, evaluate fit with the target market, and outline low-effort validation experiments.
Input Requirements
- Product or feature description
- Target market segment(s) and customer profile
- Current willingness to pay or budget constraints
- Competitive monetization approaches
- Company priorities (revenue growth, user growth, profitability)
Monetization Framework
For each strategy, include:
1. Strategy Name & Description
- What is the monetization model?
- How does it work for this product?
- Who pays and what do they get?
2. How It Works
- Revenue model and pricing mechanics
- Value exchange between company and customer
- Payment frequency and transaction size
- Lifecycle and retention mechanisms
3. Audience Fit
- Why does this resonate with your target customer?
- How does it align with customer needs and preferences?
- What problems does it solve for the customer?
- Addressable market size and revenue potential
4. Unit Economics
- Estimated customer acquisition cost (CAC)
- Estimated customer lifetime value (LTV)
- Break-even timeline
- Target gross margin
5. Risks & Challenges
- Market adoption risk
- Pricing or feature sensitivity
- Competitive vulnerability
- Customer churn or resistance
- Implementation complexity
6. Competitive Position
- How do competitors monetize?
- What makes your approach differentiated?
- Barriers to customer switching
- Defense against competitive pricing
7. Validation Experiment
- Low-cost test to validate customer willingness to pay
- Method: survey, landing page, pilot, freemium, waitlist
- Success metric and decision criteria
- Timeline and resources required
Example Monetization Strategies
1. Freemium (Free Base + Paid Premium)
- How: Free core features, premium advanced features behind paywall
- Fit: Best for high-volume, low-touch products (design tools, productivity, communication)
- Risks: Low conversion rates (typically 1-5%), features must be clear to justify upgrade
- Experiment: Launch freemium version, track conversion rate, gather upgrade feedback
2. Subscription (Recurring Monthly/Annual)
- How: Recurring charge for ongoing access and updates
- Fit: Best for products with continuous value (software, platforms, services)
- Risks: Customer churn, cannibalization from annual vs. monthly
- Experiment: Offer subscription to beta customers, measure churn rate and NPS
3. Usage-Based (Pay Per Use)
- How: Customers pay based on usage volume (API calls, storage, transactions)
- Fit: Best for B2B platforms, APIs, services with variable customer needs
- Risks: Unpredictable revenue, customer cost anxiety, usage optimization by customers
- Experiment: Implement usage tracking, pilot with 5-10 beta customers, model revenue
4. Enterprise/Seat-Based (Per User/Seat)
- How: Price per user, department, or seat using the product
- Fit: Best for B2B SaaS with team/organization adoption
- Risks: Sales complexity, contract length, implementation overhead
- Experiment: Conduct 5-10 customer interviews, validate pricing per seat, define support model
Show full SKILL.md (328 more words)Show less
5. One-Time Purchase (Buy Once)
- How: Single upfront purchase for permanent or one-time license
- Fit: Best for niche products, tools, or templates (not ongoing services)
- Risks: Revenue concentration in launch period, no recurring revenue, updates/support questions
- Experiment: Launch limited offering, track conversion and customer satisfaction
6. Marketplace/Transaction Fee
- How: Take a percentage or fixed fee from transactions between buyers and sellers
- Fit: Best for platforms connecting supply and demand
- Risks: Market liquidity chicken-and-egg problem, trust and safety, competitive pressure
- Experiment: MVP with limited sellers, offer free period to drive initial supply, model unit economics
7. Advertising/Sponsorship
- How: Generate revenue from ads, sponsored content, or brand partnerships
- Fit: Best for high-traffic, consumer-facing products
- Risks: Brand damage from intrusive ads, user experience degradation, advertiser concentration
- Experiment: Test ads with small user segment, measure engagement and revenue impact
Output Process
- Brainstorm 3-5 distinct monetization strategies (avoid repeating similar models)
- For each strategy:
- Describe how it works specifically for this product
- Assess fit with target customer and willingness to pay
- Outline key risks and challenges
- Estimate unit economics (CAC, LTV, timeline)
- Compare against competitive approaches
- For each strategy, design a low-effort validation experiment
- Prioritize by:
- Strategic fit (revenue, growth, profitability goals)
- Ease of implementation
- Market validation potential
- Competitive advantage
- Recommend 1-2 strategies to test first
- Create testing roadmap and success criteria
Strategic Considerations
- Revenue Goals: How much revenue is needed? By when?
- Growth Goals: Does monetization need to support user growth?
- Market Dynamics: Are customers ready to pay? For what?
- Competitive Pressure: How will competitors respond?
- Unit Economics: What gross margin is required for viability?
Notes
- Best monetization strategies align with customer value and willingness to pay
- Test early and often; don't wait for perfect product to validate pricing
- Most products use hybrid models (e.g., freemium + upgrade, subscription + marketplace fees)
- Pricing can be changed; customer relationships are harder to rebuild
- Monitor competitors but don't race to the bottom on price
Further Reading
© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pm-product-strategy/skills/monetization-strategy of phuryn/pm-skills.
Open the folder on GitHubat commit 8607e3b
Compare with similar skills
Monetization Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Monetization Strategy this skillphuryn/pm-skills | 27k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Setting PricingGTM-Strategist/gtm-strategist-skills | 261 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Finance-Based Pricing Advisordeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~5.9k | Automated safety check: Pass | Custom licence | |
| Pricing Strategyemotixco/claude-skills-founder | 517 | — | ~774 | Automated safety check: Pass | MIT | |
| Price Optimization Toolnexscope-ai/eCommerce-Skills | 1.1k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Exploration Modefjrevoredo/mini-diarium | 308 | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Finance-Based Pricing Advisor
deanpeters/Product-Manager-Skills
Evaluates a proposed pricing change by modeling its effect on ARPU, conversion, churn risk, expansion and CAC payback, for a go or no-go decision.
Pricing Strategy
emotixco/claude-skills-founder
Design pricing for a product. An agent skill from emotixco/claude-skills-founder.
Price Optimization Tool
nexscope-ai/eCommerce-Skills
Evaluate ecommerce price candidates using unit economics, historical observations, elasticity analysis, scenario modeling, and controlled experiments.
Exploration Mode
fjrevoredo/mini-diarium
Enter exploration mode: a thinking partner for researching and thinking through ideas and problems before implementation.
AI Product Pricing
tech-leads-club/agent-skills
Helps founders and product teams choose a charge metric, shape pricing tiers and set margin targets for AI products whose compute costs rise with usage.
More from phuryn/pm-skills
All 60 skills in this repoAgreement-Based Code Review
phuryn/pm-skills
Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.
A/B Test Analysis
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
Team OKR Brainstorm
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
Cohort Analysis and Retention Explorer
phuryn/pm-skills
Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.
Dummy Dataset Generator
phuryn/pm-skills
Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.
Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Related
Questions about Monetization Strategy
What does Monetization Strategy do?
Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Monetization Strategy is an agent skill from phuryn/pm-skills. Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.
When should I use Monetization Strategy?
Monetization Strategy fits situations like: exploring revenue models; evaluating pricing strategies; deciding how to monetize a product.
How do I install Monetization Strategy in Claude Code?
Run `npx skills add phuryn/pm-skills --skill monetization-strategy -a claude-code`. Or copy the skill folder (pm-product-strategy/skills/monetization-strategy in phuryn/pm-skills) into .claude/skills/monetization-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Monetization Strategy in Codex?
Run `npx skills add phuryn/pm-skills --skill monetization-strategy -a codex`. Or copy the skill folder (pm-product-strategy/skills/monetization-strategy in phuryn/pm-skills) into .agents/skills/monetization-strategy in your project. Codex loads it when a task matches its description.
Can I use Monetization Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill monetization-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monetization-strategy, .gemini/skills/monetization-strategy, .github/skills/monetization-strategy and .opencode/skills/monetization-strategy in your project.
What does Monetization Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Monetization Strategy is instructions for the agent only.
Does Monetization Strategy access the network?
SKILL.md names 1 domain. As links in the text: productcompass.pm. This is read from the text; nothing was executed.
Is Monetization Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Monetization Strategy use?
Monetization Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Monetization Strategy use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Monetization Strategy?
Skills that share tags, products or a category with Monetization Strategy: Setting Pricing (GTM-Strategist/gtm-strategist-skills, 261 stars), Finance-Based Pricing Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Pricing Strategy (emotixco/claude-skills-founder, 517 stars) and Price Optimization Tool (nexscope-ai/eCommerce-Skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monetization Strategy?
phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,825 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on September 14, 2026.
Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.