[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754VAFM65AC8GEMP159P5DA":3,"skill-same:01M754VAFM65AC8GEMP159P5DA":94},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M754VAFM65AC8GEMP159P5DA","pricing-strategist",null,"Use when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp Price Sensitivity Meter analysis on WTP survey data, or designing Good\u002FBetter\u002FBest packaging tiers. Recommends a model and a price range with trade-offs, never a single number. For Commercial leads, Product Marketing, and CMOs at the pricing-design moment — not deal-by-deal discounting, not brand positioning.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pricing-strategist\ndescription: \"Use when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp Price Sensitivity Meter analysis on WTP survey data, or designing Good\u002FBetter\u002FBest packaging tiers. Recommends a model and a price range with trade-offs, never a single number. For Commercial leads, Product Marketing, and CMOs at the pricing-design moment — not deal-by-deal discounting, not brand positioning.\"\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [commercial, pricing, packaging, wtp, van-westendorp, value-based-pricing, saas-pricing]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# pricing-strategist\n\n## Purpose\n\nHelp Commercial, Product Marketing, and CMO functions answer three questions at the pricing-design moment:\n\n1. **Which pricing model fits this product + customer + market?** (subscription seat-based, usage-based, value-based, freemium, hybrid)\n2. **What does the customer actually pay before it feels too expensive?** (Van Westendorp PSM on WTP survey responses)\n3. **How should we package this into tiers?** (Good \u002F Better \u002F Best — with anti-pattern detection)\n\nThe skill recommends **a model and a range**. The human picks the number, owns the trade-offs, and runs the GTM.\n\n## When to use\n\n- Launching a new SaaS \u002F API \u002F AI tool and choosing the first pricing model\n- Revisiting pricing after 18+ months of GTM data (model shift, not just price increase)\n- Designing or redesigning tier packaging (Good\u002FBetter\u002FBest, Bronze\u002FSilver\u002FGold)\n- You have Van Westendorp survey data and want the optimal price range\n- A board \u002F exec is asking \"what should we charge?\" and you need the structured answer\n- You suspect your packaging has anti-patterns (decoy tier, feature dump, no upgrade trigger)\n\n**Do not use for:**\n- Per-deal discount approval → `deal-desk`\n- Strategic CMO positioning, brand, category creation → `c-level-advisor\u002Fcmo-advisor`\n- Whole-company revenue strategy → `c-level-advisor\u002Fcro-advisor`\n- Technical-sale enablement → `business-growth\u002Fsales-engineer`\n\n## Workflow\n\n### Step 1 — Assess customer context\n\nFill `assets\u002Fpricing_brief_template.md` (≈ 20 min). Capture: industry, deal size avg, customer count, value drivers, adoption curve, consumption pattern (seat \u002F usage \u002F value \u002F hybrid), competitor models.\n\n### Step 2 — Pick the pricing model\n\nRun `scripts\u002Fpricing_model_picker.py --input brief.json --profile saas --output markdown`. Output ranks 5 models by fit-score 0-100 with trade-offs. Decision logic is deterministic: low usage variance + high seat-attach → subscription wins; power-law usage + variable customer value → usage-based wins.\n\n### Step 3 — Validate WTP with Van Westendorp PSM\n\nIf you have survey data (≥ 4 questions per respondent: too cheap \u002F bargain \u002F getting expensive \u002F too expensive), run `scripts\u002Fwtp_analyzer.py --input survey.json --output markdown`. Output: 4 intersection points (OPP, IDP, PMC, PME) and the Range of Acceptable Prices.\n\nPSM gives a **range**, not the price. See `references\u002Fvan_westendorp_methodology.md` for common misinterpretations.\n\n### Step 4 — Design packaging\n\nRun `scripts\u002Fpackaging_designer.py --input features.json --profile saas --output markdown`. Output: 3-tier Good\u002FBetter\u002FBest assignment with anti-pattern flags (decoy tier, feature dump, no upgrade trigger, Bronze loss leader, Enterprise no-anchor).\n\n### Step 5 — Decide\n\nTake model + range + packaging into the pricing committee. Skill does not commit the number — you do.\n\n## Scripts\n\n- `scripts\u002Fpricing_model_picker.py` — 5-model fit scorer (subscription \u002F usage \u002F value \u002F freemium \u002F hybrid)\n- `scripts\u002Fwtp_analyzer.py` — Van Westendorp PSM implementation\n- `scripts\u002Fpackaging_designer.py` — Good\u002FBetter\u002FBest tier designer with anti-pattern detection\n\nAll scripts: stdlib only. `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fsaas_pricing_canon.md` — Skok, Tunguz, Campbell, Ramanujam, BVP, Shevlin, Stanford GSB\n- `references\u002Fvan_westendorp_methodology.md` — original 1976 paper, NMS refinement, Conjoint.ly, Sawtooth, ESOMAR, Lipovetsky, Decision Analyst\n- `references\u002Fpackaging_anti_patterns.md` — ProfitWell, OpenView, BVP vertical SaaS, Ramanujam, Poyar, SaaS Capital\n\n## Assumptions\n\n- Pricing decisions are joint: Commercial owns the model + tier shape, Product owns the features-per-tier, Finance owns the discount envelope, Legal owns the contract.\n- Van Westendorp PSM is a **directional** tool. N ≥ 30 minimum, N ≥ 100 preferred. Below 30, the script emits a sample-size warning.\n- \"Value-based pricing\" requires a measurable customer value driver (revenue lift, cost saved, time recovered). If you can't measure it, don't pick value-based.\n- Industry profiles tune defaults — they don't override your data.\n- This is a decision-support skill, not a price oracle. Output is a model + range, never the number.\n\n## Anti-patterns\n\n- **Recommending a specific number.** This skill emits a model and a range. Final price is a human commercial decision involving deal-desk policy, competitive intel, and strategic intent that this skill cannot know.\n- **Using PSM with N \u003C 30.** Statistical noise dominates. The script warns; respect the warning.\n- **Treating PSM as \"the price.\"** PSM gives a Range of Acceptable Prices (RAP) and an Optimal Price Point (OPP). Test the range in market, don't anchor on a single intersection.\n- **Picking value-based pricing without a measurable value metric.** Without instrumentation to show customer ROI, value-based collapses into \"whatever they'll pay\" — which is just bad usage-based pricing.\n- **Designing tiers before picking a model.** Tier structure depends on the model. Run pricing_model_picker first.\n- **Packaging \"feature dumps\" into the Best tier.** If Best has 3x the features for 2x the price, customers buy Better and never upgrade. See `packaging_anti_patterns.md`.\n- **Hidden usage-based pricing inside subscription tiers.** \"Up to 100k API calls\u002Fmo, then $X per 1k\" disguised as a \"Pro tier\" is two pricing models in one. Customers notice. Pick one.\n- **Confusing this skill with deal-desk.** Pricing strategy = the menu. Deal-desk = approving discounts off the menu. Different decision, different cadence, different owner.\n\n## Distinct from\n\n- **deal-desk** — per-deal discount approval, MEDDIC, deal scoring. Operates daily on existing pricing.\n- **c-level-advisor\u002Fcmo-advisor** — strategic positioning, brand, category. Pricing strategist consumes positioning as input, doesn't generate it.\n- **c-level-advisor\u002Fcro-advisor** — full-funnel revenue strategy, comp plans, territory design. Pricing strategist is one input to CRO.\n- **business-growth\u002Fsales-engineer** — technical sale, POC scoping. Sales engineering operates after pricing is set.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-commercial` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is your customer paying for outcomes, seats, or usage?\"**\n   Recommended: outcomes (value-based) if you can measure them; usage if marginal cost is variable; seats only if usage is roughly flat per user.\n   Canon: Ramanujam 2016 (*Monetizing Innovation*) — Mistake #1 of 9: seat-based pricing on a usage-variable product caps TAM at ~20% of WTP.\n\n2. **\"Do you have a measurable value metric, or are you guessing?\"**\n   Recommended: instrument the value metric BEFORE going to market with value-based pricing.\n   Canon: Patrick Campbell \u002F ProfitWell research — value-based without instrumentation collapses into bad usage-based pricing.\n\n3. **\"What's the variance in customer usage across your top decile vs. median?\"**\n   Recommended: variance > 10x → usage-based wins; variance \u003C 3x → subscription wins; in between → hybrid with usage overage.\n   Canon: Kyle Poyar (*Growth Unhinged*) — high-variance products lose 60%+ of revenue on flat-rate plans.\n\n4. **\"What's your competitor's pricing model, and why are you choosing the same or different?\"**\n   Recommended: surface the differentiation hypothesis explicitly. Identical pricing = identical value claim.\n   Canon: David Skok (*For Entrepreneurs*) — pricing is a positioning signal.\n\n5. **\"What sample size do you have for WTP analysis, and is it segmented?\"**\n   Recommended: N≥30 per segment for PSM, N≥100 for conjoint.\n   Canon: van Westendorp 1976 \u002F Sawtooth Software methodology — sub-30 PSM is statistical noise.\n\n6. **\"What's the ONE feature that forces a tier upgrade?\"**\n   Recommended: every Better and Best tier needs a single non-negotiable upgrade trigger.\n   Canon: Ramanujam (*Monetizing Innovation*) — Mistake #4: tiers with no clear differentiator make 70% of customers pick the cheapest.\n\nWalk depth-first. Lock 1-3 before opening 4-6. After all 6 are answered, invoke `pricing_model_picker.py` → `wtp_analyzer.py` → `packaging_designer.py` in sequence.\n","# pricing-strategist\n\n## Purpose\n\nHelp Commercial, Product Marketing, and CMO functions answer three questions at the pricing-design moment:\n\n1. **Which pricing model fits this product + customer + market?** (subscription seat-based, usage-based, value-based, freemium, hybrid)\n2. **What does the customer actually pay before it feels too expensive?** (Van Westendorp PSM on WTP survey responses)\n3. **How should we package this into tiers?** (Good \u002F Better \u002F Best — with anti-pattern detection)\n\nThe skill recommends **a model and a range**. The human picks the number, owns the trade-offs, and runs the GTM.\n\n## When to use\n\n- Launching a new SaaS \u002F API \u002F AI tool and choosing the first pricing model\n- Revisiting pricing after 18+ months of GTM data (model shift, not just price increase)\n- Designing or redesigning tier packaging (Good\u002FBetter\u002FBest, Bronze\u002FSilver\u002FGold)\n- You have Van Westendorp survey data and want the optimal price range\n- A board \u002F exec is asking \"what should we charge?\" and you need the structured answer\n- You suspect your packaging has anti-patterns (decoy tier, feature dump, no upgrade trigger)\n\n**Do not use for:**\n- Per-deal discount approval → `deal-desk`\n- Strategic CMO positioning, brand, category creation → `c-level-advisor\u002Fcmo-advisor`\n- Whole-company revenue strategy → `c-level-advisor\u002Fcro-advisor`\n- Technical-sale enablement → `business-growth\u002Fsales-engineer`\n\n## Workflow\n\n### Step 1 — Assess customer context\n\nFill `assets\u002Fpricing_brief_template.md` (≈ 20 min). Capture: industry, deal size avg, customer count, value drivers, adoption curve, consumption pattern (seat \u002F usage \u002F value \u002F hybrid), competitor models.\n\n### Step 2 — Pick the pricing model\n\nRun `scripts\u002Fpricing_model_picker.py --input brief.json --profile saas --output markdown`. Output ranks 5 models by fit-score 0-100 with trade-offs. Decision logic is deterministic: low usage variance + high seat-attach → subscription wins; power-law usage + variable customer value → usage-based wins.\n\n### Step 3 — Validate WTP with Van Westendorp PSM\n\nIf you have survey data (≥ 4 questions per respondent: too cheap \u002F bargain \u002F getting expensive \u002F too expensive), run `scripts\u002Fwtp_analyzer.py --input survey.json --output markdown`. Output: 4 intersection points (OPP, IDP, PMC, PME) and the Range of Acceptable Prices.\n\nPSM gives a **range**, not the price. See `references\u002Fvan_westendorp_methodology.md` for common misinterpretations.\n\n### Step 4 — Design packaging\n\nRun `scripts\u002Fpackaging_designer.py --input features.json --profile saas --output markdown`. Output: 3-tier Good\u002FBetter\u002FBest assignment with anti-pattern flags (decoy tier, feature dump, no upgrade trigger, Bronze loss leader, Enterprise no-anchor).\n\n### Step 5 — Decide\n\nTake model + range + packaging into the pricing committee. Skill does not commit the number — you do.\n\n## Scripts\n\n- `scripts\u002Fpricing_model_picker.py` — 5-model fit scorer (subscription \u002F usage \u002F value \u002F freemium \u002F hybrid)\n- `scripts\u002Fwtp_analyzer.py` — Van Westendorp PSM implementation\n- `scripts\u002Fpackaging_designer.py` — Good\u002FBetter\u002FBest tier designer with anti-pattern detection\n\nAll scripts: stdlib only. `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fsaas_pricing_canon.md` — Skok, Tunguz, Campbell, Ramanujam, BVP, Shevlin, Stanford GSB\n- `references\u002Fvan_westendorp_methodology.md` — original 1976 paper, NMS refinement, Conjoint.ly, Sawtooth, ESOMAR, Lipovetsky, Decision Analyst\n- `references\u002Fpackaging_anti_patterns.md` — ProfitWell, OpenView, BVP vertical SaaS, Ramanujam, Poyar, SaaS Capital\n\n## Assumptions\n\n- Pricing decisions are joint: Commercial owns the model + tier shape, Product owns the features-per-tier, Finance owns the discount envelope, Legal owns the contract.\n- Van Westendorp PSM is a **directional** tool. N ≥ 30 minimum, N ≥ 100 preferred. Below 30, the script emits a sample-size warning.\n- \"Value-based pricing\" requires a measurable customer value driver (revenue lift, cost saved, time recovered). If you can't measure it, don't pick value-based.\n- Industry profiles tune defaults — they don't override your data.\n- This is a decision-support skill, not a price oracle. Output is a model + range, never the number.\n\n## Anti-patterns\n\n- **Recommending a specific number.** This skill emits a model and a range. Final price is a human commercial decision involving deal-desk policy, competitive intel, and strategic intent that this skill cannot know.\n- **Using PSM with N \u003C 30.** Statistical noise dominates. The script warns; respect the warning.\n- **Treating PSM as \"the price.\"** PSM gives a Range of Acceptable Prices (RAP) and an Optimal Price Point (OPP). Test the range in market, don't anchor on a single intersection.\n- **Picking value-based pricing without a measurable value metric.** Without instrumentation to show customer ROI, value-based collapses into \"whatever they'll pay\" — which is just bad usage-based pricing.\n- **Designing tiers before picking a model.** Tier structure depends on the model. Run pricing_model_picker first.\n- **Packaging \"feature dumps\" into the Best tier.** If Best has 3x the features for 2x the price, customers buy Better and never upgrade. See `packaging_anti_patterns.md`.\n- **Hidden usage-based pricing inside subscription tiers.** \"Up to 100k API calls\u002Fmo, then $X per 1k\" disguised as a \"Pro tier\" is two pricing models in one. Customers notice. Pick one.\n- **Confusing this skill with deal-desk.** Pricing strategy = the menu. Deal-desk = approving discounts off the menu. Different decision, different cadence, different owner.\n\n## Distinct from\n\n- **deal-desk** — per-deal discount approval, MEDDIC, deal scoring. Operates daily on existing pricing.\n- **c-level-advisor\u002Fcmo-advisor** — strategic positioning, brand, category. Pricing strategist consumes positioning as input, doesn't generate it.\n- **c-level-advisor\u002Fcro-advisor** — full-funnel revenue strategy, comp plans, territory design. Pricing strategist is one input to CRO.\n- **business-growth\u002Fsales-engineer** — technical sale, POC scoping. Sales engineering operates after pricing is set.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-commercial` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is your customer paying for outcomes, seats, or usage?\"**\n   Recommended: outcomes (value-based) if you can measure them; usage if marginal cost is variable; seats only if usage is roughly flat per user.\n   Canon: Ramanujam 2016 (*Monetizing Innovation*) — Mistake #1 of 9: seat-based pricing on a usage-variable product caps TAM at ~20% of WTP.\n\n2. **\"Do you have a measurable value metric, or are you guessing?\"**\n   Recommended: instrument the value metric BEFORE going to market with value-based pricing.\n   Canon: Patrick Campbell \u002F ProfitWell research — value-based without instrumentation collapses into bad usage-based pricing.\n\n3. **\"What's the variance in customer usage across your top decile vs. median?\"**\n   Recommended: variance > 10x → usage-based wins; variance \u003C 3x → subscription wins; in between → hybrid with usage overage.\n   Canon: Kyle Poyar (*Growth Unhinged*) — high-variance products lose 60%+ of revenue on flat-rate plans.\n\n4. **\"What's your competitor's pricing model, and why are you choosing the same or different?\"**\n   Recommended: surface the differentiation hypothesis explicitly. Identical pricing = identical value claim.\n   Canon: David Skok (*For Entrepreneurs*) — pricing is a positioning signal.\n\n5. **\"What sample size do you have for WTP analysis, and is it segmented?\"**\n   Recommended: N≥30 per segment for PSM, N≥100 for conjoint.\n   Canon: van Westendorp 1976 \u002F Sawtooth Software methodology — sub-30 PSM is statistical noise.\n\n6. **\"What's the ONE feature that forces a tier upgrade?\"**\n   Recommended: every Better and Best tier needs a single non-negotiable upgrade trigger.\n   Canon: Ramanujam (*Monetizing Innovation*) — Mistake #4: tiers with no clear differentiator make 70% of customers pick the cheapest.\n\nWalk depth-first. Lock 1-3 before opening 4-6. After all 6 are answered, invoke `pricing_model_picker.py` → `wtp_analyzer.py` → `packaging_designer.py` in sequence.\n",{"name":5,"tags":23,"author":31,"license":14,"version":32,"description":7,"compatible_tools":33},[24,25,26,27,28,29,30],"commercial","pricing","packaging","wtp","van-westendorp","value-based-pricing","saas-pricing","claude-code-skills","2.8.0",[34,35,36,37,38,39],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add ASoudy\u002FAGS --skill pricing-strategist",{"tool":52,"command":53},"bunx","bunx skills add ASoudy\u002FAGS --skill pricing-strategist",{"tool":55,"command":56},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill pricing-strategist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002FSKILL.md",true,[60,66,72,76,80,86,90],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Fpricing_brief_template.md","ASSET","资产文件",3396,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Fassets\u002Fpricing_brief_template.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fpackaging_anti_patterns.md","REFERENCE","参考文档",6152,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Freferences\u002Fpackaging_anti_patterns.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fsaas_pricing_canon.md",5217,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Freferences\u002Fsaas_pricing_canon.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fvan_westendorp_methodology.md",6579,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Freferences\u002Fvan_westendorp_methodology.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fpackaging_designer.py","SCRIPT","脚本",11970,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Fscripts\u002Fpackaging_designer.py",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fpricing_model_picker.py",11402,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Fscripts\u002Fpricing_model_picker.py",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fwtp_analyzer.py",10492,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fcommercial\u002Fskills\u002Fpricing-strategist\u002Fscripts\u002Fwtp_analyzer.py",[95,102,109,116,123,130],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]