pricing-strategy 100/100

Is pricing-strategy safe to install?

SaferSkills independently audited pricing-strategy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/pricing-strategy/SKILL.md · 1 file

skills/pricing-strategy/SKILL.md2.4 KB · Markdown

name: pricing-strategy

description: >-

Chooses a pricing model (per-seat, usage, outcome-based, or hybrid), sets tiers,

and sanity-checks unit economics. Trigger on "how should I price", "help me price

my SaaS", "pricing tiers", "what should I charge", "outcome-based pricing", or

"are my unit economics okay".

When to use

When a founder must pick a pricing model and tiers, or pressure-test whether the current pricing supports a healthy business.

Inputs to gather

What value/outcome the product delivers and how it's measured.
ICP and their budget reality (who signs, what they spend today).
Rough cost-to-serve per customer (incl. model/API costs).
Current or guessed CAC and expected retention.

Process

Pick the model by value metric:

Per-seat — value scales with users (collaboration tools).
Usage — value scales with volume; aligns cost-to-serve.
Outcome-based — charge per result delivered (per resolved ticket, per confirmed

booking, per agent action). The 2026 shift; NRR 120-150% when it lands. See Intercom Fin (per-resolution), Zendesk (per automated resolution), Salesforce (per agent action).

Hybrid — small platform fee + outcome/usage, to floor revenue and de-risk.

Set 3 tiers (entry / pro / enterprise) anchored to value, with a clear reason

to upgrade between each. Use price anchoring — make the middle tier the obvious pick.

Sanity-check unit economics: LTV = ARPA × gross margin × avg lifetime. Target

LTV:CAC ≥ 3:1 and CAC payback < 12 months. Flag if model costs crush margin.

Stress-test churn: assume B2B 10-20%/yr, B2C 40-60%/yr; if B2C, push toward

annual or higher-value use cases.

Output

Recommended model + one-line rationale tied to the value metric.
Tier table: name, price, who it's for, gating feature, upgrade trigger.
Unit economics: LTV, CAC, LTV:CAC, payback months, with assumptions.
One pricing experiment to run next (e.g. test outcome vs. seat on 5 deals).

Quality bar & pitfalls

Good = price maps to a value metric the customer already counts in their head.
Outcome-based requires you can attribute and measure the result — verify that first.
Avoid: cost-plus pricing; too many tiers; undercharging "to get started" (anchors low

forever); ignoring API/model cost in margin. For vertical AI, outcome + proprietary data is the durable combo.

pricing-strategy— agent skill

Is pricing-strategy safe to install?

When to use

Inputs to gather

Process

Output

Quality bar & pitfalls

Audit the pieces. Scan the whole. Decide.