Answer WordPress.com plan, pricing, upgrade, and feature-tier questions (plan names, what each tier unlocks — plugins, themes, custom code, SSH, hosting — and current prices) from authoritative live data. Load before answering ANY plan, pricing, or feature-gating question; never answer these from memory.
npx skills add https://github.com/Automattic/studio --skill hosting-plans-helper
Use this skill whenever the user asks about WordPress.com (or Pressable) plans,
pricing, upgrades, or what a plan tier unlocks — for example "which plan do I need
for plugins?", "what does Business include?", "how much is Commerce?", "can I use
custom CSS on Premium?", or "should I upgrade?".
Plan names, prices, and feature-tier gating change, and your training data is stale.
You MUST fetch current data with this skill before answering. Do not state a plan
name, a price, or which tier unlocks a feature from memory — even if you are
confident. If the fetch fails, say you can't verify current plan data right now and
point the user to https://wordpress.com/pricing; do not guess.
Fetch wpcom/v2/plans/features. It returns, per plan, the current name, the
product_slug (used to look up the price in Step 2), and the full list of features
that tier unlocks — grouped (Essential features, Performance boosters, High
Availability, Developer tools, Security, etc.).
Local sites (Bash tool available):
curl -s "https://public-api.wordpress.com/wpcom/v2/plans/features?locale=en"
Connected WordPress.com sites (wpcom_request tool available, no Bash):
wpcom_request method=GET path="!/plans/features" apiNamespace="wpcom/v2"
Fetch wpcom/v2/products for prices. It is keyed by product slug; each product has a
cost_display (the formatted, already-localized price, e.g. "$300") and a
currency_code.
Local sites:
curl -s "https://public-api.wordpress.com/wpcom/v2/products"
Connected WordPress.com sites:
wpcom_request method=GET path="!/products" apiNamespace="wpcom/v2"
Both endpoints are public (no authentication) and both are reachable in either
environment.
names.
products[ plan.product_slug ].cost_display andquote it as-is (it is already localized; mention the currency). The free plan has
no price.
per-plan features list from Step 1. Each feature has a title, a tooltip (use
it to explain), and a group. Recommend the lowest tier whose features includes
what the user needs.
unlocks for the user's stated goal.
Answer directly and authoritatively, as plain product knowledge. Do not mention that
you fetched anything, or reference "the live data", "the data I fetched", "according
to the API", or any source or tool. The fetched data is simply the truth — state it.
above."
Currently covers the WordPress.com consumer plans (Free, Personal, Premium,
Business, Commerce). If the user asks about a plan or product not in the response
(e.g. Pressable, Woo Hosted, VIP, enterprise), say it's not covered by this data and
point them to https://wordpress.com/pricing rather than answering from memory.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
Generate memes using the memegen.link API. Use when users request memes, want to add humor to content, or need visual aids for social media. Supports 100+ popular templates with custom text and styling.
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
> Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens — use frontend-design instead.
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked navigation, or requests involving private, loopback, link-local, or metadata IP destinations.
Marketing landing page and conversion-focused product page reference. Use this skill when building hero sections, feature grids, pricing pages, testimonials, CTAs, footers, navigation bars, or any public-facing marketing surface. Covers a warm, professional, developer-friendly design language (cream backgrounds, generous whitespace, pill CTAs, corner-bracket card decorations) and a complete token set, animation system, and copy-paste component snippets. NOT for product/dashboard UIs — use frontend-design-saas for those.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
Take automattic/hosting-plans-helper from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.