Agent skill

Pricing Strategy

by alirezarezvani in alirezarezvani/claude-skills

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

MITAuto-check passedSales & Support

Install Pricing Strategy

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill pricing-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills pricing-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/pricing-strategy .claude/skills/pricing-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pricing-strategy
GitHub stars
28k
Used in
1 other repo
Token cost
~3.5k tokens
SKILL.md length
1,729 words
Files
4 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

  • Works in 3 steps: Current State → Business Context → Goals
  • Building a pricing model from scratch
  • SKILL.md covers Before Starting, How This Skill Works, The Three Pricing Axes and Value Metric Selection, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Pricing Strategy is an agent skill from alirezarezvani/claude-skills. Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy…

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/pricing-models.md`, `references/pricing-page-playbook.md` and `scripts/pricing_modeler.py`).

It sits in Sales & Support, covering Pricing strategy and Landing pages. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Building a pricing model from scratch
  • Redesigning existing pricing
  • Planning a price increase
  • Improving a pricing page

Example prompts

  • “/pricing-strategy”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Current State
  2. Business Context
  3. Goals

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pricing Strategy loads about 3.5k tokens when it runs, and up to ~7.4k if it reads all its reference files. Until then it costs about 165 tokens; SKILL.md has 1,729 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,729 words, ~3,519 tokens.

Download SKILL.mdSave it as .claude/skills/pricing-strategy/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
pricing-strategy
description
Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.
license
MIT
metadata.version
1.0.0
metadata.author
Alireza Rezvani
metadata.category
marketing
metadata.updated
2026-03-06

Pricing Strategy

You are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.

Pricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context:

1. Current State
  • Do you have pricing today? If so: what plans, what price points, what's the billing model?
  • What's your conversion rate from trial/free to paid? (If known)
  • What's your average revenue per customer?
  • What's your monthly churn rate?
2. Business Context
  • Product type: B2B or B2C? Self-serve or sales-assisted?
  • Customer segments: who are your best customers vs. casual users?
  • Competitors: who do customers compare you to, and what do those cost?
  • Cost structure: what does serving one customer cost you per month?
3. Goals
  • Are you designing, optimizing, or planning a price increase?
  • Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)

How This Skill Works

Mode 1: Design Pricing From Scratch

Starting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.

Mode 2: Optimize Existing Pricing

Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.

Mode 3: Plan a Price Increase

Prices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.


The Three Pricing Axes

Every pricing decision lives across three axes. Get all three right.

         ┌─────────────────┐
         │   PACKAGING     │  What's in each tier?
         │  (what you get) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  VALUE METRIC   │  What do you charge for?
         │ (how it scales) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  PRICE POINT    │  How much?
         │    (the number) │
         └─────────────────┘

Most teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.


Value Metric Selection

Your value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.

Common Value Metrics for SaaS
MetricBest ForExample
Per seat / userCollaboration tools, CRMsSalesforce, Notion, Linear
Per usageAPI tools, infrastructure, AIStripe, Twilio, OpenAI
Per featurePlatform plays, add-onsIntercom, HubSpot
Flat feeUnlimited-feel, SMB toolsBasecamp, Calendly Basic
Per outcomeHigh-value, measurable ROICommission-based tools
HybridMix of aboveMost mature SaaS
How to Choose

Answer these questions:

  1. What makes a customer willing to pay more? → That's your value metric
  2. Does the metric scale with their success? → If they grow, you grow
  3. Is it easy to understand? → Complexity kills conversion
  4. Is it hard to game? → Customers shouldn't be able to work around it

Red flags:

  • "Per seat" in a tool where one power user does all the work → seats don't scale with value
  • "Flat fee" when some customers derive 10x the value of others → you're subsidizing heavy users
  • "Per API call" when call count varies wildly week to week → unpredictable bills = churn

Good-Better-Best Tier Structure

Three tiers is the standard. Not because of tradition — because it anchors perception.

Tier Design Principles

Entry tier (Good):

  • Captures the segment that will churn if priced higher
  • Limited — either by features, usage, or support
  • NOT free. Free is a separate strategy (freemium), not a tier.
  • Should cover your costs at minimum

Middle tier (Better) — your default:

  • This is where you push most customers
  • Price: 2-3x the entry tier
  • Features: everything a growing company needs
  • Call it out visually as recommended

Top tier (Best):

  • For high-value customers with enterprise needs
  • May be "Contact us" or custom pricing
  • Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts
  • If you have enterprise deals >$1k MRR, this tier exists to capture them
What Goes in Each Tier
Feature CategoryEntryBetterBest
Core product✅ (limited)✅ (full)✅ (full)
Usage limitsLowMediumHigh / unlimited
Users/seats1-35-unlimitedUnlimited
IntegrationsBasicFullFull + custom
ReportingBasicAdvancedCustom
SupportEmailPriorityDedicated CSM
Admin features——SSO, audit log, SCIM
SLA——✅

See references/pricing-models.md for model deep dives and SaaS examples.


Value-Based Pricing

Price between the next-best alternative and your perceived value.

[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]

Step 1: Define the next-best alternative

  • What would the customer do if your product didn't exist?
  • A competitor? A spreadsheet? Manual process? Hiring someone?
  • What does that cost them?

Step 2: Estimate value delivered

  • Time saved × hourly rate of the person using it
  • Revenue generated or protected
  • Cost of error/risk avoided
  • Ask your best customers: "What would you lose if you stopped using us tomorrow?"

Step 3: Price in the middle

  • A rough heuristic: price at 10-20% of documented value delivered
  • Don't price at 50% of value — customers feel they're overpaying
  • Don't price below the next-best alternative — signals you don't believe in your own product

Conversion rate as a signal:

  • 40% trial-to-paid: likely underpriced — test a price increase

  • 15-30%: healthy for most SaaS
  • <10%: pricing may be high, or trial-to-paid funnel has friction

Pricing Research Methods

Van Westendorp Price Sensitivity Meter

Four questions, asked to current customers or target segment:

  1. At what price would this product be so cheap you'd question its quality?
  2. At what price would this product be a bargain — great deal?
  3. At what price would this product start to feel expensive — still acceptable?
  4. At what price would this product be too expensive to consider?

Interpret the results: Plot the four curves. The intersection of "too cheap" and "too expensive" gives your acceptable price range. The intersection of "bargain" and "expensive" gives the optimal price point.

When to use: B2B SaaS, n≥30 respondents, existing customers or qualified prospects.

MaxDiff Analysis

Show respondents sets of features/prices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.

When to use: When deciding which features to put in which tier.

Competitor Benchmarking
StepWhat to Do
1List direct competitors and alternatives customers consider
2Record their published pricing (plan names, prices, value metrics)
3Note what's included at each price point
4Identify where your product over- and under-delivers vs. each
5Price relative to positioning: premium = 20-40% above market, value = at or below

Don't just copy competitor prices — their pricing reflects their cost structure and positioning, not yours.


Show full SKILL.md (659 more words)Show less

Price Increase Strategies

Raising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.

Strategy Selection
StrategyUse WhenRisk
New customers onlySignificant pushback expectedLow — doesn't touch existing base
Grandfather + delayedLoyal customer base, contract riskMedium — existing customers feel respected
Tied to value deliveryClear new features/improvementLow — justifiable
Plan restructureSignificant packaging changeMedium — complexity for customers
Uniform increaseConfident in value, price is clearly below marketMedium-High
Execution Checklist
  1. Quantify the move: Calculate new MRR at 100%, 80%, 70% retention of existing customers
  2. Segment by risk: Annual contracts, champions vs. detractors, usage-based at-risk accounts
  3. Set the date: 60-90 days notice for existing customers. 30 days minimum.
  4. Communicate the reason: New features, rising costs, investment in [X] — be specific
  5. Offer a path: Lock in current price for annual commitment, or give a 3-month window
  6. Arm your CS team: FAQ, talking points, approved offer authority
  7. Monitor for 60 days: Churn rate, downgrade rate, support ticket volume

Expected churn from a 20-30% price increase: 5-15%. If your net revenue impact is positive, proceed.


Pricing Page Design

The pricing page converts intent to purchase. Design it with that job in mind.

Above the Fold

Must have:

  • Plan names (simple: Starter / Pro / Enterprise, or named after customer segment)
  • Price with billing toggle (monthly/annual — annual should show savings)
  • 3-5 bullet differentiators per plan
  • CTA button per plan
  • "Most popular" badge on recommended tier
Below the Fold
  • Full feature comparison table — comprehensive, scannable, uses ✅ and ❌ not walls of text
  • FAQ section — address the 5 objections that stop people from buying:
    • "Can I cancel anytime?"
    • "What happens when I hit limits?"
    • "Do you offer refunds?"
    • "Is my data secure?"
    • "What if I need to upgrade/downgrade?"
  • Social proof — logos, quotes, or case studies relevant to each tier
  • Security badges if B2B enterprise (SOC2, ISO 27001, GDPR)
Annual vs. Monthly Toggle
  • Show annual pricing by default (or highlight it) — it improves LTV
  • Show savings explicitly: "Save 20%" or "2 months free"
  • Don't hide the monthly price — hiding it builds distrust

See references/pricing-page-playbook.md for design specs and copy templates.


Proactive Triggers

Surface these without being asked:

  • Conversion rate >40% trial-to-paid → Strong signal of underpricing. Flag: test 20-30% price increase.
  • All customers on the middle tier → No upsell path. Flag: enterprise tier needed or feature lock-in missing.
  • Customer asked for features that aren't in their tier → Expansion revenue being left on the table. Flag: feature gatekeeping review.
  • Churn rate >5% monthly → Before raising prices, fix churn. Price increases accelerate churners.
  • Price hasn't changed in 2+ years → Inflation alone justifies 10-15% increase. Flag for strategic review.
  • Only one pricing option → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.

Output Artifacts

When you ask for...You get...
"Design pricing"Three-tier structure with value metric, feature grid, price points, and rationale
"Audit my pricing"Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins
"Plan a price increase"Increase strategy selection, communication templates, risk model, 90-day rollout plan
"Design a pricing page"Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy
"Research pricing"Van Westendorp survey questions + MaxDiff framework for your specific product
"Model pricing scenarios"Run scripts/pricing_modeler.py with your inputs

Communication

All output follows the structured communication standard:

  • Bottom line first — recommendation before justification
  • What + Why + How — every recommendation has all three
  • Actions have owners and deadlines — no vague "consider"
  • Confidence tagging — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed

  • product-strategist: Use for product roadmap and broader monetization strategy. NOT for pricing page or price increase execution.
  • copywriting: Use for pricing page copy polish. NOT for pricing structure or tier design.
  • churn-prevention: Use when churn is the underlying issue — fix retention before raising prices.
  • ab-test-setup: Use to A/B test price points or pricing page layouts after initial design.
  • customer-success-manager: Use for expansion revenue through upselling. NOT for pricing design or packaging.
  • competitor-alternatives: Use for competitive comparison pages that complement pricing pages.

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in marketing-skill/skills/pricing-strategy of alirezarezvani/claude-skills.

  • SKILL.md
  • references/pricing-models.md
  • references/pricing-page-playbook.md
  • scripts/pricing_modeler.py

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Pricing Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pricing Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pricing Strategy this skillalirezarezvani/claude-skills28k1 repos~3.5kAutomated safety check: PassMIT
Pricing FinderVarnan-Tech/opendirectory674—~6.8kAutomated safety check: PassMIT
Paw Mkt Pricingpawbytes/skill-suites113—~2.1kAutomated safety check: PassMIT
Pricemenkesu/awesome-pm-skills433—~5.3kAutomated safety check: PassCustom licence
Pricing StrategyOpenClaudia/openclaudia-skills713—~1.8kAutomated safety check: PassMIT
Suede PricingJasonColapietro/suede-creator-skills127—~2.4kAutomated safety check: PassMIT

Similar skills

  • Pricing Finder

    Varnan-Tech/opendirectory

    Tell it what your product is (URL or description) and it finds 5 competitors globally, fetches their actual pricing pages, extracts every tier and price point, and returns a complete pricing…

    674 GitHub stars~6.8k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Paw Mkt Pricing

    pawbytes/skill-suites

    Pricing models, tier packaging, and willingness-to-pay research.

    113 GitHub stars~2.1k tokensUpdated 5 days ago
    Sales & SupportAuto-check passed
  • Price

    menkesu/awesome-pm-skills

    Builds a pricing model, packaging/tier structure and willingness-to-pay research plan, then grades your existing pricing page or plan.

    433 GitHub stars~5.3k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Pricing Strategy

    OpenClaudia/openclaudia-skills

    Optimize pricing pages, pricing models, and pricing strategy.

    713 GitHub stars~1.8k tokensUpdated 21 days ago
    Sales & SupportAuto-check passed
  • Suede Pricing

    JasonColapietro/suede-creator-skills

    Suede-owned pricing and packaging discipline. An agent skill from JasonColapietro/suede-creator-skills.

    127 GitHub stars~2.4k tokensUpdated today
    Sales & SupportAuto-check passed
  • Competitor Price Tracker

    OneWave-AI/claude-skills

    Monitor competitor pricing pages and send alerts when prices change.

    328 GitHub starsUsed in 2 repos~372 tokens
    Sales & SupportAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Categories

Questions about Pricing Strategy

What does Pricing Strategy do?

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Pricing Strategy is an agent skill from alirezarezvani/claude-skills. Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

When should I use Pricing Strategy?

Pricing Strategy fits situations like: building a pricing model from scratch; redesigning existing pricing; planning a price increase; improving a pricing page.

How do I install Pricing Strategy in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill pricing-strategy -a claude-code`. Or copy the skill folder (marketing-skill/skills/pricing-strategy in alirezarezvani/claude-skills) into .claude/skills/pricing-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Pricing Strategy in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill pricing-strategy -a codex`. Or copy the skill folder (marketing-skill/skills/pricing-strategy in alirezarezvani/claude-skills) into .agents/skills/pricing-strategy in your project. Codex loads it when a task matches its description.

Can I use Pricing Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill pricing-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pricing-strategy, .gemini/skills/pricing-strategy, .github/skills/pricing-strategy and .opencode/skills/pricing-strategy in your project.

What does Pricing Strategy need to run?

Going by SKILL.md and its folder, Pricing Strategy needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Pricing Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pricing Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Pricing Strategy use?

Pricing Strategy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pricing Strategy use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Pricing Strategy?

Skills that share tags, products or a category with Pricing Strategy: Pricing Finder (Varnan-Tech/opendirectory, 674 stars), Paw Mkt Pricing (pawbytes/skill-suites, 113 stars), Price (menkesu/awesome-pm-skills, 433 stars) and Pricing Strategy (OpenClaudia/openclaudia-skills, 713 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pricing Strategy?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,891 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.