Skills for Creators
The skills that let Claude run a Subscriby community through the MCP server, from the launch to the week's figures, with the example prompts that trigger each and the point at which each one asks before it changes anything.
A creator skill is a procedure for one part of running the community, written for Claude: the concept model it needs, the order to do things in, the tools it may use, the point at which it must stop and ask, and the page here it rests on. Claude loads a skill when your request matches its description, so you ask in plain words and the right procedure follows. Every write is shown before it runs; every figure comes with the tool call behind it.
account-and-billing
Used when the user asks about their own Subscriby account, notifications and where alerts go, exporting their data, the Partner Program and its commissions or payouts, transaction fees and invoices, Copilot Credits and packs, their creator plan or addons, or their API tokens.
Rests on /account, /account/notifications, /account/partner-program.
analytics
Used when the user asks for figures, trends, revenue, MRR, churn, trial conversion, earnings by period, plan performance, where revenue comes from, subscriber counts, a report, the transaction ledger, or the activity log of a member, a subscription or a project.
Rests on /creators/dashboard-analytics, /creators/exporting-data, /mcp/v1/prompting-guide.
broadcasts
Used when the user asks to send a message, announcement or reminder to members, a segment, a plan's members, pass holders or people whose access is expiring, to preview who a broadcast reaches, to read a broadcast's history or who it missed, or to retry or resend one.
Rests on /creators/broadcasts.
connectors
Used when the user asks about a project's connectors, installations or bots and their health, the Connectors Marketplace, installing, verifying, configuring, diagnosing, disconnecting or uninstalling a connector, the places a connector gates, or Telegram and Discord specifics.
Rests on /connectors, /connectors/marketplace, /connectors/telegram.
coupons-and-access-codes
Used when the user asks to create or manage a coupon or discount code, run a sale, generate access codes for a giveaway, an offline sale, a gift, team access or a migration, revoke a code, check a code that does not work, or asks what the code quota and overage cost are.
Rests on /creators/coupon-codes, /creators/codes, /payments/access-codes.
disaster-recovery
Used when the user asks about a banned bot, place or account, an outage or degraded installation, recovery incidents and operations, standbys, the live mirror, automatic failover, readiness, the roll call, undo, allowances or outage compensation.
Rests on /disaster-recovery, /disaster-recovery/how-detection-works, /disaster-recovery/replacing-places.
knowledge
Used when the user asks to teach Subscriby Copilot something about a project, add a question and answer or a guide to Knowledge, decide whether members or only the team may be answered from it, check what the Copilot knows, or read, change or remove a Knowledge entry.
Rests on /creators/knowledge, /copilot/what-it-can-do.
launch-project
Used when the user asks to create a new Subscriby project, launch or set up a paid community from nothing, go live, run the go-live checklist, or asks what a project needs before it can sell. From an empty project to a live one, in order, with the writes confirmed one at a time.
Rests on /creators/projects, /creators/resources, /creators/methods.
members
Used when the user asks about a project's members or subscribers, who lapsed or churned, a member's connected accounts, members waiting on a connection, banning, unbanning or kicking someone, the perks still to hand over, or a member's access grants and invite links.
Rests on /creators/managing-members, /subscribers/on-the-platform.
plans-and-passes
Used when the user asks to create, price, edit, publish, reorder or delete a plan, set a billing cycle or trial, restrict who can buy, sell a time-limited pass or a pass series, schedule or cancel access windows, remind pass holders, or start a next season.
Rests on /creators/plans, /creators/time-limited-passes, /creators/pass-series.
portal-design
Used when the user asks to change how a project's portal page looks or reads, its colours, fonts, layout, wording, blocks, announcement, gallery, footer, pixels, CSS or languages, to publish or discard a portal draft, or for the portal address or a bot deep link.
Rests on /creators/portal-design, /creators/portal-css, /creators/share.
referral-program
Used when the user asks about a project's Referral Program, affiliates, referral codes or links, free membership days or cash commissions for members who bring friends, approving or suspending an affiliate, the reward ledger, or recording a payout to an affiliate.
Rests on /creators/referral-program, /addons/referral-program, /subscribers/refer-a-friend.
revenue-recovery
Used when the user asks about failed renewals, the grace window, dunning, why members leave, cancellation reasons or offers, win-back or nurture sequences, leads who never bought, stalled checkouts, trials about to end, or the Revenue Recovery figures and settings.
Rests on /creators/revenue-recovery, /addons/revenue-recovery, /subscribers/follow-up-messages.
smart-links
Used when the user asks to track where members come from, create a tracked link for a bio, a video, a newsletter or a QR code, read a link's clicks, leads, checkouts, paid members and revenue, compare channels, embed plans on a website, or rename, expire or archive a link.
Rests on /creators/smart-links, /creators/share.
subscriptions-and-payments
Used when the user asks about subscriptions and their statuses, cancelling, pausing or reactivating one, a member's payments, transactions, refunds or failed charges, payment methods and gateways, test against live mode, or the currency a member pays in.
Rests on /creators/managing-subscriptions, /creators/transactions, /creators/methods.
support-inbox
Used when the user asks about member messages, the support inbox or a conversation, to triage, reply, resolve, reopen, assign or block, to manage saved replies, or to change the inbox settings, including whether Subscriby Copilot may answer members in the inbox or on the portal.
Rests on /creators/support-inbox, /copilot/in-your-inbox.
teams-and-roles
Used when the user asks about teams, inviting or removing a collaborator, changing someone's role, creating or editing roles and groups, which permissions a teammate holds, or why a team action is refused on their plan.
Rests on /teams, /teams/roles, /teams/groups.
Three rules every creator skill shares
Read before writing, so Claude knows the project's real state and never guesses an id. Confirm every change, with the exact wording when a message will reach a person. Never promise what a tool cannot do: a refund, a gateway connection and your own Subscriby billing stay in the dashboard, and the skill says so.
Each skill, with the prompts that start it
Related
- Slash commands:
/subscriby:launch,/subscriby:doctor,/subscriby:statusand/subscriby:weeklyrun the routines above in a fixed order. - Subagents: the launch auditor and the community analyst report on the same reads.
- Creator guide: the pages the skills rest on.
How is this guide?
Last updated on
Install and Sign In
Add the envigo marketplace, install the subscriby plugin and its guard, sign in to the bundled MCP server and prove the connection, in the terminal, the VS Code extension, claude.ai or any other agent.
Skills for Developers
The skills that let Claude integrate Subscriby into whatever you are building, from a verified webhook receiver and the right events to tokens, retries, the Zapier and n8n nodes, OpenAPI toolkits, your own agent and every MCP client.