[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNNHXJHS6CXZKHHRWFS5BH":3,"skill-same:01M7DNNHXJHS6CXZKHHRWFS5BH":96},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7DNNHXJHS6CXZKHHRWFS5BH","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.","Prudhviraj101\u002FX_Agent","Prudhviraj101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141725940?v=4","01M7DN1Y3RW3QD7692M89MPS3D","MALLA PRUDHVI RAJ S S N MURTHY","01M7DN1Y4A763ESFP16P13EE19",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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## Quick example\n\n```bash\n# Emits a scored 5-model pricing-fit recommendation (subscription \u002F usage \u002F value \u002F freemium \u002F hybrid) for the built-in example\ncd commercial\u002Fskills\u002Fpricing-strategist && python3 scripts\u002Fpricing_model_picker.py --sample\n```\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## Quick example\n\n```bash\n# Emits a scored 5-model pricing-fit recommendation (subscription \u002F usage \u002F value \u002F freemium \u002F hybrid) for the built-in example\ncd commercial\u002Fskills\u002Fpricing-strategist && python3 scripts\u002Fpricing_model_picker.py --sample\n```\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":24,"author":32,"license":15,"version":33,"description":7,"compatible_tools":34},[25,26,27,28,29,30,31],"commercial","pricing","packaging","wtp","van-westendorp","value-based-pricing","saas-pricing","claude-code-skills","2.8.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","229636be8dd3adf33e35a2aa95b85dc022251d6b",".agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent","https:\u002F\u002Fgithub.com\u002FPrudhviraj101","B.Tech CSE (AI\u002FML) Student | Building practical software with AI 🚀 | AI\u002FML Developer | Building AI agents, intelligent automation & real-world software ","2026-10-02 21:19:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Prudhviraj101\u002FX_Agent --skill pricing-strategist",{"tool":54,"command":55},"bunx","bunx skills add Prudhviraj101\u002FX_Agent --skill pricing-strategist",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Prudhviraj101\u002FX_Agent --skill pricing-strategist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002FSKILL.md",true,[62,68,74,78,82,88,92],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fpricing_brief_template.md","ASSET","资产文件",3396,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Fassets\u002Fpricing_brief_template.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fpackaging_anti_patterns.md","REFERENCE","参考文档",6152,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Freferences\u002Fpackaging_anti_patterns.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsaas_pricing_canon.md",5217,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Freferences\u002Fsaas_pricing_canon.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fvan_westendorp_methodology.md",6579,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Freferences\u002Fvan_westendorp_methodology.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fpackaging_designer.py","SCRIPT","脚本",11970,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Fscripts\u002Fpackaging_designer.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fpricing_model_picker.py",11402,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Fscripts\u002Fpricing_model_picker.py",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fwtp_analyzer.py",10492,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fcommercial__pricing-strategist\u002Fscripts\u002Fwtp_analyzer.py",[97,106,114,122,129,137],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DQMKNKM6F5G21PPJNW3HR5","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7DQMF21V9VHCTVS8H5JFNJM","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.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7DQM8HREQ0DN1HV12K0W3VT","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7DQM5J7B71CQ8EVHBXCCCN2","systematic-planning","Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystematic-planning\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7DQKG6WREWGRRCKHCJS96Y1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7DQJY7AN1XCX6G3ACA5K4JH","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]