技能 pricing-diagnostic
📦
pricing-diagnostic
內容修訂 r1 安全 ⚙️ 外部命令📁 檔案系統存取
Diagnose Pricing Gaps Before Changing Prices
Pricing problems can come from weak demand evidence, misaligned billing units, or confusing tiers. This skill evaluates all three and recommends a focused next step.
支援: Claude Codex Code(CC)
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "pricing-diagnostic" from https://skillstore.io/skills/cmj-hub-pricing-diagnostic.md and its manifest at https://skillstore.io/api/skills/cmj-hub-pricing-diagnostic/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「pricing-diagnostic」。 Illustrative case: research is absent, discounts exceed policy, billing aligns with value, and tested tiers are clear.
預期結果:
- Willingness to pay: low. Main gaps are missing research and discounts above policy.
- Value metric: high. The supplied billing evidence aligns charges with customer value.
- Packaging: high. Tested differentiation supports the existing tiers.
- Triage: willingness-to-pay discovery before raising prices. Suggested timeline: about four weeks.
正在使用「pricing-diagnostic」。 Illustrative case: recent segment research and billing alignment are strong, but 60% of buyers choose a confusing bottom tier.
預期結果:
- Willingness to pay: high. Recent segment evidence supports the review.
- Value metric: high. Charges scale with customer success.
- Packaging: low. Tier confusion and buyer concentration suggest a packaging problem.
- Triage: packaging rebuild rather than a price change. Suggested timeline: about three weeks.
安全審計
安全v1 • 2026/10/3 開啟版本化報告
All 23 static findings are false positives in the reviewed SKILL.md. Backticks format Markdown, parent-relative paths name documentation, and the reconnaissance match concerns customer billing behavior. No evidence found of executable commands, credential collection, data exfiltration, or prompt injection; referenced dependencies were not reviewed.
1
已掃描檔案
172
分析行數
0
複核項目
0
已忽略的誤報
風險因素
⚙️ 外部命令 (17)
📁 檔案系統存取 (5)
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/cmj-hub-pricing-diagnostic/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/cmj-hub-pricing-diagnostic?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/cmj-hub-pricing-diagnostic?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-pricing-diagnostic/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/cmj-hub-pricing-diagnostic.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
cmj-hub. (2026). pricing-diagnostic security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-pricing-diagnostic/audits/1BibTeX 引用
@techreport{cmj-hub-cmj-hub-pricing-diagnostic-2026,
author = {cmj-hub},
title = {pricing-diagnostic security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-pricing-diagnostic/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pricing-diagnostic security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-pricing-diagnostic/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-pricing-diagnostic:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 55
架構
85
可維護性
87
內容
65
社群
83
規範符合度
你可以打造什麼
Evaluate a Proposed Price Increase
Separate missing willingness-to-pay evidence from genuine pricing opportunities before deciding whether to raise prices.
Review Billing Metric Alignment
Investigate whether high-value customers pay proportionately and whether the current billing unit limits expansion.
Prioritize Tier Packaging Changes
Compare tier clarity, feature placement, and buyer distribution to determine whether packaging needs attention before price levels.
試試這些提示
Start a Pricing Review
Diagnose my pricing using the attached tiers, billing metric, customer profiles, and discount policy. Identify missing evidence before scoring.
Investigate Discount Pressure
Review these segment close rates, discounts, and willingness-to-pay research. Score the three surfaces and explain whether more research should precede a price increase.
Compare Metric and Packaging Problems
Use these usage ratios, customer payment ratios, tier features, and buyer distributions. Distinguish billing misalignment from packaging problems and prioritize the gaps.
Prepare a Pricing Triage Report
Evaluate all supplied pricing evidence by customer profile. Explain each score, apply the triage matrix, name the next workflow, and estimate a timeline.
最佳實務
- Provide dated research and segment-level evidence alongside current tiers, billing units, customer profiles, and discount policy.
- Explain each score using supplied evidence and distinguish missing data from observed problems.
- Use the triage decision to prioritize investigation before implementing a material pricing change.
避免
- Inventing willingness-to-pay percentiles, close rates, or customer usage data to complete the report.
- Treating qualitative surface scores as precise forecasts of revenue or customer response.
- Raising prices when the evidence indicates a billing metric or packaging problem.
常見問題
What inputs are required?
Provide current tiers and cadence, the billing unit, customer Pain Signal Profiles, and the discount policy.
What does the report contain?
It includes three 0-100 scores, evidence-based gaps, recommended actions, a triage decision, a next workflow, and a timeline.
Can it work without willingness-to-pay research?
It can use supplied close rates and discount evidence. It must identify missing research and must not invent willingness-to-pay numbers.
Does it automatically change prices?
No. The documented workflow produces diagnostic recommendations, not automatic billing changes or pricing-page deployment.
Is it a standalone command?
No. It is marked as not user-invocable and is designed for routing from the parent pricing skill.
What did the security review cover?
The review covered SKILL.md and adjudicated 23 static detections as false positives. Referenced resources and sibling skills were not reviewed.