goodbarber

shop-best-sellers

Run a strict best-sellers workflow for a shop app using orders and catalog data, and return a fixed-format report. Use by default whenever the user wants top products, seller ranking, revenue leaders, merchandising priorities, or a view of what is selling best, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-article-publish

Guided workflow to create a full CMS article: article item + structured body paragraphs (text, photo, quote, embed) + category, slug, publication status, scheduling, pinning, and paywall settings. Dry-run by default — the user validates before any mutation. Verifies each mutation with a get to confirm. Use by default whenever the user wants to create, write, publish, or fully set up a CMS article, blog post, or news item, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-article-restructure

Reorganize the body of an existing CMS article: reorder paragraphs, remove empty or duplicate blocks, and fix the reading flow — without rewriting the article from scratch. Dry-run by default — the user approves the new layout before any mutation. Use by default whenever the user wants to reorder, move, clean up, or restructure an article's paragraphs/sections, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-content-audit

CMS content quality audit across articles, events, maps, photo galleries, videos, and sounds: detect incomplete items (no cover, empty body, missing category, events missing dates, map points missing coordinates, premium items with no free preview) and produce a prioritized cleanup todo list. Read-only — suggests fixes but does not apply them. Use by default whenever the user wants to audit content quality, find incomplete posts, or clean up the CMS, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-draft-review

Surface unfinished CMS content: drafts and never-published items across articles, events, maps, and videos, grouped by type and age, with a recommended action (publish, finish, or delete) for each. Read-only — recommends but does not mutate. Use by default whenever the user wants to review drafts, find unpublished content, clean up work-in-progress, or see what is sitting unfinished, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-editorial-calendar

Build a forward-looking CMS editorial calendar: scheduled publications (status=stock with a future publishedDate), upcoming agenda events, and content set to auto-unpublish (publicationEndDate), grouped into urgency buckets. Read-only. Use by default whenever the user wants to know what is scheduled to go live, which events are coming up, or what content expires soon, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-event-publish

Guided workflow to create a full CMS agenda event: event item (start/end datetime, category, status, scheduling, paywall) + structured body paragraphs (text, photo, quote, embed). Dry-run by default — the user validates before any mutation. Verifies each mutation with a get to confirm. Use by default whenever the user wants to create, add, schedule, or publish an event, agenda item, or calendar entry, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-gallery-builder

Guided workflow to build a CMS photo gallery: batch-upload images (1–10 per batch) into a gallery section, then set each photo's title, description, and publication status. Dry-run by default — the user validates before any upload. Verifies with a list to confirm. Use by default whenever the user wants to create a gallery, add photos, upload images, or build a photo album, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-paywall-audit

In-app-purchase paywall consistency audit for CMS content: review accessTier (free/premium) and, for articles, maxFreeParagraphs and displaySummaryInList, flagging premium items with no free preview, invalid field combinations, and previews longer than the body. Read-only — recommends but does not mutate. Only meaningful for apps that sell in-app purchases. Use by default whenever the user wants to audit paywalls, premium content, free previews, or IAP gating, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-place-publish

Guided workflow to create a full CMS map point of interest: map item (address + latitude/longitude, category, status, scheduling, paywall) + structured body paragraphs (text, photo, quote, embed). Dry-run by default — the user validates before any mutation. Verifies each mutation with a get to confirm. Use by default whenever the user wants to add a place, location, venue, store, point of interest, or map pin, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-stale-content-refresh

Find aging CMS articles that haven't been touched in a long time and rank them as refresh or unpublish candidates, by age and category. Read-only — recommends but does not mutate. Use by default whenever the user wants to find old content, stale articles, things to update or retire, or content due for a refresh, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

cms-weekly-digest

Automated weekly CMS recap: what was published in the last 7 days across articles, events, maps, photo galleries, videos, and sounds, plus what is scheduled to go live in the next 7 days. Read-only. Use by default whenever the user wants a content recap, an editorial weekly summary, or a "what shipped this week" view of the CMS, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

community-device-landscape

Device landscape report for community apps. Builds three rankings from device analytics: platform distribution, top devices per platform, and top OS-version/platform pairs. Read-only. Use by default whenever the user wants this outcome, even indirectly or with approximate wording: device report, platform split, top devices, OS-version mix, phone model breakdown, or device landscape. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

