[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9BM9B05GCGSMD7SWWD6PC":3,"skill-same:01M6M9BM9B05GCGSMD7SWWD6PC":107},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6M9BM9B05GCGSMD7SWWD6PC","suede-pricing",null,"Suede AI Pricing Skills: value metric selection, tiers, willingness-to-pay research, AI unit economics, migration, and pricing-page clarity. Use when asked \"restructure our pricing tiers\" or to decide prices, raise them, or diagnose buyer confusion. NOT FOR: in-product prompts (suede-paywalls), offer bonuses and guarantees (suede-offers), or executing billing changes.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1554,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"suede pricing","pricing","unit","when","value","metric","for","prices","pay","billing","ai pricing","economics","paywalls","selection","unit economics","use","decide","page","clarity","product","diagnose","2026-11-10 10:12:30",false,"---\nname: suede-pricing\ndescription: \"Suede AI Pricing Skills: value metric selection, tiers, willingness-to-pay research, AI unit economics, migration, and pricing-page clarity. Use when asked \\\"restructure our pricing tiers\\\" or to decide prices, raise them, or diagnose buyer confusion. NOT FOR: in-product prompts (suede-paywalls), offer bonuses and guarantees (suede-offers), or executing billing changes.\"\nmetadata:\n  display-name: \"Suede AI Pricing Skills\"\n  version: 2.1.0\n---\n\n# Suede AI Pricing Skills\n\n## Compatibility\n\nWorks with supplied product economics, customer evidence, and current pricing. Competitor and regulatory facts require current sources. Produces a decision brief or teardown; billing writes require separate authorization.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nSuede AI Pricing turns verified product economics, buyer evidence, and commercial\nconstraints into testable prices, value metrics, tiers, and migration plans.\nIt produces a decision brief and measurement plan while keeping billing changes\nbehind explicit approval.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\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\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your ARPU and churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Optimizing for growth, revenue, or profitability?\n- Moving upmarket or expanding downmarket?\n\n---\n\n## Pricing Fundamentals\n\nThree axes, decided in this order: **packaging** (what's included per tier),\n**pricing metric** (what you charge for), **price point** (how much).\n\nPrice sits between the next best alternative (the floor) and the customer's\nperceived value (the ceiling). Cost to serve is a baseline, never the basis.\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 |\n| Per transaction | Payments, marketplaces | Stripe |\n| Flat fee | Simple products | Basecamp |\n\n### Choosing Your Value Metric\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### Pricing AI features\n\nWhen a feature's cost to serve scales with model usage, flat per-seat pricing can turn heavy users unprofitable. Common structures:\n- **Hybrid:** a seat or platform fee with included usage, plus credits or overage beyond it.\n- **Credits:** one currency across AI actions, priced so the most expensive action still clears margin. Publish what a credit buys in plain words.\n- **Outcome-based:** charge per resolved ticket, qualified lead, or completed task, when the outcome is countable and attributable.\n\nFor each, model margin at the 90th-percentile user, state included limits on the pricing page, and give buyers a usage view before the bill surprises them.\n\n### Defaults to Beat\n\nThese are the answers a model reaches for unprompted. Each is allowed, but only\nonce you state why it beats the alternative for this product: never by default:\n**$9\u002F$29\u002F$99** (or any flat 3x ladder); **Starter\u002FPro\u002FEnterprise** names that\ncarry no product meaning; **exactly three tiers** when the buyer set is two or\nfour; **20% off annual** as the reflex discount; **\"Contact us\"** on the top\ntier, which hides price from buyers and from the agents that now shortlist tools\n(see Pricing Page Teardown); **per-seat** when usage, records, or transactions\ntrack value better.\n\n---\n\n## Tier Structure Overview\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):** Core features, limited usage, low price\n**Better tier (Recommended):** Full features, reasonable limits, anchor price\n**Best tier (Premium):** Everything, advanced features, 2-3x Better price\n\n### Tier Differentiation\n\n- **Feature gating**: Basic vs. advanced features\n- **Usage limits**: Same features, different limits\n- **Support level**: Email → Priority → Dedicated\n- **Access**: API, SSO, custom branding\n\n**For detailed tier structures and persona-based packaging**: See [references\u002Ftier-structure.md](references\u002Ftier-structure.md)\n\n---\n\n## Pricing Research\n\n### Van Westendorp Method\n\nFour questions that identify acceptable price range:\n1. Too expensive (wouldn't consider)\n2. Too cheap (question quality)\n3. Expensive but might consider\n4. A bargain\n\nAnalyze intersections to find optimal pricing zone.\n\n### MaxDiff Analysis\n\nIdentifies which features customers value most:\n- Show sets of features\n- Ask: Most important? Least important?\n- Results inform tier packaging\n\n**For detailed research methods**: See [references\u002Fresearch-methods.md](references\u002Fresearch-methods.md)\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Conversion well above your own trailing baseline with no price objections in sales notes\n- Churn low and stable, with price rarely named as a cancel reason\n- Strong unit economics (payback and gross margin, from your own data)\n\n**Product signals:**\n- Significant value added since last pricing\n- Product more mature\u002Fstable\n\n### Price Increase Strategies\n\n1. **Grandfather existing**: New price for new customers only\n2. **Delayed increase**: Announce 3-6 months out\n3. **Tied to value**: Raise price but add features\n4. **Plan restructure**: Change plans entirely\n\n**Legal notice floor for existing subscribers:** an increase on an auto-renewing plan needs clear advance notice with cancellation instructions. California's amended Automatic Renewal Law (in force July 1, 2025) requires that notice 7 to 30 days before the new price applies; contracts and other jurisdictions may require more. Current rules live in `suede-paywalls`.\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Common Elements\n- An on-page FAQ that answers cost, limits, trials, and cancellation in plain text (buyers and AI assistants both read it)\n- The annual saving stated in dollars and percent, whatever discount you chose\n- A guarantee or trial terms near the CTA\n- Renewal terms beside any auto-renewing plan: price, billing interval, and how to cancel\n\n### Price transparency rules\n- Show the total mandatory price. In the UK, the DMCC Act has banned drip pricing of mandatory fees since April 6, 2025 ([CMA207 guidance](https:\u002F\u002Fwww.gov.uk\u002Fgovernment\u002Fpublications\u002Funfair-commercial-practices-cma207)).\n- Auto-renewing plans need clear disclosure and consent before billing under US ROSCA and state auto-renewal laws; `suede-paywalls` holds the current US, UK, and EU subscription rules.\n\n### Pricing Psychology\nTreat each as a test, using the evidence tiers in the `suede-offers` behavioral-models catalog:\n- **Anchoring (Robust):** show the higher-priced option or the cost of the alternative first, honestly.\n- **Good-better-best relativity (Context-dependent):** design the middle tier as the target and check real tier-selection data.\n- **Decoy tier (Contested):** a third tier can clarify the comparison; do not count on it to move choice.\n- **Charm vs. round endings (Context-dependent):** weak for B2B subscriptions; test rather than assume.\n\n---\n\n## Pricing Page Teardown\n\nWhen someone wants to audit an existing pricing *page* for **clarity, transparency, and AI-readability** (not the pricing strategy itself, and not conversion-rate optimization, that's `suede-site-alchemy`), run a **teardown** that scores it across two axes and returns prioritized fixes:\n\n- **Human buyer experience**: value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.\n- **AI-agent readiness**, whether the LLMs and agents that increasingly shortlist and compare tools can actually read and quote your pricing: machine-readable prices (not locked in an image or behind \"Contact us\"), extractable FAQ\u002Fobjection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT\u002FPerplexity\u002FClaude \"what's the best X and what does it cost?\" *before* visiting, a pricing page an agent can't parse loses deals you never see.\n\n**Fast check, the \"paste test\":** give the pricing URL to a browsing-capable AI (Perplexity, ChatGPT with search, Claude with web), or paste the rendered page text, and ask \"what are the plans and prices?\" A clean miss means agents fetching your page will struggle too (a heuristic, not proof every agent fails).\n\nThe AI-readiness fixes are usually high-impact, low-effort (put prices in text, add JSON-LD that matches them). Hand implementation to **suede-seo-audit** (structured data and supported-schema checks), **suede-ai-seo** (extractability and AI-bot access), and **suede-competitors** for \"vs\" and alternatives pages that cite the same prices.\n\n**For the full 10-dimension rubric, scoring, structured-data facts, and report template:** See [references\u002Fpricing-page-teardown.md](references\u002Fpricing-page-teardown.md).\n\n---\n\n## Output: Pricing Decision Brief\n\nEvery pricing or packaging engagement that is not a teardown returns this exact\nstructure. Use these headings verbatim; leave a heading in with \"not decided,\n[what's missing]\" rather than dropping it.\n\n```markdown\n# Pricing Decision Brief: [product]\n\n## Value metric\n[What you charge for, and the one sentence proving usage of it tracks value.]\n\n## Tier map\n| Tier | Who it's for | Included | Limits | Price |\n|------|--------------|----------|--------|-------|\n\n## Price points + rationale\n[Each number, and what it is anchored to: alternative, perceived value, or research.]\n\n## Assumptions\n[Every number taken on faith, flagged as assumption not measurement.]\n\n## Validation plan\n[What test or research confirms each assumption, and the metric that reads out.]\n\n## Migration + grandfathering\n[Existing customers: who moves, when, on what notice, and who is held.]\n\n## What I did NOT decide\n[Anything left to the user: committed price, published copy, billing changes.]\n```\n\n---\n\n## Boundaries\n\n- Do not create or change billing products, prices, subscriptions, or customer\n  migrations without verified live state, a maximum-cost check, and explicit\n  approval.\n- Do not present willingness-to-pay, conversion, churn, or revenue impact as\n  measured unless current research or product data supports it.\n- Do not publish pricing copy, choose grandfathering policy, or commit the\n  business to a price; return a recommendation, assumptions, and validation\n  plan for the user to decide.\n\n## Routing\n\n- Use `suede-paywalls` for in-product upgrade and paywall experiences.\n- Use `suede-offers` for bonuses, guarantees, and offer framing.\n- Use `suede-ab-testing` to validate pricing-page or packaging hypotheses.\n- Use `suede-revops` for approved deal-desk and pipeline implementation.\n","# Suede AI Pricing Skills\n\n## Compatibility\n\nWorks with supplied product economics, customer evidence, and current pricing. Competitor and regulatory facts require current sources. Produces a decision brief or teardown; billing writes require separate authorization.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nSuede AI Pricing turns verified product economics, buyer evidence, and commercial\nconstraints into testable prices, value metrics, tiers, and migration plans.\nIt produces a decision brief and measurement plan while keeping billing changes\nbehind explicit approval.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\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\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your ARPU and churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Optimizing for growth, revenue, or profitability?\n- Moving upmarket or expanding downmarket?\n\n---\n\n## Pricing Fundamentals\n\nThree axes, decided in this order: **packaging** (what's included per tier),\n**pricing metric** (what you charge for), **price point** (how much).\n\nPrice sits between the next best alternative (the floor) and the customer's\nperceived value (the ceiling). Cost to serve is a baseline, never the basis.\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 |\n| Per transaction | Payments, marketplaces | Stripe |\n| Flat fee | Simple products | Basecamp |\n\n### Choosing Your Value Metric\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### Pricing AI features\n\nWhen a feature's cost to serve scales with model usage, flat per-seat pricing can turn heavy users unprofitable. Common structures:\n- **Hybrid:** a seat or platform fee with included usage, plus credits or overage beyond it.\n- **Credits:** one currency across AI actions, priced so the most expensive action still clears margin. Publish what a credit buys in plain words.\n- **Outcome-based:** charge per resolved ticket, qualified lead, or completed task, when the outcome is countable and attributable.\n\nFor each, model margin at the 90th-percentile user, state included limits on the pricing page, and give buyers a usage view before the bill surprises them.\n\n### Defaults to Beat\n\nThese are the answers a model reaches for unprompted. Each is allowed, but only\nonce you state why it beats the alternative for this product: never by default:\n**$9\u002F$29\u002F$99** (or any flat 3x ladder); **Starter\u002FPro\u002FEnterprise** names that\ncarry no product meaning; **exactly three tiers** when the buyer set is two or\nfour; **20% off annual** as the reflex discount; **\"Contact us\"** on the top\ntier, which hides price from buyers and from the agents that now shortlist tools\n(see Pricing Page Teardown); **per-seat** when usage, records, or transactions\ntrack value better.\n\n---\n\n## Tier Structure Overview\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):** Core features, limited usage, low price\n**Better tier (Recommended):** Full features, reasonable limits, anchor price\n**Best tier (Premium):** Everything, advanced features, 2-3x Better price\n\n### Tier Differentiation\n\n- **Feature gating**: Basic vs. advanced features\n- **Usage limits**: Same features, different limits\n- **Support level**: Email → Priority → Dedicated\n- **Access**: API, SSO, custom branding\n\n**For detailed tier structures and persona-based packaging**: See [references\u002Ftier-structure.md](references\u002Ftier-structure.md)\n\n---\n\n## Pricing Research\n\n### Van Westendorp Method\n\nFour questions that identify acceptable price range:\n1. Too expensive (wouldn't consider)\n2. Too cheap (question quality)\n3. Expensive but might consider\n4. A bargain\n\nAnalyze intersections to find optimal pricing zone.\n\n### MaxDiff Analysis\n\nIdentifies which features customers value most:\n- Show sets of features\n- Ask: Most important? Least important?\n- Results inform tier packaging\n\n**For detailed research methods**: See [references\u002Fresearch-methods.md](references\u002Fresearch-methods.md)\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Conversion well above your own trailing baseline with no price objections in sales notes\n- Churn low and stable, with price rarely named as a cancel reason\n- Strong unit economics (payback and gross margin, from your own data)\n\n**Product signals:**\n- Significant value added since last pricing\n- Product more mature\u002Fstable\n\n### Price Increase Strategies\n\n1. **Grandfather existing**: New price for new customers only\n2. **Delayed increase**: Announce 3-6 months out\n3. **Tied to value**: Raise price but add features\n4. **Plan restructure**: Change plans entirely\n\n**Legal notice floor for existing subscribers:** an increase on an auto-renewing plan needs clear advance notice with cancellation instructions. California's amended Automatic Renewal Law (in force July 1, 2025) requires that notice 7 to 30 days before the new price applies; contracts and other jurisdictions may require more. Current rules live in `suede-paywalls`.\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Common Elements\n- An on-page FAQ that answers cost, limits, trials, and cancellation in plain text (buyers and AI assistants both read it)\n- The annual saving stated in dollars and percent, whatever discount you chose\n- A guarantee or trial terms near the CTA\n- Renewal terms beside any auto-renewing plan: price, billing interval, and how to cancel\n\n### Price transparency rules\n- Show the total mandatory price. In the UK, the DMCC Act has banned drip pricing of mandatory fees since April 6, 2025 ([CMA207 guidance](https:\u002F\u002Fwww.gov.uk\u002Fgovernment\u002Fpublications\u002Funfair-commercial-practices-cma207)).\n- Auto-renewing plans need clear disclosure and consent before billing under US ROSCA and state auto-renewal laws; `suede-paywalls` holds the current US, UK, and EU subscription rules.\n\n### Pricing Psychology\nTreat each as a test, using the evidence tiers in the `suede-offers` behavioral-models catalog:\n- **Anchoring (Robust):** show the higher-priced option or the cost of the alternative first, honestly.\n- **Good-better-best relativity (Context-dependent):** design the middle tier as the target and check real tier-selection data.\n- **Decoy tier (Contested):** a third tier can clarify the comparison; do not count on it to move choice.\n- **Charm vs. round endings (Context-dependent):** weak for B2B subscriptions; test rather than assume.\n\n---\n\n## Pricing Page Teardown\n\nWhen someone wants to audit an existing pricing *page* for **clarity, transparency, and AI-readability** (not the pricing strategy itself, and not conversion-rate optimization, that's `suede-site-alchemy`), run a **teardown** that scores it across two axes and returns prioritized fixes:\n\n- **Human buyer experience**: value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.\n- **AI-agent readiness**, whether the LLMs and agents that increasingly shortlist and compare tools can actually read and quote your pricing: machine-readable prices (not locked in an image or behind \"Contact us\"), extractable FAQ\u002Fobjection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT\u002FPerplexity\u002FClaude \"what's the best X and what does it cost?\" *before* visiting, a pricing page an agent can't parse loses deals you never see.\n\n**Fast check, the \"paste test\":** give the pricing URL to a browsing-capable AI (Perplexity, ChatGPT with search, Claude with web), or paste the rendered page text, and ask \"what are the plans and prices?\" A clean miss means agents fetching your page will struggle too (a heuristic, not proof every agent fails).\n\nThe AI-readiness fixes are usually high-impact, low-effort (put prices in text, add JSON-LD that matches them). Hand implementation to **suede-seo-audit** (structured data and supported-schema checks), **suede-ai-seo** (extractability and AI-bot access), and **suede-competitors** for \"vs\" and alternatives pages that cite the same prices.\n\n**For the full 10-dimension rubric, scoring, structured-data facts, and report template:** See [references\u002Fpricing-page-teardown.md](references\u002Fpricing-page-teardown.md).\n\n---\n\n## Output: Pricing Decision Brief\n\nEvery pricing or packaging engagement that is not a teardown returns this exact\nstructure. Use these headings verbatim; leave a heading in with \"not decided,\n[what's missing]\" rather than dropping it.\n\n```markdown\n# Pricing Decision Brief: [product]\n\n## Value metric\n[What you charge for, and the one sentence proving usage of it tracks value.]\n\n## Tier map\n| Tier | Who it's for | Included | Limits | Price |\n|------|--------------|----------|--------|-------|\n\n## Price points + rationale\n[Each number, and what it is anchored to: alternative, perceived value, or research.]\n\n## Assumptions\n[Every number taken on faith, flagged as assumption not measurement.]\n\n## Validation plan\n[What test or research confirms each assumption, and the metric that reads out.]\n\n## Migration + grandfathering\n[Existing customers: who moves, when, on what notice, and who is held.]\n\n## What I did NOT decide\n[Anything left to the user: committed price, published copy, billing changes.]\n```\n\n---\n\n## Boundaries\n\n- Do not create or change billing products, prices, subscriptions, or customer\n  migrations without verified live state, a maximum-cost check, and explicit\n  approval.\n- Do not present willingness-to-pay, conversion, churn, or revenue impact as\n  measured unless current research or product data supports it.\n- Do not publish pricing copy, choose grandfathering policy, or commit the\n  business to a price; return a recommendation, assumptions, and validation\n  plan for the user to decide.\n\n## Routing\n\n- Use `suede-paywalls` for in-product upgrade and paywall experiences.\n- Use `suede-offers` for bonuses, guarantees, and offer framing.\n- Use `suede-ab-testing` to validate pricing-page or packaging hypotheses.\n- Use `suede-revops` for approved deal-desk and pipeline implementation.\n",{"name":5,"metadata":50,"description":7},{"version":51,"display-name":52},"2.1.0","Suede AI Pricing Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing",468,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 02:22:54",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-pricing",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-pricing",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-pricing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002FSKILL.md",true,[77,83,87,91,95,99,103],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"agents\u002Fopenai.yaml","REFERENCE","参考文档",624,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Fagents\u002Fopenai.yaml",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"CARD.md",4401,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002FCARD.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fevals.json",6893,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Fevals\u002Fevals.json",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpricing-page-teardown.md",8405,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Freferences\u002Fpricing-page-teardown.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fresearch-methods.md",4812,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Freferences\u002Fresearch-methods.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Ftier-structure.md",7410,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Freferences\u002Ftier-structure.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fworked-contract.md",2123,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-pricing\u002Freferences\u002Fworked-contract.md",[108,133,158,190,209,223],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":45},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[115,116,117,118,119,120,121,40,122,123,124,27,125,126,127,128,129,130,131,132],"search","deja search","error","ready","never","memory","re","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":45},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[140,141,142,143,120,144,145,146,147,148,149,150,151,128,152,153,154,155,156,157],"reflect","deja reflect","brew","remember","project rules","project","session","end","reflection","Rules","decisions","review","with","record","github","next","https","node",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":173,"publishedAt":45},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[164,167,170],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,174,175,176,177,178,145,179,121,180,181,182,183,27,184,185,186,187,188,189],"Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","URL","image","mcp server","schedule","api","publish",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":45},"01M71569ZM2X3H5RBFK8PVKMK2","review-study","Review a QuestionPunk survey before launch for wording, answer choices, branching, and missing settings. Use for check my survey or review this draft before publishing.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Freview-study\u002FSKILL.md",[],[197,198,151,30,199,200,201,202,39,203,204,205,206,207,208],"study","review study","answer","missing","survey","publishing","check","draft","settings","launch","my","branching",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":45},"01M71567GV0C35YQBY0DPGR86B","manage-study","Find QuestionPunk studies, check status, publish an explicitly requested draft, or retrieve its participant link. Use for find my survey, publish this study, or how many people responded.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fmanage-study\u002FSKILL.md",[],[216,197,217,30,201,39,218,203,204,189,219,220,221,222,207],"manage study","manage","people","how","find","link","status",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":45},"01M71565A8TCA01AZQZRGRYMFZ","create-study","Create a saved QuestionPunk survey draft from a research brief or edit specified questions. Use for requests such as make a customer feedback survey or shorten my onboarding study.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fcreate-study\u002FSKILL.md",[],[230,197,231,232,233,234,30,235,201,236,39,237,238,204,239,240,241,242,243,207],"create study","create","brief","as","feedback","customer feedback","research brief","shorten","saved","research","requests","customer","questions","edit"]