[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE2SX41CFZD7G2TKXNES55":3,"skill-same:01M6AE2SX41CFZD7G2TKXNES55":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AE2SX41CFZD7G2TKXNES55","pricing-strategy",null,"When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fpricing-strategy\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"pricing","pricing strategy","strategy","when","research","value","metric","pay","with","monetization strategy","price","free","structure","monetization","use","packaging","user","decisions","help","2026-11-10 10:12:30",false,"---\nname: pricing-strategy\ndescription: \"When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.\"\n---\n\n# Pricing Strategy\n\nYou are an expert in SaaS pricing and monetization strategy with access to pricing research data and analysis tools. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.\n\n## Before Starting\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What type of product? (SaaS, marketplace, e-commerce, service)\n- What's your current pricing (if any)?\n- What's your target market? (SMB, mid-market, enterprise)\n- What's your go-to-market motion? (self-serve, sales-led, hybrid)\n\n### 2. Value & Competition\n- What's the primary value you deliver?\n- What alternatives do customers consider?\n- How do competitors price?\n- What makes you different\u002Fbetter?\n\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your average revenue per user (ARPU)?\n- What's your churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Are you optimizing for growth, revenue, or profitability?\n- Are you trying to move upmarket or expand downmarket?\n- Any pricing changes you're considering?\n\n---\n\n## Pricing Fundamentals\n\n### The Three Pricing Axes\n\nEvery pricing decision involves three dimensions:\n\n**1. Packaging** — What's included at each tier?\n- Features, limits, support level\n- How tiers differ from each other\n\n**2. Pricing Metric** — What do you charge for?\n- Per user, per usage, flat fee\n- How price scales with value\n\n**3. Price Point** — How much do you charge?\n- The actual dollar amounts\n- The perceived value vs. cost\n\n### Value-Based Pricing Framework\n\nPrice should be based on value delivered, not cost to serve:\n\n```\n┌─────────────────────────────────────────────────────────┐\n│                                                         │\n│  Customer's perceived value of your solution            │\n│  ────────────────────────────────────────────── $1000   │\n│                                                         │\n│  ↑ Value captured (your opportunity)                    │\n│                                                         │\n│  Your price                                             │\n│  ────────────────────────────────────────────── $500    │\n│                                                         │\n│  ↑ Consumer surplus (value customer keeps)              │\n│                                                         │\n│  Next best alternative                                  │\n│  ────────────────────────────────────────────── $300    │\n│                                                         │\n│  ↑ Differentiation value                                │\n│                                                         │\n│  Your cost to serve                                     │\n│  ────────────────────────────────────────────── $50     │\n│                                                         │\n└─────────────────────────────────────────────────────────┘\n```\n\n**Key insight:** Price between the next best alternative and perceived value. Cost is a floor, not a basis.\n\n---\n\n## Pricing Research Methods\n\n### Van Westendorp Price Sensitivity Meter\n\nThe Van Westendorp survey identifies the acceptable price range for your product.\n\n**The Four Questions:**\n\nAsk each respondent:\n1. \"At what price would you consider [product] to be so expensive that you would not consider buying it?\" (Too expensive)\n2. \"At what price would you consider [product] to be priced so low that you would question its quality?\" (Too cheap)\n3. \"At what price would you consider [product] to be starting to get expensive, but you still might consider it?\" (Expensive\u002Fhigh side)\n4. \"At what price would you consider [product] to be a bargain—a great buy for the money?\" (Cheap\u002Fgood value)\n\n**How to Analyze:**\n\n1. Plot cumulative distributions for each question\n2. Find the intersections:\n   - **Point of Marginal Cheapness (PMC):** \"Too cheap\" crosses \"Expensive\"\n   - **Point of Marginal Expensiveness (PME):** \"Too expensive\" crosses \"Cheap\"\n   - **Optimal Price Point (OPP):** \"Too cheap\" crosses \"Too expensive\"\n   - **Indifference Price Point (IDP):** \"Expensive\" crosses \"Cheap\"\n\n**The acceptable price range:** PMC to PME\n**Optimal pricing zone:** Between OPP and IDP\n\n**Survey Tips:**\n- Need 100-300 respondents for reliable data\n- Segment by persona (different willingness to pay)\n- Use realistic product descriptions\n- Consider adding purchase intent questions\n\n**Sample Van Westendorp Analysis Output:**\n\n```\nPrice Sensitivity Analysis Results:\n─────────────────────────────────\nPoint of Marginal Cheapness:  $29\u002Fmo\nOptimal Price Point:          $49\u002Fmo\nIndifference Price Point:     $59\u002Fmo\nPoint of Marginal Expensiveness: $79\u002Fmo\n\nRecommended range: $49-59\u002Fmo\nCurrent price: $39\u002Fmo (below optimal)\nOpportunity: 25-50% price increase without significant demand impact\n```\n\n### MaxDiff Analysis (Best-Worst Scaling)\n\nMaxDiff identifies which features customers value most, informing packaging decisions.\n\n**How It Works:**\n\n1. List 8-15 features you could include\n2. Show respondents sets of 4-5 features at a time\n3. Ask: \"Which is MOST important? Which is LEAST important?\"\n4. Repeat across multiple sets until all features compared\n5. Statistical analysis produces importance scores\n\n**Example Survey Question:**\n\n```\nWhich feature is MOST important to you?\nWhich feature is LEAST important to you?\n\n□ Unlimited projects\n□ Custom branding\n□ Priority support\n□ API access\n□ Advanced analytics\n```\n\n**Analyzing Results:**\n\nFeatures are ranked by utility score:\n- High utility = Must-have (include in base tier)\n- Medium utility = Differentiator (use for tier separation)\n- Low utility = Nice-to-have (premium tier or cut)\n\n**Using MaxDiff for Packaging:**\n\n| Utility Score | Packaging Decision |\n|---------------|-------------------|\n| Top 20% | Include in all tiers (table stakes) |\n| 20-50% | Use to differentiate tiers |\n| 50-80% | Higher tiers only |\n| Bottom 20% | Consider cutting or premium add-on |\n\n### Willingness to Pay Surveys\n\n**Direct method (simple but biased):**\n\"How much would you pay for [product]?\"\n\n**Better: Gabor-Granger method:**\n\"Would you buy [product] at [$X]?\" (Yes\u002FNo)\nVary price across respondents to build demand curve.\n\n**Even better: Conjoint analysis:**\nShow product bundles at different prices\nRespondents choose preferred option\nStatistical analysis reveals price sensitivity per feature\n\n---\n\n## Value Metrics\n\n### What is a Value Metric?\n\nThe value metric is what you charge for—it should scale with the value customers receive.\n\n**Good value metrics:**\n- Align price with value delivered\n- Are easy to understand\n- Scale as customer grows\n- Are hard to game\n\n### Common Value Metrics\n\n| Metric | Best For | Example |\n|--------|----------|---------|\n| Per user\u002Fseat | Collaboration tools | Slack, Notion |\n| Per usage | Variable consumption | AWS, Twilio |\n| Per feature | Modular products | HubSpot add-ons |\n| Per contact\u002Frecord | CRM, email tools | Mailchimp, HubSpot |\n| Per transaction | Payments, marketplaces | Stripe, Shopify |\n| Flat fee | Simple products | Basecamp |\n| Revenue share | High-value outcomes | Affiliate platforms |\n\n### Choosing Your Value Metric\n\n**Step 1: Identify how customers get value**\n- What outcome do they care about?\n- What do they measure success by?\n- What would they pay more for?\n\n**Step 2: Map usage to value**\n\n| Usage Pattern | Value Delivered | Potential Metric |\n|---------------|-----------------|------------------|\n| More team members use it | More collaboration value | Per user |\n| More data processed | More insights | Per record\u002Fevent |\n| More revenue generated | Direct ROI | Revenue share |\n| More projects managed | More organization | Per project |\n\n**Step 3: Test for alignment**\n\nAsk: \"As a customer uses more of [metric], do they get more value?\"\n- If yes → good value metric\n- If no → price doesn't align with value\n\n### Mapping Usage to Value: Framework\n\n**1. Instrument usage data**\nTrack how customers use your product:\n- Feature usage frequency\n- Volume metrics (users, records, API calls)\n- Outcome metrics (revenue generated, time saved)\n\n**2. Correlate with customer success**\n- Which usage patterns predict retention?\n- Which usage patterns predict expansion?\n- Which customers pay the most, and why?\n\n**3. Identify value thresholds**\n- At what usage level do customers \"get it\"?\n- At what usage level do they expand?\n- At what usage level should price increase?\n\n**Example Analysis:**\n\n```\nUsage-Value Correlation Analysis:\n─────────────────────────────────\nSegment: High-LTV customers (>$10k ARR)\nAverage monthly active users: 15\nAverage projects: 8\nAverage integrations: 4\n\nSegment: Churned customers\nAverage monthly active users: 3\nAverage projects: 2\nAverage integrations: 0\n\nInsight: Value correlates with team adoption (users)\n        and depth of use (integrations)\n\nRecommendation: Price per user, gate integrations to higher tiers\n```\n\n---\n\n## Tier Structure\n\n### How Many Tiers?\n\n**2 tiers:** Simple, clear choice\n- Works for: Clear SMB vs. Enterprise split\n- Risk: May leave money on table\n\n**3 tiers:** Industry standard\n- Good tier = Entry point\n- Better tier = Recommended (anchor to best)\n- Best tier = High-value customers\n\n**4+ tiers:** More granularity\n- Works for: Wide range of customer sizes\n- Risk: Decision paralysis, complexity\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):**\n- Purpose: Remove barriers to entry\n- Includes: Core features, limited usage\n- Price: Low, accessible\n- Target: Small teams, try before you buy\n\n**Better tier (Recommended):**\n- Purpose: Where most customers land\n- Includes: Full features, reasonable limits\n- Price: Your \"anchor\" price\n- Target: Growing teams, serious users\n\n**Best tier (Premium):**\n- Purpose: Capture high-value customers\n- Includes: Everything, advanced features, higher limits\n- Price: Premium (often 2-3x \"Better\")\n- Target: Larger teams, power users, enterprises\n\n### Tier Differentiation Strategies\n\n**Feature gating:**\n- Basic features in all tiers\n- Advanced features in higher tiers\n- Works when features have clear value differences\n\n**Usage limits:**\n- Same features, different limits\n- More users, storage, API calls at higher tiers\n- Works when value scales with usage\n\n**Support level:**\n- Email support → Priority support → Dedicated success\n- Works for products with implementation complexity\n\n**Access and customization:**\n- API access, SSO, custom branding\n- Works for enterprise differentiation\n\n### Example Tier Structure\n\n```\n┌────────────────┬─────────────────┬─────────────────┬─────────────────┐\n│                │ Starter         │ Pro             │ Business        │\n│                │ $29\u002Fmo          │ $79\u002Fmo          │ $199\u002Fmo         │\n├────────────────┼─────────────────┼─────────────────┼─────────────────┤\n│ Users          │ Up to 5         │ Up to 20        │ Unlimited       │\n│ Projects       │ 10              │ Unlimited       │ Unlimited       │\n│ Storage        │ 5 GB            │ 50 GB           │ 500 GB          │\n│ Integrations   │ 3               │ 10              │ Unlimited       │\n│ Analytics      │ Basic           │ Advanced        │ Custom          │\n│ Support        │ Email           │ Priority        │ Dedicated       │\n│ API Access     │ ✗               │ ✓               │ ✓               │\n│ SSO            │ ✗               │ ✗               │ ✓               │\n│ Audit logs     │ ✗               │ ✗               │ ✓               │\n└────────────────┴─────────────────┴─────────────────┴─────────────────┘\n```\n\n---\n\n## Packaging for Personas\n\n### Identifying Pricing Personas\n\nDifferent customers have different:\n- Willingness to pay\n- Feature needs\n- Buying processes\n- Value perception\n\n**Segment by:**\n- Company size (solopreneur → SMB → enterprise)\n- Use case (marketing vs. sales vs. support)\n- Sophistication (beginner → power user)\n- Industry (different budget norms)\n\n### Persona-Based Packaging\n\n**Step 1: Define personas**\n\n| Persona | Size | Needs | WTP | Example |\n|---------|------|-------|-----|---------|\n| Freelancer | 1 person | Basic features | Low | $19\u002Fmo |\n| Small Team | 2-10 | Collaboration | Medium | $49\u002Fmo |\n| Growing Co | 10-50 | Scale, integrations | Higher | $149\u002Fmo |\n| Enterprise | 50+ | Security, support | High | Custom |\n\n**Step 2: Map features to personas**\n\n| Feature | Freelancer | Small Team | Growing | Enterprise |\n|---------|------------|------------|---------|------------|\n| Core features | ✓ | ✓ | ✓ | ✓ |\n| Collaboration | — | ✓ | ✓ | ✓ |\n| Integrations | — | Limited | Full | Full |\n| API access | — | — | ✓ | ✓ |\n| SSO\u002FSAML | — | — | — | ✓ |\n| Audit logs | — | — | — | ✓ |\n| Custom contract | — | — | — | ✓ |\n\n**Step 3: Price to value for each persona**\n- Research willingness to pay per segment\n- Set prices that capture value without blocking adoption\n- Consider segment-specific landing pages\n\n---\n\n## Freemium vs. Free Trial\n\n### When to Use Freemium\n\n**Freemium works when:**\n- Product has viral\u002Fnetwork effects\n- Free users provide value (content, data, referrals)\n- Large market where % conversion drives volume\n- Low marginal cost to serve free users\n- Clear feature\u002Fusage limits for upgrade trigger\n\n**Freemium risks:**\n- Free users may never convert\n- Devalues product perception\n- Support costs for non-paying users\n- Harder to raise prices later\n\n**Example: Slack**\n- Free tier for small teams\n- Message history limit creates upgrade trigger\n- Free users invite others (viral growth)\n- Converts when team hits limit\n\n### When to Use Free Trial\n\n**Free trial works when:**\n- Product needs time to demonstrate value\n- Onboarding\u002Fsetup investment required\n- B2B with buying committees\n- Higher price points\n- Product is \"sticky\" once configured\n\n**Trial best practices:**\n- 7-14 days for simple products\n- 14-30 days for complex products\n- Full access (not feature-limited)\n- Clear countdown and reminders\n- Credit card optional vs. required trade-off\n\n**Credit card upfront:**\n- Higher trial-to-paid conversion (40-50% vs. 15-25%)\n- Lower trial volume\n- Better qualified leads\n\n### Hybrid Approaches\n\n**Freemium + Trial:**\n- Free tier with limited features\n- Trial of premium features\n- Example: Zoom (free 40-min, trial of Pro)\n\n**Reverse trial:**\n- Start with full access\n- After trial, downgrade to free tier\n- Example: See premium value, live with limitations until ready\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- You're significantly cheaper than alternatives\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Very high conversion rates (>40%)\n- Very low churn (\u003C3% monthly)\n- Customers using more than they pay for\n- Unit economics are strong\n\n**Product signals:**\n- You've added significant value since last pricing\n- Product is more mature\u002Fstable\n- New features justify higher price\n\n### Price Increase Strategies\n\n**1. Grandfather existing customers**\n- New price for new customers only\n- Existing customers keep old price\n- Pro: No churn risk\n- Con: Leaves money on table, creates complexity\n\n**2. Delayed increase for existing**\n- Announce increase 3-6 months out\n- Give time to lock in old price (annual)\n- Pro: Fair, drives annual conversions\n- Con: Some churn, requires communication\n\n**3. Increase tied to value**\n- Raise price but add features\n- \"New Pro tier with X, Y, Z\"\n- Pro: Justified increase\n- Con: Requires actual new value\n\n**4. Plan restructure**\n- Change plans entirely\n- Existing customers mapped to nearest fit\n- Pro: Clean slate\n- Con: Disruptive, requires careful mapping\n\n### Communicating Price Increases\n\n**For new customers:**\n- Just update pricing page\n- No announcement needed\n- Monitor conversion rate\n\n**For existing customers:**\n\n```\nSubject: Updates to [Product] pricing\n\nHi [Name],\n\nI'm writing to let you know about upcoming changes to [Product] pricing.\n\n[Context: what you've added, why change is happening]\n\nStarting [date], our pricing will change from [old] to [new].\n\nAs a valued customer, [what this means for them: grandfathered, locked rate, timeline].\n\n[If they're affected:]\nYou have until [date] to [action: lock in current rate, renew at old price].\n\n[If they're grandfathered:]\nYou'll continue at your current rate. No action needed.\n\nWe appreciate your continued support of [Product].\n\n[Your name]\n```\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Tier Presentation\n\n- Lead with the recommended tier (visual emphasis)\n- Show value progression clearly\n- Use checkmarks and limits, not paragraphs\n- Anchor to higher tier (show enterprise first or savings)\n\n### Common Elements\n\n- [ ] Feature comparison table\n- [ ] Who each tier is for\n- [ ] FAQ section\n- [ ] Contact sales option\n- [ ] Annual discount callout\n- [ ] Money-back guarantee\n- [ ] Customer logos\u002Ftrust signals\n\n### Pricing Psychology to Apply\n\n- **Anchoring:** Show higher-priced option first\n- **Decoy effect:** Middle tier should be obviously best value\n- **Charm pricing:** $49 vs. $50 (for value-focused)\n- **Round pricing:** $50 vs. $49 (for premium)\n- **Annual savings:** Show monthly price but offer annual discount (17-20%)\n\n---\n\n## Price Testing\n\n### Methods for Testing Price\n\n**1. A\u002FB test pricing page (risky)**\n- Different visitors see different prices\n- Ethical\u002Flegal concerns\n- May damage trust if discovered\n\n**2. Geographic testing**\n- Test higher prices in new markets\n- Different currencies\u002Fregions\n- Cleaner test, limited reach\n\n**3. New customer only**\n- Raise prices for new customers\n- Compare conversion rates\n- Monitor cohort LTV\n\n**4. Sales team discretion**\n- Test higher quotes through sales\n- Track close rates at different prices\n- Works for sales-led GTM\n\n**5. Feature-based testing**\n- Test different packaging\n- Add premium tier at higher price\n- See adoption without changing existing\n\n### What to Measure\n\n- Conversion rate at each price point\n- Average revenue per user (ARPU)\n- Total revenue (conversion × price)\n- Customer lifetime value\n- Churn rate by price paid\n- Price sensitivity by segment\n\n---\n\n## Enterprise Pricing\n\n### When to Add Custom Pricing\n\nAdd \"Contact Sales\" when:\n- Deal sizes exceed $10k+ ARR\n- Customers need custom contracts\n- Implementation\u002Fonboarding required\n- Security\u002Fcompliance requirements\n- Procurement processes involved\n\n### Enterprise Tier Elements\n\n**Table stakes:**\n- SSO\u002FSAML\n- Audit logs\n- Admin controls\n- Uptime SLA\n- Security certifications\n\n**Value-adds:**\n- Dedicated support\u002Fsuccess\n- Custom onboarding\n- Training sessions\n- Custom integrations\n- Priority roadmap input\n\n### Enterprise Pricing Strategies\n\n**Per-seat at scale:**\n- Volume discounts for large teams\n- Example: $15\u002Fuser (standard) → $10\u002Fuser (100+)\n\n**Platform fee + usage:**\n- Base fee for access\n- Usage-based above thresholds\n- Example: $500\u002Fmo base + $0.01 per API call\n\n**Value-based contracts:**\n- Price tied to customer's revenue\u002Foutcomes\n- Example: % of transactions, revenue share\n\n---\n\n## Pricing Checklist\n\n### Before Setting Prices\n\n- [ ] Defined target customer personas\n- [ ] Researched competitor pricing\n- [ ] Identified your value metric\n- [ ] Conducted willingness-to-pay research\n- [ ] Mapped features to tiers\n\n### Pricing Structure\n\n- [ ] Chosen number of tiers\n- [ ] Differentiated tiers clearly\n- [ ] Set price points based on research\n- [ ] Created annual discount strategy\n- [ ] Planned enterprise\u002Fcustom tier\n\n### Validation\n\n- [ ] Tested pricing with target customers\n- [ ] Reviewed pricing with sales team\n- [ ] Validated unit economics work\n- [ ] Planned for price increases\n- [ ] Set up tracking for pricing metrics\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What pricing research have you done (surveys, competitor analysis)?\n2. What's your current ARPU and conversion rate?\n3. What's your primary value metric (what do customers pay for value)?\n4. Who are your main pricing personas (by size, use case)?\n5. Are you self-serve, sales-led, or hybrid?\n6. What pricing changes are you considering?\n\n---\n\n## Related Skills\n\n- **page-cro**: For optimizing pricing page conversion\n- **copywriting**: For pricing page copy\n- **marketing-psychology**: For pricing psychology principles\n- **ab-test-setup**: For testing pricing changes\n- **analytics-tracking**: For tracking pricing metrics\n","# Pricing Strategy\n\nYou are an expert in SaaS pricing and monetization strategy with access to pricing research data and analysis tools. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.\n\n## Before Starting\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What type of product? (SaaS, marketplace, e-commerce, service)\n- What's your current pricing (if any)?\n- What's your target market? (SMB, mid-market, enterprise)\n- What's your go-to-market motion? (self-serve, sales-led, hybrid)\n\n### 2. Value & Competition\n- What's the primary value you deliver?\n- What alternatives do customers consider?\n- How do competitors price?\n- What makes you different\u002Fbetter?\n\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your average revenue per user (ARPU)?\n- What's your churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Are you optimizing for growth, revenue, or profitability?\n- Are you trying to move upmarket or expand downmarket?\n- Any pricing changes you're considering?\n\n---\n\n## Pricing Fundamentals\n\n### The Three Pricing Axes\n\nEvery pricing decision involves three dimensions:\n\n**1. Packaging** — What's included at each tier?\n- Features, limits, support level\n- How tiers differ from each other\n\n**2. Pricing Metric** — What do you charge for?\n- Per user, per usage, flat fee\n- How price scales with value\n\n**3. Price Point** — How much do you charge?\n- The actual dollar amounts\n- The perceived value vs. cost\n\n### Value-Based Pricing Framework\n\nPrice should be based on value delivered, not cost to serve:\n\n```\n┌─────────────────────────────────────────────────────────┐\n│                                                         │\n│  Customer's perceived value of your solution            │\n│  ────────────────────────────────────────────── $1000   │\n│                                                         │\n│  ↑ Value captured (your opportunity)                    │\n│                                                         │\n│  Your price                                             │\n│  ────────────────────────────────────────────── $500    │\n│                                                         │\n│  ↑ Consumer surplus (value customer keeps)              │\n│                                                         │\n│  Next best alternative                                  │\n│  ────────────────────────────────────────────── $300    │\n│                                                         │\n│  ↑ Differentiation value                                │\n│                                                         │\n│  Your cost to serve                                     │\n│  ────────────────────────────────────────────── $50     │\n│                                                         │\n└─────────────────────────────────────────────────────────┘\n```\n\n**Key insight:** Price between the next best alternative and perceived value. Cost is a floor, not a basis.\n\n---\n\n## Pricing Research Methods\n\n### Van Westendorp Price Sensitivity Meter\n\nThe Van Westendorp survey identifies the acceptable price range for your product.\n\n**The Four Questions:**\n\nAsk each respondent:\n1. \"At what price would you consider [product] to be so expensive that you would not consider buying it?\" (Too expensive)\n2. \"At what price would you consider [product] to be priced so low that you would question its quality?\" (Too cheap)\n3. \"At what price would you consider [product] to be starting to get expensive, but you still might consider it?\" (Expensive\u002Fhigh side)\n4. \"At what price would you consider [product] to be a bargain—a great buy for the money?\" (Cheap\u002Fgood value)\n\n**How to Analyze:**\n\n1. Plot cumulative distributions for each question\n2. Find the intersections:\n   - **Point of Marginal Cheapness (PMC):** \"Too cheap\" crosses \"Expensive\"\n   - **Point of Marginal Expensiveness (PME):** \"Too expensive\" crosses \"Cheap\"\n   - **Optimal Price Point (OPP):** \"Too cheap\" crosses \"Too expensive\"\n   - **Indifference Price Point (IDP):** \"Expensive\" crosses \"Cheap\"\n\n**The acceptable price range:** PMC to PME\n**Optimal pricing zone:** Between OPP and IDP\n\n**Survey Tips:**\n- Need 100-300 respondents for reliable data\n- Segment by persona (different willingness to pay)\n- Use realistic product descriptions\n- Consider adding purchase intent questions\n\n**Sample Van Westendorp Analysis Output:**\n\n```\nPrice Sensitivity Analysis Results:\n─────────────────────────────────\nPoint of Marginal Cheapness:  $29\u002Fmo\nOptimal Price Point:          $49\u002Fmo\nIndifference Price Point:     $59\u002Fmo\nPoint of Marginal Expensiveness: $79\u002Fmo\n\nRecommended range: $49-59\u002Fmo\nCurrent price: $39\u002Fmo (below optimal)\nOpportunity: 25-50% price increase without significant demand impact\n```\n\n### MaxDiff Analysis (Best-Worst Scaling)\n\nMaxDiff identifies which features customers value most, informing packaging decisions.\n\n**How It Works:**\n\n1. List 8-15 features you could include\n2. Show respondents sets of 4-5 features at a time\n3. Ask: \"Which is MOST important? Which is LEAST important?\"\n4. Repeat across multiple sets until all features compared\n5. Statistical analysis produces importance scores\n\n**Example Survey Question:**\n\n```\nWhich feature is MOST important to you?\nWhich feature is LEAST important to you?\n\n□ Unlimited projects\n□ Custom branding\n□ Priority support\n□ API access\n□ Advanced analytics\n```\n\n**Analyzing Results:**\n\nFeatures are ranked by utility score:\n- High utility = Must-have (include in base tier)\n- Medium utility = Differentiator (use for tier separation)\n- Low utility = Nice-to-have (premium tier or cut)\n\n**Using MaxDiff for Packaging:**\n\n| Utility Score | Packaging Decision |\n|---------------|-------------------|\n| Top 20% | Include in all tiers (table stakes) |\n| 20-50% | Use to differentiate tiers |\n| 50-80% | Higher tiers only |\n| Bottom 20% | Consider cutting or premium add-on |\n\n### Willingness to Pay Surveys\n\n**Direct method (simple but biased):**\n\"How much would you pay for [product]?\"\n\n**Better: Gabor-Granger method:**\n\"Would you buy [product] at [$X]?\" (Yes\u002FNo)\nVary price across respondents to build demand curve.\n\n**Even better: Conjoint analysis:**\nShow product bundles at different prices\nRespondents choose preferred option\nStatistical analysis reveals price sensitivity per feature\n\n---\n\n## Value Metrics\n\n### What is a Value Metric?\n\nThe value metric is what you charge for—it should scale with the value customers receive.\n\n**Good value metrics:**\n- Align price with value delivered\n- Are easy to understand\n- Scale as customer grows\n- Are hard to game\n\n### Common Value Metrics\n\n| Metric | Best For | Example |\n|--------|----------|---------|\n| Per user\u002Fseat | Collaboration tools | Slack, Notion |\n| Per usage | Variable consumption | AWS, Twilio |\n| Per feature | Modular products | HubSpot add-ons |\n| Per contact\u002Frecord | CRM, email tools | Mailchimp, HubSpot |\n| Per transaction | Payments, marketplaces | Stripe, Shopify |\n| Flat fee | Simple products | Basecamp |\n| Revenue share | High-value outcomes | Affiliate platforms |\n\n### Choosing Your Value Metric\n\n**Step 1: Identify how customers get value**\n- What outcome do they care about?\n- What do they measure success by?\n- What would they pay more for?\n\n**Step 2: Map usage to value**\n\n| Usage Pattern | Value Delivered | Potential Metric |\n|---------------|-----------------|------------------|\n| More team members use it | More collaboration value | Per user |\n| More data processed | More insights | Per record\u002Fevent |\n| More revenue generated | Direct ROI | Revenue share |\n| More projects managed | More organization | Per project |\n\n**Step 3: Test for alignment**\n\nAsk: \"As a customer uses more of [metric], do they get more value?\"\n- If yes → good value metric\n- If no → price doesn't align with value\n\n### Mapping Usage to Value: Framework\n\n**1. Instrument usage data**\nTrack how customers use your product:\n- Feature usage frequency\n- Volume metrics (users, records, API calls)\n- Outcome metrics (revenue generated, time saved)\n\n**2. Correlate with customer success**\n- Which usage patterns predict retention?\n- Which usage patterns predict expansion?\n- Which customers pay the most, and why?\n\n**3. Identify value thresholds**\n- At what usage level do customers \"get it\"?\n- At what usage level do they expand?\n- At what usage level should price increase?\n\n**Example Analysis:**\n\n```\nUsage-Value Correlation Analysis:\n─────────────────────────────────\nSegment: High-LTV customers (>$10k ARR)\nAverage monthly active users: 15\nAverage projects: 8\nAverage integrations: 4\n\nSegment: Churned customers\nAverage monthly active users: 3\nAverage projects: 2\nAverage integrations: 0\n\nInsight: Value correlates with team adoption (users)\n        and depth of use (integrations)\n\nRecommendation: Price per user, gate integrations to higher tiers\n```\n\n---\n\n## Tier Structure\n\n### How Many Tiers?\n\n**2 tiers:** Simple, clear choice\n- Works for: Clear SMB vs. Enterprise split\n- Risk: May leave money on table\n\n**3 tiers:** Industry standard\n- Good tier = Entry point\n- Better tier = Recommended (anchor to best)\n- Best tier = High-value customers\n\n**4+ tiers:** More granularity\n- Works for: Wide range of customer sizes\n- Risk: Decision paralysis, complexity\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):**\n- Purpose: Remove barriers to entry\n- Includes: Core features, limited usage\n- Price: Low, accessible\n- Target: Small teams, try before you buy\n\n**Better tier (Recommended):**\n- Purpose: Where most customers land\n- Includes: Full features, reasonable limits\n- Price: Your \"anchor\" price\n- Target: Growing teams, serious users\n\n**Best tier (Premium):**\n- Purpose: Capture high-value customers\n- Includes: Everything, advanced features, higher limits\n- Price: Premium (often 2-3x \"Better\")\n- Target: Larger teams, power users, enterprises\n\n### Tier Differentiation Strategies\n\n**Feature gating:**\n- Basic features in all tiers\n- Advanced features in higher tiers\n- Works when features have clear value differences\n\n**Usage limits:**\n- Same features, different limits\n- More users, storage, API calls at higher tiers\n- Works when value scales with usage\n\n**Support level:**\n- Email support → Priority support → Dedicated success\n- Works for products with implementation complexity\n\n**Access and customization:**\n- API access, SSO, custom branding\n- Works for enterprise differentiation\n\n### Example Tier Structure\n\n```\n┌────────────────┬─────────────────┬─────────────────┬─────────────────┐\n│                │ Starter         │ Pro             │ Business        │\n│                │ $29\u002Fmo          │ $79\u002Fmo          │ $199\u002Fmo         │\n├────────────────┼─────────────────┼─────────────────┼─────────────────┤\n│ Users          │ Up to 5         │ Up to 20        │ Unlimited       │\n│ Projects       │ 10              │ Unlimited       │ Unlimited       │\n│ Storage        │ 5 GB            │ 50 GB           │ 500 GB          │\n│ Integrations   │ 3               │ 10              │ Unlimited       │\n│ Analytics      │ Basic           │ Advanced        │ Custom          │\n│ Support        │ Email           │ Priority        │ Dedicated       │\n│ API Access     │ ✗               │ ✓               │ ✓               │\n│ SSO            │ ✗               │ ✗               │ ✓               │\n│ Audit logs     │ ✗               │ ✗               │ ✓               │\n└────────────────┴─────────────────┴─────────────────┴─────────────────┘\n```\n\n---\n\n## Packaging for Personas\n\n### Identifying Pricing Personas\n\nDifferent customers have different:\n- Willingness to pay\n- Feature needs\n- Buying processes\n- Value perception\n\n**Segment by:**\n- Company size (solopreneur → SMB → enterprise)\n- Use case (marketing vs. sales vs. support)\n- Sophistication (beginner → power user)\n- Industry (different budget norms)\n\n### Persona-Based Packaging\n\n**Step 1: Define personas**\n\n| Persona | Size | Needs | WTP | Example |\n|---------|------|-------|-----|---------|\n| Freelancer | 1 person | Basic features | Low | $19\u002Fmo |\n| Small Team | 2-10 | Collaboration | Medium | $49\u002Fmo |\n| Growing Co | 10-50 | Scale, integrations | Higher | $149\u002Fmo |\n| Enterprise | 50+ | Security, support | High | Custom |\n\n**Step 2: Map features to personas**\n\n| Feature | Freelancer | Small Team | Growing | Enterprise |\n|---------|------------|------------|---------|------------|\n| Core features | ✓ | ✓ | ✓ | ✓ |\n| Collaboration | — | ✓ | ✓ | ✓ |\n| Integrations | — | Limited | Full | Full |\n| API access | — | — | ✓ | ✓ |\n| SSO\u002FSAML | — | — | — | ✓ |\n| Audit logs | — | — | — | ✓ |\n| Custom contract | — | — | — | ✓ |\n\n**Step 3: Price to value for each persona**\n- Research willingness to pay per segment\n- Set prices that capture value without blocking adoption\n- Consider segment-specific landing pages\n\n---\n\n## Freemium vs. Free Trial\n\n### When to Use Freemium\n\n**Freemium works when:**\n- Product has viral\u002Fnetwork effects\n- Free users provide value (content, data, referrals)\n- Large market where % conversion drives volume\n- Low marginal cost to serve free users\n- Clear feature\u002Fusage limits for upgrade trigger\n\n**Freemium risks:**\n- Free users may never convert\n- Devalues product perception\n- Support costs for non-paying users\n- Harder to raise prices later\n\n**Example: Slack**\n- Free tier for small teams\n- Message history limit creates upgrade trigger\n- Free users invite others (viral growth)\n- Converts when team hits limit\n\n### When to Use Free Trial\n\n**Free trial works when:**\n- Product needs time to demonstrate value\n- Onboarding\u002Fsetup investment required\n- B2B with buying committees\n- Higher price points\n- Product is \"sticky\" once configured\n\n**Trial best practices:**\n- 7-14 days for simple products\n- 14-30 days for complex products\n- Full access (not feature-limited)\n- Clear countdown and reminders\n- Credit card optional vs. required trade-off\n\n**Credit card upfront:**\n- Higher trial-to-paid conversion (40-50% vs. 15-25%)\n- Lower trial volume\n- Better qualified leads\n\n### Hybrid Approaches\n\n**Freemium + Trial:**\n- Free tier with limited features\n- Trial of premium features\n- Example: Zoom (free 40-min, trial of Pro)\n\n**Reverse trial:**\n- Start with full access\n- After trial, downgrade to free tier\n- Example: See premium value, live with limitations until ready\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- You're significantly cheaper than alternatives\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Very high conversion rates (>40%)\n- Very low churn (\u003C3% monthly)\n- Customers using more than they pay for\n- Unit economics are strong\n\n**Product signals:**\n- You've added significant value since last pricing\n- Product is more mature\u002Fstable\n- New features justify higher price\n\n### Price Increase Strategies\n\n**1. Grandfather existing customers**\n- New price for new customers only\n- Existing customers keep old price\n- Pro: No churn risk\n- Con: Leaves money on table, creates complexity\n\n**2. Delayed increase for existing**\n- Announce increase 3-6 months out\n- Give time to lock in old price (annual)\n- Pro: Fair, drives annual conversions\n- Con: Some churn, requires communication\n\n**3. Increase tied to value**\n- Raise price but add features\n- \"New Pro tier with X, Y, Z\"\n- Pro: Justified increase\n- Con: Requires actual new value\n\n**4. Plan restructure**\n- Change plans entirely\n- Existing customers mapped to nearest fit\n- Pro: Clean slate\n- Con: Disruptive, requires careful mapping\n\n### Communicating Price Increases\n\n**For new customers:**\n- Just update pricing page\n- No announcement needed\n- Monitor conversion rate\n\n**For existing customers:**\n\n```\nSubject: Updates to [Product] pricing\n\nHi [Name],\n\nI'm writing to let you know about upcoming changes to [Product] pricing.\n\n[Context: what you've added, why change is happening]\n\nStarting [date], our pricing will change from [old] to [new].\n\nAs a valued customer, [what this means for them: grandfathered, locked rate, timeline].\n\n[If they're affected:]\nYou have until [date] to [action: lock in current rate, renew at old price].\n\n[If they're grandfathered:]\nYou'll continue at your current rate. No action needed.\n\nWe appreciate your continued support of [Product].\n\n[Your name]\n```\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Tier Presentation\n\n- Lead with the recommended tier (visual emphasis)\n- Show value progression clearly\n- Use checkmarks and limits, not paragraphs\n- Anchor to higher tier (show enterprise first or savings)\n\n### Common Elements\n\n- [ ] Feature comparison table\n- [ ] Who each tier is for\n- [ ] FAQ section\n- [ ] Contact sales option\n- [ ] Annual discount callout\n- [ ] Money-back guarantee\n- [ ] Customer logos\u002Ftrust signals\n\n### Pricing Psychology to Apply\n\n- **Anchoring:** Show higher-priced option first\n- **Decoy effect:** Middle tier should be obviously best value\n- **Charm pricing:** $49 vs. $50 (for value-focused)\n- **Round pricing:** $50 vs. $49 (for premium)\n- **Annual savings:** Show monthly price but offer annual discount (17-20%)\n\n---\n\n## Price Testing\n\n### Methods for Testing Price\n\n**1. A\u002FB test pricing page (risky)**\n- Different visitors see different prices\n- Ethical\u002Flegal concerns\n- May damage trust if discovered\n\n**2. Geographic testing**\n- Test higher prices in new markets\n- Different currencies\u002Fregions\n- Cleaner test, limited reach\n\n**3. New customer only**\n- Raise prices for new customers\n- Compare conversion rates\n- Monitor cohort LTV\n\n**4. Sales team discretion**\n- Test higher quotes through sales\n- Track close rates at different prices\n- Works for sales-led GTM\n\n**5. Feature-based testing**\n- Test different packaging\n- Add premium tier at higher price\n- See adoption without changing existing\n\n### What to Measure\n\n- Conversion rate at each price point\n- Average revenue per user (ARPU)\n- Total revenue (conversion × price)\n- Customer lifetime value\n- Churn rate by price paid\n- Price sensitivity by segment\n\n---\n\n## Enterprise Pricing\n\n### When to Add Custom Pricing\n\nAdd \"Contact Sales\" when:\n- Deal sizes exceed $10k+ ARR\n- Customers need custom contracts\n- Implementation\u002Fonboarding required\n- Security\u002Fcompliance requirements\n- Procurement processes involved\n\n### Enterprise Tier Elements\n\n**Table stakes:**\n- SSO\u002FSAML\n- Audit logs\n- Admin controls\n- Uptime SLA\n- Security certifications\n\n**Value-adds:**\n- Dedicated support\u002Fsuccess\n- Custom onboarding\n- Training sessions\n- Custom integrations\n- Priority roadmap input\n\n### Enterprise Pricing Strategies\n\n**Per-seat at scale:**\n- Volume discounts for large teams\n- Example: $15\u002Fuser (standard) → $10\u002Fuser (100+)\n\n**Platform fee + usage:**\n- Base fee for access\n- Usage-based above thresholds\n- Example: $500\u002Fmo base + $0.01 per API call\n\n**Value-based contracts:**\n- Price tied to customer's revenue\u002Foutcomes\n- Example: % of transactions, revenue share\n\n---\n\n## Pricing Checklist\n\n### Before Setting Prices\n\n- [ ] Defined target customer personas\n- [ ] Researched competitor pricing\n- [ ] Identified your value metric\n- [ ] Conducted willingness-to-pay research\n- [ ] Mapped features to tiers\n\n### Pricing Structure\n\n- [ ] Chosen number of tiers\n- [ ] Differentiated tiers clearly\n- [ ] Set price points based on research\n- [ ] Created annual discount strategy\n- [ ] Planned enterprise\u002Fcustom tier\n\n### Validation\n\n- [ ] Tested pricing with target customers\n- [ ] Reviewed pricing with sales team\n- [ ] Validated unit economics work\n- [ ] Planned for price increases\n- [ ] Set up tracking for pricing metrics\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What pricing research have you done (surveys, competitor analysis)?\n2. What's your current ARPU and conversion rate?\n3. What's your primary value metric (what do customers pay for value)?\n4. Who are your main pricing personas (by size, use case)?\n5. Are you self-serve, sales-led, or hybrid?\n6. What pricing changes are you considering?\n\n---\n\n## Related Skills\n\n- **page-cro**: For optimizing pricing page conversion\n- **copywriting**: For pricing page copy\n- **marketing-psychology**: For pricing psychology principles\n- **ab-test-setup**: For testing pricing changes\n- **analytics-tracking**: For tracking pricing metrics\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fpricing-strategy",3911,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-11 21:38:31",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add davila7\u002Fclaude-code-templates --skill pricing-strategy",{"tool":67,"command":68},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill pricing-strategy",{"tool":70,"command":71},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill pricing-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fpricing-strategy\u002FSKILL.md",true,[],[76,101,128,161,196,220],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":83,"publishedAt":46},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[82],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[84,85,86,87,88,89,90,91,41,30,92,35,93,94,95,96,97,98,99,100],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":46},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[107],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,114,115,116,117,118,119,30,120,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":143,"publishedAt":46},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[134,137,138],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,89,151,152,153,154,155,156,157,41,158,159,30,160],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":46},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,89,195],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":46},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[208,209,210,211,212,174,213,183,184,214,215,216,217,89,218,35,219],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":46},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[227,230,231],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":232,"categoryName":233,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,45,238,239,240,241,176,242,186,120,243,244,245,246,247,156,248,30,249,250,251,252,253,98,254],"discernment nudge","nudge","interpretation","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]