community-push-broadcast

Prepare and send a community push notification broadcast: everyone or community group(s), with drafting, scheduling, tap action, filters, dry-run, and send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants this outcome, even indirectly or with approximate wording: send a push, notify members, announce something, reach everyone, or message a group. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

community-push-targeted

Prepare and send a targeted community push notification to specific users: user resolution, drafting, scheduling, platform targeting, filters, tap action, dry-run, send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants to notify named community users or an explicit user ID list. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

community-traffic-report

Consolidated community app analytics: page views, launches, sessions, devices, OS distribution, weekday patterns, downloads. Read-only. Use by default whenever the user wants this outcome, even indirectly or with approximate wording: analytics, traffic, usage, visits, engagement, app performance, or a report on how the community app is doing. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

community-weekly-digest

Weekly community business digest ready to paste into Slack/Notion: traffic, launches, sessions, pushes sent (global + per group), engagement alerts. Read-only. Use by default whenever the user wants this outcome, even indirectly or with approximate wording: weekly digest, weekly report, recap, summary, Monday update, team update, or internal newsletter. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-catalog-audit

Shop catalog quality audit: detect incomplete products (no image, no description, no variant, no tag, no collection, missing price), produce a prioritized cleanup todo list. Read-only — suggests fixes but does not apply them. Use by default whenever the user wants to audit product quality, find incomplete listings, or clean up the catalog, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-customer-insights

Analyze the customer base: top customers by revenue, purchase frequency, loyalty status, segments to re-engage. Recommend loyalty adjustments or targeted pushes. Read-only by default; the user validates each loyalty update. Use by default whenever the user wants customer analysis, segmentation, loyalty review, re-engagement targets, or who to reward, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-kpi-monitor

KPI watchdog for shop operations: detect meaningful drops/spikes in revenue, orders, traffic, and pending-order backlog with actionable alerts. Read-only. Use by default whenever the user wants shop health monitoring, KPI checks, business alerts, or a quick read on what changed, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-low-performers

Identify the lowest-performing shop products for a selected time window (default 30 days): zero-sales first, then low quantity / low revenue. Returns action-ready rows with direct back-office links per product. Read-only. Use by default whenever the user wants to find products that are not selling, underperforming, or dragging catalog performance, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-order-followup

Produce the todo list of orders needing action: unshipped, incomplete shipping, awaiting tracking. Sorted by age and urgency. Proposes shipping updates but only applies them after validation. Use by default whenever the user wants to review pending orders, shipping follow-up, fulfillment backlog, or what still needs action, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-orphan-products

Find orphan products (products with no assigned collection), return them in a table with direct back-office links, and propose a practical collection assignment plan based on similar catalog items. Read-only. Use by default whenever the user wants to find products missing collections or clean up catalog organization, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-product-launch

Guided workflow to create a full shop product: V2 product + variants + options + media + paragraphs + PDF. Dry-run by default — the user validates each step before creation. Verifies each mutation with a get to confirm. Use by default whenever the user wants to create, launch, publish, or fully set up a shop product, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-promo-campaign

End-to-end shop promo campaign design: pick the promocode type (amount, product, collection, tag), create the code, and send the announcement push broadcast. Dry-run required before creation — the user sees exactly what will be created. Use by default whenever the user wants to plan or launch a promo, discount, sale, offer, or code-based campaign, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-promo-performance-review

Measure promo impact with a strict pre/during/post comparison: orders, revenue, AOV, and estimated lift. Read-only. Use by default whenever the user wants to review promo results, discount impact, campaign lift, or promo ROI, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-prospect-nurture

Analyze shop prospects (non-converted visitors), prioritize follow-ups, update sales notes. Produces a call queue sorted by potential. Modifies prospect notes only on request. Use by default whenever the user wants to review shop leads, prospects, follow-ups, or who to contact next, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-push-broadcast

Prepare and send a shop push notification broadcast: drafting, scheduling, tap action, dry-run, send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants to announce something to all shoppers with a push or shop notification, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-push-targeted

