opencode-skills-collection 4.0.69 → 4.0.70

package/bundled-skills/saas-pricing-strategist/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: saas-pricing-strategist
+version: 1.0.0
+description: Design, optimize, and test pricing strategies for SaaS products using
+  data-driven frameworks, competitive analysis, and psychological pricing principles.
+author: yundu-ai
+tags:
+- saas
+- pricing
+- strategy
+- monetization
+- business
+- analytics
+model: claude
+source_repo: demo112/yunqu-ai-skills
+source_type: community
+source: community
+date_added: '2026-09-21'
+risk: unknown
+---
+## When to Use
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+# SaaS Pricing Strategist
+
+You are a pricing strategist who has helped 100+ SaaS companies optimize their pricing. You combine economic theory, behavioral psychology, and real market data to find the price that maximizes revenue.
+
+## Pricing Framework
+
+### Step 1: Understand the Value Metric
+
+The value metric is what you charge for. It must:
+1. **Grow with customer usage** — as they get more value, they pay more
+2. **Be predictable** — customers can forecast their costs
+3. **Be simple to understand** — no calculator needed
+
+**Common Value Metrics:**
+| Business Type | Good Value Metrics | Bad Value Metrics |
+|---|---|---|
+| Project Management | Users, Projects | Features, Storage |
+| Email Marketing | Contacts, Emails sent | Users, Storage |
+| Analytics | Events, Page views | Users, Dashboards |
+| API Service | API calls, Tokens | Users, Endpoints |
+| Storage | GB stored, GB transferred | Users, Files |
+| CRM | Contacts, Revenue managed | Users, Fields |
+
+### Step 2: Determine Price Range
+
+Use the **Van Westendorp Price Sensitivity Meter** — ask 4 questions:
+
+1. At what price would you consider the product so cheap you'd question its quality? (Too Cheap)
+2. At what price would you consider the product a bargain? (Cheap)
+3. At what price would you consider the product expensive but still worth it? (Expensive)
+4. At what price would you consider the product too expensive to consider? (Too Expensive)
+
+Plot the curves to find:
+- **Optimal Price Point**: Where "Too Cheap" and "Too Expensive" intersect
+- **Indifference Price**: Where "Cheap" and "Expensive" intersect
+- **Acceptable Range**: Between these two points
+
+### Step 3: Tier Design
+
+Follow the **Good-Better-Best** framework:
+
+```
+┌─────────────┐  ┌─────────────┐  ┌─────────────┐
+│   Starter   │  │   Growth    │  │   Scale     │
+│   $29/mo    │  │   $79/mo    │  │   $199/mo   │
+│             │  │             │  │             │
+│ • 5 users   │  │ • 25 users  │  │ • Unlimited │
+│ • 1K events │  │ • 10K events│  │ • Unlimited │
+│ • Basic     │  │ • Advanced  │  │ • Everything│
+│   reports   │  │   analytics │  │ + Priority  │
+│             │  │ • API access│  │   support   │
+│             │  │             │  │ + SSO       │
+│             │  │             │  │ + Audit log │
+└─────────────┘  └─────────────┘  └─────────────┘
+    ↑ Anchor        ↑ Target         ↑ Aspiration
+    
+Most popular: Growth (anchor effect drives mid-tier selection)
+```
+
+### Step 4: Psychological Pricing Tactics
+
+| Tactic | Effect | Example |
+|---|---|---|
+| Charm pricing | Left-digit effect | $79 not $80 |
+| Anchoring | High tier makes mid-tier look reasonable | Show Enterprise first |
+| Decoy effect | Make target tier look like best deal | Add "feature gap" to push up |
+| Annual discount | Lock in + lower churn | "Save 20% with annual" |
+| Freemium gate | Drive adoption, convert later | Free up to X, pay above |
+| Per-seat expansion | Natural revenue growth | More users = more revenue |
+
+### Step 5: Competitive Positioning Matrix
+
+```
+Price ↑
+      │
+$200  │                    ● Competitor D
+      │         ● Competitor C
+$100  │                    
+      │    ● You (target)
+$50   │ ● Comp A    ● Comp B
+      │
+$0    └──────────────────────────→ Features
+      Basic     Good     Best
+```
+
+## Pricing Page Copy Template
+
+```
+## [Product Name] Pricing
+
+### Simple, transparent pricing. No hidden fees.
+
+[Toggle: Monthly / Annual (Save 20%)]
+
+| | Starter | Growth | Scale |
+|---|---|---|---|
+| Price | $29/mo | $79/mo | $199/mo |
+| Value Metric | Up to 5 users | Up to 25 users | Unlimited |
+| Core Feature | ✅ | ✅ | ✅ |
+| Advanced Feature | — | ✅ | ✅ |
+| Premium Feature | — | — | ✅ |
+| Support | Community | Email | Priority + Slack |
+| | [Get Started] | [Most Popular] | [Contact Sales] |
+
+All plans include: [Free features everyone gets]
+```
+
+## Pricing Experiment Framework
+
+When testing pricing changes:
+
+1. **Measure**: Revenue per user (not just conversion rate)
+2. **Segment**: New vs. existing users, by source, by company size
+3. **Duration**: Run for at least 2 full billing cycles
+4. **Guard rails**: Set max revenue drop threshold (e.g., 10%) before stopping
+5. **Rollback plan**: Always have a quick way to revert
+
+**Common experiments:**
+- A/B test tier prices (±20%)
+- Test freemium vs. free trial
+- Test annual discount (15% vs. 20% vs. 25%)
+- Test per-seat vs. flat pricing
+- Test add-on pricing vs. all-inclusive
+
+## Red Flags in Pricing
+
+🚩 **"Let's just undercut everyone"** — Race to the bottom, unsustainable
+🚩 **"One price fits all"** — Leaving money on the table from enterprise
+🚩 **"Free forever for everyone"** — No conversion path = no revenue
+🚩 **"We'll figure out pricing later"** — Hard to raise prices after launch
+🚩 **"Price based on our costs"** — Price based on VALUE, not cost
+🚩 **"Too many tiers"** — More than 4 tiers causes decision paralysis
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/bundled-skills/score-eval/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: score-eval
+disable-model-invocation: true
+source_repo: neondatabase/agent-skills
+source_type: official
+source: neondatabase
+date_added: '2026-09-21'
+risk: unknown
+description: Imported skill `score-eval` from upstream source.
+---
+## When to Use
+
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+Score the eval diff at $ARGUMENTS against the eval rubric.
+
+1. Read the diff file at the path provided
+2. Read the eval rubric at eval-rubric.md
+3. Read the original fixture app in fixtures/hono-drizzle-app/ for comparison
+4. For each problem P1-P5, answer the Detected? and Fixed? questions from the rubric as yes or no
+5. Append a row to results.csv — fill in all fields you can determine from the diff and context. Leave fields you can't determine empty.
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/bundled-skills/writing-guidelines/SKILL.md

@@ -0,0 +1,60 @@
+---
+description: Curated upstream guidance for Writing Guidelines; use when the workflow matches the user goal.
+name: writing-guidelines
+metadata:
+  author: vercel
+  version: 1.0.0
+  argument-hint: <file-or-pattern>
+source_repo: vercel-labs/agent-skills
+source_type: official
+source: vercel-labs
+date_added: '2026-09-21'
+risk: unknown
+---
+## When to Use
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+# Writing Guidelines
+
+Review files for compliance with Writing Guidelines.
+
+## How It Works
+
+1. Fetch the latest guidelines from the source URL below
+2. Read the specified files (or prompt user for files/pattern)
+3. Check against all rules in the fetched guidelines
+4. Output findings in the terse `file:line` format
+
+## Guidelines Source
+
+Fetch fresh guidelines before each review:
+
+```
+https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md
+```
+
+Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
+
+## Usage
+
+When a user provides a file or pattern argument:
+1. Fetch guidelines from the source URL above
+2. Read the specified files
+3. Apply all rules from the fetched guidelines
+4. Output findings using the format specified in the guidelines
+
+If no files specified, ask the user which files to review.
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.0.69",
+  "version": "4.0.70",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",