All authors
Claude Skills by 808enzo
github.com/808enzo36 skills0 installs48 views
- PULL REQUEST TEMPLATE**Skill:** <!-- slug, the name agreed in the issue -->Votes: 0GitHub stars: 2
- B2b LifecycleCarry a business account from first known contact to the buying group's decision. Use when leads handed to sales are never accepted or sent back, a deal sits in a stage with no next step, one champion answers and the deal dies at the budget holder, or a lost deal never comes back. Not cold outreach, or renewal after signature (b2b-retention).Votes: 0GitHub stars: 2
- B2b RetentionCarry an invoiced business contract from the won deal to the customer's renewal decision. Use when notices of non-renewal arrive too late, an auto-renewal invoice is disputed, a key client contact leaves mid-term, or an invoice stays unpaid. Not a card or app store subscription (subscription-retention) or the deal before signature (b2b-lifecycle).Votes: 0GitHub stars: 2
- Chat And BotsDecide whether a bot or a person answers someone who writes in, how the matter reaches whoever can settle it, and when it closes. Use when a bot traps people, handoffs lose context, reply times slip, or you ask what first-pass share is normal. Not messaging platform rules (messaging-channels) or surveys (voice-of-customer).Votes: 0GitHub stars: 2
- Consent And PreferencesDecide on what basis you may write to a person, by channel and purpose, and how far and fast their choices and withdrawals reach. Use when a base arrives with a subscribed flag and no proof, an unsubscribe does not reach another system, or a segment rests on sensitive data. Not the capture form (onsite-capture) or the cap (contact-orchestration).Votes: 0GitHub stars: 2
- Contact OrchestrationCap how many messages one person gets across channels and systems, and decide which message wins when two collide. Use when setting a frequency cap or quiet hours, ordering priority, deduplicating one pitch across channels, or unsubscribes rise while each campaign looks fine. Not one flow (triggered-messages) or one screen (in-product-messaging).Votes: 0GitHub stars: 2
- Crm Program DesignDecide what the CRM program is for, the single number it is judged on, who owns each part, and what gets built first. Use when starting lifecycle work from scratch, when many live mechanics add up to nothing anyone can name, or two people claim one result. Not which mechanics run (scenario-map) or a metric's formula (metric-definitions).Votes: 0GitHub stars: 2
- Crm ReportingBuild the regular program report, read change on cohorts, and keep attribution credit apart from effect. Use when someone asks for a CRM dashboard, a figure rose and nobody can say against what, or channel tools claim more orders than the business took. Not a metric's definition (metric-definitions) or test design (experiments-and-holdouts).Votes: 0GitHub stars: 2
- DeliverabilityDecide how your mail identifies itself to mailbox providers, earns volume, and recovers when a provider stops letting it through. Use when mail stops arriving at one provider, a domain lands on a blocklist, bounces or complaints spike, or a new domain starts sending. Not what goes out or to whom (email-program) or the template (email-design).Votes: 0GitHub stars: 2
- Email CopyDecide what one email says, what it promises and what it asks for, and whether the words made the difference. Use when writing or rewriting a message or a subject line, a send carries two jobs, clicks land on the wrong link, or a draft needs a go or no-go review. Not who receives it (email-program) or the template (email-design).Votes: 0GitHub stars: 2
- Email DesignMake an email template hold up in the inboxes, apps and modes its author never looked at. Use when a template is built or changed, a message looks right in the editor and broken in an inbox, images are off, or dark mode or mobile breaks it, or you ask what click rate is normal per app. Not the words (email-copy) or inbox placement (deliverability).Votes: 0GitHub stars: 2
- Email ProgramRun email as a standing program rather than one-off sends, deciding who gets what and when. Use when setting sending rhythm by engagement tier, building a slot calendar, excluding people from a send, or diagnosing a channel whose returns are falling. Not the copy (email-copy), the template (email-design) or inbox placement (deliverability).Votes: 0GitHub stars: 2
- Experiments And HoldoutsDesign a comparison a decision can rest on, from an A/B test to a control group or holdout. Use when sizing a test and its length, reading a result without over-reading it, or asking whether a mechanic produces anything beyond what customers would do on their own. Not the metric formula (metric-definitions) or the regular report (crm-reporting).Votes: 0GitHub stars: 2
- In Product MessagingDecide what the product shows someone already inside it, where, how often, and which message wins the screen. Use when every launch opens a modal, in-app messages come from systems that cannot see each other, or one pitch arrives by email, push and in-app in a day. Not push (push-notifications) or site widgets (onsite-capture).Votes: 0GitHub stars: 2
- Lapse And WinbackDecide who counts as lapsed, catch people on the way out, and run one finite attempt to bring back those already gone. Use when nobody can say how long without a purchase counts as lapsed, win-back reaches people who just bought, or re-engagement never ends. Not a failed subscription charge (subscription-retention) or discount depth (offer-design).Votes: 0GitHub stars: 2
- List BuildingKnow where every contact record came from, which record wins when two disagree, and when a contact stops being worth keeping. Use when one person sits in the base several times, two sources disagree on a field, nobody knows what to collect, or you ask what base growth is normal. Not the capture form (onsite-capture) or segments (segmentation).Votes: 0GitHub stars: 2
- Loyalty Program DesignDesign what a loyalty program is made of, how its rules work, and what it costs. Use when choosing between a discount, a points currency and paid access, setting earn, burn, expiry and tiers, sizing a referral reward, or changing rules members were already promised. Not the rollout (loyalty-program-launch) or a one-off offer (offer-design).Votes: 0GitHub stars: 2
- Loyalty Program LaunchTake a loyalty program from a signed design to a running one, and get people into it. Use when deciding whether to launch at all, checking the design works at the till, sizing a pilot, rolling out by store, migrating members off an old program, or getting staff to ask. Not earn, burn, tiers or reward value (loyalty-program-design).Votes: 0GitHub stars: 2
- Martech StackDecide which system owns each fact, how fresh events are, and how to change platforms without losing the program. Use when two systems disagree on a customer, a segment stops filling though nobody changed it, events reach a trigger late, or a platform move is planned. Not segment design (segmentation) or trigger design (triggered-messages).Votes: 0GitHub stars: 2
- Messaging ChannelsRun SMS, RCS, WhatsApp and similar channels where a carrier or platform stands between you and the person. Use when choosing the sending number, a template needs approval or gets paused, an order update and a promotion share one number, STOP must work everywhere, or sends are billed per segment. Not the conversation after a reply (chat-and-bots).Votes: 0GitHub stars: 2
- Metric DefinitionsWrite down what a metric is, so two people quoting it mean the same thing. Use when two dashboards or teams disagree, a metric is about to become a target, its numerator, denominator and window are unwritten, or it needs a baseline from your own periods. Not the report (crm-reporting) or whether a difference is real (experiments-and-holdouts).Votes: 0GitHub stars: 2
- Offer DesignDecide what you promise for a purchase, from the form and depth of the benefit to its terms, and what happens when offers stack. Use when a discount is decided before anyone sets its depth, a code leaks, or two promotions stack into a loss. Not a loyalty program (loyalty-program-design) or the promotional calendar (promo-calendar).Votes: 0GitHub stars: 2
- Onsite CaptureTurn anonymous site visitors into contacts you may write to, and decide what to ask and give. Use when placing or auditing pop-ups, forms and quizzes, setting when a widget may appear, fixing overlays that pile up, or asking what pop-up conversion is normal. Not the welcome series (welcome-and-activation) or consent (consent-and-preferences).Votes: 0GitHub stars: 2
- PersonalizationDecide what changes in a message or page from person to person, where each value comes from, and what shows when it is missing. Use when a greeting ships with an empty name, a recommendation block shows everybody the same items, or a block varies by person. Not who receives it (segmentation) or the words (email-copy).Votes: 0GitHub stars: 2
- Program Audit And OpsNotice when something you launched has stopped working, respond, and decide what keeps running. Use when a flow goes quiet, a send goes out twice or to the wrong list, an export stops refreshing, a promo pool runs dry, or a metric sags for no clear reason. Not flow design (triggered-messages) or proof a change worked (experiments-and-holdouts).Votes: 0GitHub stars: 2
- Promo CalendarPlan what runs when across the year, and what a peak does to the weeks around it. Use when building the promotional calendar, deciding which occasions earn a place, running a peak window, keeping sales apart, or explaining why a sale that looked good left the year smaller. Not discount depth (offer-design) or the cap (contact-orchestration).Votes: 0GitHub stars: 2
- Push NotificationsDecide who can be reached by push, through which endpoint, and what each send costs the permission. Use when planning when to ask for notification permission, opt-in looks fine but reach keeps shrinking, people switch notifications off unnoticed, or one promo lights up every device. Not in-app messages (in-product-messaging).Votes: 0GitHub stars: 2
- Repeat PurchaseWork out when the next purchase is due, move first-time buyers to a second order, and decide what goes with an order. Use when a replenishment reminder arrives after the customer restocked, nobody knows where its date comes from, or first-time buyers get nothing after welcome. Not the trigger (triggered-messages) or win-back (lapse-and-winback).Votes: 0GitHub stars: 2
- Rfm SegmentsCut the base by recency, frequency and money on your own distribution, and collapse the grid into groups a team can work. Use when handed a big RFM table and asked which cells to message, when placing a band boundary, or when many customers have no purchase history. Not the choice of attribute (segmentation).Votes: 0GitHub stars: 2
- Scenario MapDecide which mechanics the program runs at all, which gets built first, and which leaves. Use when nobody can list what is running, someone hands you an industry list of scenarios to launch, or a new flow asks for a slot. Not the program's goal and owners (crm-program-design) or monitoring what runs (program-audit-and-ops).Votes: 0GitHub stars: 2
- SegmentationCut a customer base into segments that hold up in use and that someone else can reproduce. Use when choosing the attribute to split on, writing a segment definition, sizing a segment, setting how often it recomputes, resolving overlaps, or handling everyone left over. Not RFM bands (rfm-segments) or what changes inside a message (personalization).Votes: 0GitHub stars: 2
- Subscription RetentionKeep a paid subscription from ending over a failed charge, and end it cleanly when the person cancels. Use when a renewal charge fails and nobody knows the retry window or access, the cancel screen hides the button behind a discount, or a pause never resumes. Not win-back after a lapse (lapse-and-winback) or invoiced contracts (b2b-retention).Votes: 0GitHub stars: 2
- Transactional MessagingDecide which service messages an order, booking, payment or account request sets off, what each contains, and how fast it arrives. Use when people keep asking where their order is, a delay notice comes late, or someone wants a cross-sell in the confirmation. Not marketing event flows (triggered-messages) or the cap (contact-orchestration).Votes: 0GitHub stars: 2
- Triggered MessagesBuild flows fired by a customer event such as an abandoned cart, a browsed product, back in stock, a price drop or a birthday. Use when choosing which events deserve a message, setting the delay, the exit and the cascade, or untangling flows that collide. Not order and account notices (transactional-messaging) or welcome (welcome-and-activation).Votes: 0GitHub stars: 2
- Voice Of CustomerAsk customers about an experience, route what they say to an owner, and act on it. Use when setting up a post-purchase, post-delivery or post-cancellation survey, a low score arrives and nobody owns it, or nobody can tell whether a change customers asked for worked. Not the score's formula (metric-definitions) or product research.Votes: 0GitHub stars: 2
- Welcome And ActivationRun the first weeks after someone arrives, from the recorded contact to a first purchase or first use of the product. Use when a signup gets no messages, one welcome series serves many entry points, a trial ends unused, or nobody owns a contact after welcome. Not the capture form (onsite-capture) or the second purchase (repeat-purchase).Votes: 0GitHub stars: 2