Prepare and send a targeted shop push notification to specific customers or prospects: recipient resolution, drafting, scheduling, tap action, dry-run, send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants to notify named shoppers, customers, prospects, or a small explicit recipient list. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-reorder-planner

Build a supplier-ready reorder queue from current stock and recent sell velocity. Prioritizes what to reorder now, soon, or monitor. Read-only. Use by default whenever the user wants reorder, restock, purchasing, stock-cover, or supplier-planning help, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-rfm-segmentation

Segment customers with an RFM model (Recency, Frequency, Monetary) and produce action-ready buckets for growth and retention. Read-only by default; execution is delegated to promo/push skills. Use by default whenever the user wants customer targeting, retention segments, scoring, or high-value/risk buckets, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-stock-check

Shop inventory audit: scan all products, identify stock-outs and low stock, produce a prioritized report with restocking recommendations. Read-only — never modifies the catalog. Use by default whenever the user wants stock status, stockout checks, low-stock triage, or restock guidance, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-traffic-report

Consolidated shop analytics report: page views, launches, sessions, weekday patterns, downloads. Read-only. Use by default whenever the user wants shop traffic, visits, engagement, usage trends, or analytics reporting, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

shop-weekly-digest

Weekly shop business digest ready to paste into Slack/Notion: revenue, orders, top products, active promocodes, traffic, pushes sent, alerts. Read-only. Use by default whenever the user wants a weekly shop recap, digest, report, or leadership-ready summary, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-device-landscape

Device landscape report for membership apps. Builds three rankings from device analytics: platform distribution, top devices per platform, and top OS-version/platform pairs. Read-only. Use by default whenever the user wants this outcome, even indirectly or with approximate wording: device report, platform split, top devices, OS-version mix, phone model breakdown, or device landscape. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-expiration-calendar

Build a day-by-day membership expiration calendar for the upcoming period (default 30 days), with urgency buckets to prioritize retention actions. Read-only. Use by default whenever the user wants to know who expires soon, what renewals are coming up, or which subscribers need retention attention next, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-internal-subscription-grant

Safe workflow to create, modify, or revoke an internal membership subscription (granted by the team, off-Stripe / off-IAP). Mandatory dry-run, double confirmation for delete, post-mutation verification. Use by default whenever the user wants to grant, gift, comp, extend, fix, or revoke internal access, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-longest-subscribers

Build a membership leaderboard with two ranked tables: (1) currently active users by longest subscription duration, (2) all users (active or not) by longest subscription duration. Default output size is 10 rows per table and can be overridden. Use by default whenever the user wants the longest-tenured subscribers, top subscribers, a loyalty leaderboard, or duration-based rankings, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-prospect-followup

Prioritize membership prospects and update their sales notes after interaction. Read for analysis, write only note-by-note. Use by default whenever the user wants a follow-up queue, lead triage, prospect tracking, outreach planning, or prospect-note updates, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-push-broadcast

Prepare and send a membership push notification broadcast: drafting, scheduling, tap action, filters, dry-run, send. The push is NEVER sent without explicit confirmation. Membership broadcasts do not support group targeting. Use by default whenever the user wants to notify all subscribers or app users, announce something in the app, or send a push, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-push-targeted

Prepare and send a targeted membership push notification to specific users or subscription-status audiences: recipient resolution, drafting, scheduling, platform targeting, filters, tap action, dry-run, send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants to notify named members, prospects, active subscribers, expired subscribers, or users without an active subscription. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-subscription-audit

Full audit of membership subscriptions: active vs expired, churn detection, at-risk customers, winback opportunities. Updates subscription notes only on request. Use by default whenever the user wants subscription health, churn, retention risk, winback candidates, or an overall membership status review, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-traffic-report

Consolidated membership app analytics: page views, launches, sessions, devices, OS distribution, weekday patterns, downloads. Read-only. Use by default whenever the user wants traffic, analytics, usage, visits, engagement, or an app-performance snapshot, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.

membership-weekly-digest

Weekly membership business digest ready to paste into Slack/Notion: active vs expired subscriptions, net subscriber delta, traffic, pushes sent, at-risk subscribers. Read-only. Use by default whenever the user wants a weekly recap, business summary, team update, or ready-to-share membership report, even indirectly or with approximate wording. Prefer this skill over raw MCP-tool handling when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.