Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.
MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) that users can annotate and provide feedback on, using the lavish-axi CLI. Use when preparing a plan, comparison, diagram, table, code diff, report, or anything easier to understand visually than as prose.
Create a local decision knowledge project for business, relationships, health, career, learning, or investment topics that need long-term tracking. Use when the user asks to open a decision case, record outcomes, build a status profile, or conduct a long-term review.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Run a macro, periodic review of the full RevOps/GTM tool stack against the revenue workflows it serves and decide, tool by tool, what to keep, consolidate, replace, or cut - four-channel inventory, function-level overlap map, TIME scoring, a renewal-triggered action calendar, and re-sprawl governance. Use whenever the user mentions stack rationalization, GTM tool consolidation, a revops stack audit, a GTM stack review, SaaS sprawl, too many sales and marketing tools, cutting tooling spend, redundant GTM tools, or platform vs point solutions - even if they never say "rationalization". Covers B2B sales-led and B2C/e-commerce GTM stacks. Portfolio-level and periodic - not a pre-purchase checklist for one candidate tool, and not contract or legal negotiation.
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.
Design the sales-to-CS handoff process after a deal closes - what data transfers, when, in what artifact, and who is accountable - producing a handoff spec with a gated closed-won trigger, a required handoff packet, timing SLAs, a kickoff meeting pattern, and a CS acceptance/rejection step. For RevOps and Sales Ops designing and enforcing the process, not a CSM running one handoff. Use whenever the user mentions sales to CS handoff, post-close transition, closed-won to kickoff, handoff accountability, "the CSM starts from zero", or "customers repeat themselves after signing" - even if they never say "handoff". Covers B2B high-touch through PLG/self-serve and B2C subscription. Do NOT use for account health scoring - use mbfinotti/revops-skills@customer-health-score instead.
Design, validate, and recalibrate a lead scoring model - fit and engagement signals, weighting, negative scoring and exclusions, decay, MQL/PQL threshold and tier setting, backtesting against closed-won/closed-lost outcomes, and governance; also diagnoses an existing broken model. Use whenever the user mentions lead scoring, an MQL threshold, fit vs engagement scoring, product-qualified leads, score decay, "score my leads", "our lead scores are wrong", "sales rejects our MQLs", or "too many junk MQLs" - even if they never say "scoring model". Covers B2B sales-led and B2C/PLG, rules-based design and predictive readiness. Do NOT use for assigning scored leads to reps - use mbfinotti/revops-skills@lead-routing instead.
Design, validate, and govern a composite customer health score: product usage and engagement signals combined into one weighted, normalized, decayed, banded account score that flags both churn risk and expansion readiness, backtested against real churn outcomes and recalibrated. Use whenever the user mentions a customer health score, health scoring model, account health, signal weighting, score bands, at-risk account flagging, churn risk score, expansion risk, or says “green accounts keep churning”—even if they never say “health score.” Covers B2B account-level rollup and B2C/PLG continuous scoring. Do NOT use for discovering which indicators actually predict churn—use mbfinotti/revops-skills@customer-churn-signals instead
Design the assignment logic that routes inbound leads to sales reps: rule precedence and waterfall ordering, lead-to-account matching, territory assignment rules (geography, segment, industry, named accounts), round-robin variants (straight, weighted, capacity-based, availability-aware), fallback catch-all queues, SLA escalation and reassignment, and safe rollout of routing changes. Use whenever the user mentions lead routing, lead assignment, territory assignment, round-robin, lead distribution, “who gets this lead,” a lopsided round-robin, or leads sitting unworked in a CRM queue—even if they never say “routing.” Covers B2B account-based and B2C/PLG high-volume routing. Do NOT use for designing the lead score itself—use mbfinotti/revops-skills@lead-scoring instead
Turn a campaign goal and an audience insight into a structured creative brief a designer, video editor, or UGC creator can execute—messaging angle, hook directions, art direction, specs, testing intent, and the handoff and revision loop. Covers B2B and B2C, with variants for static image, short-form video/UGC, and search/responsive text ads. Use whenever the user needs to brief a designer or creator, asks what an ad should say, or mentions messaging pillars, creative direction, or a design handoff—even if they never say “brief”. Writes direction, never the finished asset: the ad copy itself is mbfinotti/advertising-skills@ad-copy-variants and shot-by-shot creator scripts are mbfinotti/advertising-skills@ugc-ad-scripts.
Design the deal desk approval chain and exception-handling process for non-standard B2B SaaS deals - a tiered discount approval matrix and delegation of authority across five concession levers (price, payment terms, services, contract risk, security), margin floor policy, exception intake, two SLA clocks with a sales escalation path, and precedent control. Includes the rules-driven promo/discount-policy equivalent for PLG, self-serve, and B2C. Use whenever the user mentions deal desk, discount approval, quote approval, approval matrix, delegation of authority, non-standard deals, concessions, margin floors, or discount creep - even if they never say "deal desk". Covers deal-level commercial approvals only, not general business-process approval workflows.
Define the metric set and narrative structure for an executive or board revenue report so it tells one coherent story—a small stable metric spine, locked definitions, an answer-first narrative around plan vs actual vs forecast, presenting a miss without surprising the board, the reconciliation and sign-off chain, and weekly vs monthly vs quarterly cadences. Use whenever the user mentions a board revenue report, exec deck metrics, the QBR revenue section, a monthly revenue review, an investor update, or a board deck that reads as a data dump—even if they never say “reporting”. Covers B2B subscription, B2C, transactional, usage-based, and PLG. Do NOT use for designing the org-level KPI hierarchy—use mbfinotti/revops-skills@revenue-kpi-framework instead.
Design a pre-launch ad creative test plan—falsifiable hypothesis, isolation level, test cells with per-cell budgets, required sample, spend and duration, and kill/scale rules pre-registered before any money moves. Every cell carries an explicit read standard, so an underpowered screen is never dressed up as an A/B test. Use whenever the user wants to test ads, mentions an A/B or split test on creative, asks how much budget or how long a test needs, or mentions sample size, statistical significance, single-variable vs big-swing testing, or test cell structure—even if they never say “test plan”. Covers B2B and B2C. Do NOT use to read results from a test already running—use mbfinotti/advertising-skills@ad-creative-fatigue instead.
Diagnose the root cause of an underperforming paid ad account - why the ads stopped working, why CPA went up, why ROAS dropped - instead of defaulting to 'increase the budget'. Weighs tracking, account structure, targeting, creative, bidding and budget, offer, and external forces, and returns a prioritised verdict with evidence and confidence. Covers B2B and B2C on search, paid social, video, and native. Use whenever the user mentions an ad account audit, a campaign structure review, wasted ad spend, rising cost per lead, or says their ads used to work - even if they never say 'diagnostic'. Diagnosis only, and it stops at the click: post-click page problems are mbfinotti/advertising-skills@paid-landing-page-audit and creative decay is mbfinotti/advertising-skills@ad-creative-fatigue.
Decide whether a running ad creative is genuinely wearing out, or whether a confounder - budget change, learning-phase reset, audience saturation, auction CPM inflation, seasonality, tracking breakage - explains the decline, and return a verdict with confidence plus the highest-return remedy per unit of effort. Use whenever the user mentions creative or ad fatigue, wear-out, climbing frequency, dropping CTR, a rising CPA on an older ad, when to refresh creative, or whether to kill an ad - even if they never say 'fatigue'. Covers B2B and B2C across search, social, video, and native. Ends at the verdict: replacement creative belongs to mbfinotti/advertising-skills@ad-copy-variants and mbfinotti/advertising-skills@ugc-ad-scripts.
Assemble, define, validate, and rank leading indicators of customer churn from account activity, product usage, and support data into a ranked churn signal register—each signal includes an event, threshold, window, baseline, lift over base rate, lead time, and coverage. Use whenever the user mentions churn signals, churn indicators, leading indicators of churn, an early warning system for at-risk accounts, champion departure, seat utilisation drops, payment failure, or says “our health score misses churn”—even if they never say “signal.” Covers B2B and B2C subscription. Do NOT use for combining signals into one composite score, weights, bands, or tiers—use mbfinotti/revops-skills@customer-health-score instead
Verify that conversion events are correctly configured, firing once, and deduplicated before a paid campaign launches, then turn the evidence into a GO / NO-GO decision. Covers tag debugging, test conversion tracing, browser/server event deduplication (including Conversions API setups), value and currency checks, conversion action status, consent handling, and test-data exclusion. Use whenever the user asks if their tracking works, mentions a pixel or tag check, conversions not showing up, duplicate conversions, or a pre-launch checklist—even if they never say “conversion tracking”. Covers B2B lead gen and B2C ecommerce on any ad platform. Do NOT use to reconcile platform vs CRM numbers after launch—use mbfinotti/advertising-skills@ad-attribution-gap instead.
Build and maintain a competitor swipe file - competitors' currently-running ads collected into a categorised, queryable library classified by format, hook type, offer/angle, awareness stage, and funnel stage, then converted into ranked creative test hypotheses. Accepts pasted ad text, described ads, screenshots, export files, or public ad transparency libraries. Use whenever the user asks what ads competitors are running, wants a competitor ad teardown, creative inspiration, or to know what is working in their category - even if they never say 'swipe file'. Covers B2B and B2C on any paid channel. Stops at ranked hypotheses: briefing is mbfinotti/advertising-skills@ad-creative-brief and test design is mbfinotti/advertising-skills@ad-creative-test-plan.
Set the organisation's top-level paid-media spend guardrails as written policy - maximum allowable CAC, minimum ROAS/MER floor, kill-switch thresholds, counter-metrics, who owns them and who may override them - each derived from contribution margin, payback, and cash runway rather than inherited from a dashboard. Use whenever the user asks what CAC they can afford, mentions a ROAS floor, spend guardrails, a kill switch, when to stop spending, or who approves a budget increase - even if they never say 'guardrails'. Covers B2B and B2C. Do NOT use to judge whether current CAC/ROAS is actually good (mbfinotti/advertising-skills@cac-roas-benchmark) or to monitor daily pacing (mbfinotti/advertising-skills@ad-budget-pacing).
Turn a business's ICP and buying signals into a layered ad audience targeting plan—cold/broad prospecting, interest and in-market behavioural segments, lookalike/similar, first-party lists, and retargeting pools—each sized against platform audience floors, budgeted to the learning threshold, and kept from overlapping by exclusion rules. Use whenever the user mentions ad targeting, who to target with ads, audience tiers or layers, broad vs. layered targeting, audience overlap between campaigns, or mapping an ICP onto ad audiences—even if they never say “audience”. Covers B2B and B2C. Do NOT use to pick the seed customers behind a lookalike (mbfinotti/advertising-skills@lookalike-audience-seeds) or to sequence retargeting messages (mbfinotti/advertising-skills@retargeting-funnel).
Audit a landing page receiving paid traffic against post-click conversion best practice and return a prioritised fix list—message match to the ad, above-the-fold clarity, form friction, trust, speed, mobile, policy risk—with every finding labelled by evidence class and no statistical claims on thin data. Use whenever the user says their ads get clicks but no conversions, asks why a landing page isn't converting, or mentions post-click experience, message match, conversion friction, form friction, or CPA rising after the click—even if they never say “landing page audit”. Covers B2B and B2C on any platform. Audit only. Do NOT use for pre-click account problems—use mbfinotti/advertising-skills@ad-account-diagnostic instead.
Decide when a proven paid campaign has earned a budget increase, how large each step should be, how the ramp sequences over weeks and months, and how to avoid performance collapse on the way up—including readiness gates, vertical vs horizontal scaling, and rollback triggers. Use whenever the user asks whether to scale a campaign, how fast ad spend can rise, mentions a budget ramp, a scaling ceiling, or says performance collapsed after the budget was raised—even if they never say “scaling”. Covers B2B and B2C. Do NOT use to split a fixed total across campaigns (mbfinotti/advertising-skills@ad-spend-allocation) or to track daily spend against a set budget (mbfinotti/advertising-skills@ad-budget-pacing).
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app—not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes
Split a fixed total paid-media budget across campaigns, platforms, funnel stages, and audiences based on expected marginal return - the monthly or quarterly reallocation decision, for B2B and B2C. Use whenever the user asks how to split an ad budget, which channel or campaign should get more money, how to reallocate spend, how much to put behind prospecting vs retargeting, or mentions a portfolio split, marginal return, or diminishing returns - even if they never say 'allocation'. Do NOT use to raise the total budget on a proven campaign (mbfinotti/advertising-skills@paid-media-scaling), to track daily spend against a set budget (mbfinotti/advertising-skills@ad-budget-pacing), or to pick channels at setup (mbfinotti/advertising-skills@ad-platform-selection).
Track daily and weekly spend against a single campaign or account budget and flag under-pacing or over-pacing before it hurts results, reporting the pacing ratio, projected period spend, and the corrective daily spend behind every alert. Use whenever the user mentions budget pacing, spend tracking, burn rate, spend vs budget, projected month-end spend, underspending or overspending, or asks whether a campaign is on pace - even if they never say 'pacing'. Covers any ad platform, B2B and B2C, calendar-month or fixed-date flights. It flags and recommends; it never changes budgets or bids. Do NOT use to plan a scale-up (mbfinotti/advertising-skills@paid-media-scaling) or to set CAC/ROAS thresholds (mbfinotti/advertising-skills@ad-spend-guardrails).
Select and size the seed customer list behind a lookalike, similar, or value-based audience—which customers to upload, how many, and whether the matched count (not the row count) clears the platform floor—with RFM and value-based selection, a negative-selection pass, a privacy and consent gate before any customer list upload, and a fallback ladder when the floor cannot be cleared. Use whenever the user mentions a lookalike or similar audience, a seed list, a customer list upload, match rate, an audience that is too small, or says their lookalike isn't working—even if they never say “seed”. Covers B2B and B2C. Do NOT use to design the whole targeting tier structure—use mbfinotti/advertising-skills@ad-audience-targeting instead.
Build and maintain negative keyword lists from search term reports to cut wasted ad spend in paid search—n-gram query mining to surface irrelevant search terms, the right negative match types and exclusion levels (account, shared list, campaign, ad group), and a review cadence that avoids overblocking queries that convert. Use whenever the user mentions a search term or search query report, irrelevant clicks, junk traffic, wasted ad spend, or wants to exclude or block keywords—even if they never say “negative keywords”. Covers B2B lead gen and B2C/e-commerce; needs the account's query data. Do NOT use for account-wide underperformance with no query-level evidence—use mbfinotti/advertising-skills@ad-account-diagnostic instead.
Compute a business's CAC and ROAS family metrics from real spend and outcome data, then judge whether the spend is healthy against three references— the business's own break-even, its own trailing history, and provenance-labelled external benchmarks—returning healthy, watch, unhealthy, or insufficient evidence. Use whenever the user asks whether their CAC is too high, whether a ROAS is good, what ROAS to aim for, whether ads are profitable, or mentions MER, blended CAC, payback period, or a spend health check—even if they never say “benchmark”. Covers B2B/SaaS (cost per SQL, cost per closed-won, cohort lag) and B2C/ecommerce. Do NOT use to set those thresholds as policy—use mbfinotti/advertising-skills@ad-spend-guardrails instead.
Before starting any paid advertising work, before each recurring advertising review, and whenever routing is unclear, route the task to the right skill of the advertising-skills collection—or say plainly that none fits—and bootstrap or resume the project's shared context artifact. Use at every advertising project start, on later sessions of the same project to re-route without re-interviewing, and whenever the user mentions a new ad campaign or paid media project, asks which advertising skill they need, or wants a periodic advertising check-in—even if they name no skill at all. Prefer this whenever several skills could apply, since the collection has three colliding clusters—the hirer-vs-candidate pair, the budget cluster, the creative cluster—and it returns a short-list plus an ordered skill chain rather than a single guess. Do NOT use when the task already maps cleanly to one skill, such as a pure account audit—that is mbfinotti/advertising-skills@ad-account-diagnostic.
Decide which paid channel families fit a business's economics, audience, funnel stage, and budget at campaign setup—paid search, paid social, short-form video, connected TV, native/discovery, retail media, programmatic display, podcast/audio, paid review listings, B2B professional networks—including whether each is affordable against allowable CAC and payback. Use whenever the user asks where to spend a new ad budget, which platform to advertise on, how to build a paid channel mix, whether a channel is worth trying, or compares two ad channels—even if they never say “channel selection”. Covers B2B and B2C. Do NOT use to split an ongoing budget across existing campaigns—use mbfinotti/advertising-skills@ad-spend-allocation instead.
Build the complete hiring packet for a paid-advertising role—the rung decision (media buyer vs performance marketer vs growth marketer; creative strategist is its own role), an outcome scorecard, a 2-3 round interview loop with a judgment-first question bank, a time-boxed in-interview work sample, and a 30-60-90 ramp with staged spend authority. For the marketing leader or founder recruiting. Use for “hire a media buyer”, “interview questions for a performance marketer”, “paid media work sample”, “scorecard for our first ad hire”, or “30-60-90 for a new paid media hire”. Does not source candidates, post jobs, run applicant tracking, or write offers, and does not cover the candidate side—that is the sibling mbfinotti/advertising-skills@advertising-career.
Quantify and explain the discrepancy between ad platform reporting, an analytics tool, and the source of truth (CRM or order system), classifying every unit of the gap as timing, definitional, or unexplained residual. Use whenever the user says the numbers don't match, that the platform reports more conversions or revenue than the CRM or order system, or mentions cross-platform reconciliation, double-counted conversions, an attribution discrepancy, or asks whether a reporting gap is normal—even if they never say “attribution”. Covers B2B (CRM-anchored) and B2C/ecommerce (order-system-anchored). Do NOT use to fix broken or missing tracking—use mbfinotti/advertising-skills@ad-conversion-tracking instead.
Design a multi-stage retargeting sequence from a site's own funnel data—recency windows and behavioural-depth tiers per stage, a message and offer ladder for each stage, mutually exclusive audiences with exclusion logic, and per-stage frequency caps. Use whenever the user mentions retargeting or remarketing, cart or form abandonment, how long a retargeting window should be, frequency caps, a retargeting audience that is too small, or ads still showing to people who already bought—even if they never say “funnel”. Covers B2B and B2C, and produces a stage-by-stage plan rather than campaigns built inside an ad platform. Do NOT use to design cold prospecting audience tiers—use mbfinotti/advertising-skills@ad-audience-targeting instead.
Build a personalised, time-budgeted watch list of paid-advertising information sources—PPC and paid-social podcasts, newsletters, ad-platform release notes, communities, industry events, and media buyers worth following—with a verification method that keeps it fresh and a disclosure of what each source is selling. Use whenever a media buyer, PPC specialist, or growth marketer asks how to stay current on Google Ads, Meta, LinkedIn, TikTok, or Microsoft Ads changes, which PPC newsletters or paid-social podcasts to follow, which communities or conferences deserve their time, or who to follow in performance marketing—even if they never say “radar”. Do NOT use for career planning—use mbfinotti/advertising-skills@advertising-career instead.
Plan and advance a paid-advertising career from the candidate side—media buyer, performance marketer, PPC specialist, creative strategist, growth marketer—covering the junior-to-lead ladder, the five real interview formats (live account audit, mental-maths case, metric diagnosis, take-home, behavioural), an NDA-safe results portfolio, platform certifications, in-house vs agency vs freelance, and promotion and pay conversations. Use whenever the user asks how to get into paid media or PPC, preps for a media-buyer or growth interview, wants an ad portfolio, or weighs an agency vs in-house move—even if they never say “career”. Do NOT use for the employer side of hiring—use mbfinotti/advertising-skills@advertising-hiring instead.
Map the likely buying committee for an offer, deal size, and industry, and give each role a messaging angle plus the ad-targeting proxy—job function and seniority, account list, account-level intent—that actually reaches them, sequenced by buying stage. Use whenever the user mentions a buying committee or buying group, decision makers, influencers or blockers, who signs off, targeting the economic buyer or a champion, per-role ad messaging, or whether one broad message beats per-role targeting—even if they never say “buying committee”. Covers B2B committees and multi-decider household purchases. Do NOT use to size or build the audiences themselves—use mbfinotti/advertising-skills@ad-audience-targeting instead.
MANDATORY recipe for every Caffeine build that lists upcoming events or creates events on the user's own Google Calendar. The ONLY supported path is the `googlecalendar-client` mops package (Calendar REST API v3) combined with the `google-oauth` mops package (token exchange + refresh + PKCE). Hand-rolling `ic.http_request` calls to `oauth2.googleapis.com` or `www.googleapis.com/calendar/v3` is a FORBIDDEN anti-pattern—it bypasses bearer auth, replication-cost safeguards, and the `google-oauth` library's percent-encoding and JSON parsing. Load this skill whenever the user, spec, or any prior task mentions scheduling, calendar events, appointments, meetings, “add to calendar,” or any equivalent phrasing—and BEFORE writing any code that touches a Google endpoint.
Choose the bidding policy per platform and goal - manual vs automated, cost-goal vs value/return-goal, when to switch, and how to set and move the target - written up as a policy with an evaluation window, change discipline, and a rollback trigger. Use whenever the user mentions a bid strategy, target CPA or target ROAS, smart or automated bidding, bid cap vs cost cap, portfolio bid strategies, seasonal bid adjustments, value-based bidding readiness, or delivery collapsing after a target change - even if they never say 'bidding'. Covers B2B and B2C. Do NOT use to split budgets across campaigns (mbfinotti/advertising-skills@ad-spend-allocation) or to track spend against a budget (mbfinotti/advertising-skills@ad-budget-pacing).
Score and force-rank the openings of candidate video ads — from a script, transcript, storyboard, shot list, or a description of a finished cut — to decide which hooks deserve test budget, returning a ranked shortlist within the batch rather than an absolute performance prediction. Use whenever the user mentions a hook, the first 3 seconds, an ad opening, hook rate, thumbstop, attention scoring, or asks which hook to test or whether a hook works — even if they never say 'hook analyzer'. Covers B2B and B2C on any platform. Ends at the ranking: writing the scripts themselves is mbfinotti/advertising-skills@ugc-ad-scripts and static copy is mbfinotti/advertising-skills@ad-copy-variants.
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity. Use when migrating or replatforming to Sanity from AEM, Adobe Experience Manager, Contentful, Strapi, Webflow, WordPress, Payload, Drupal, Markdown/MDX/frontmatter files, WXR/XML exports, CMS APIs, database dumps, static HTML, or when designing extraction, transformation, Portable Text conversion, asset migration, redirects, validation, and cutover workflows
Run an extremely strict maintainability review focused on abstraction quality, oversized files, and growth of spaghetti conditions. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Evaluate Expo skills in this repo end-to-end—trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify that its output renders correctly.
Turn a product brief and target audience into UGC-style short-form video ad scripts a creator can film — hook, body, CTA — with 3-5 hook variants per concept written as spoken line plus on-screen text plus opening visual, with delivery notes and disclosure lines. Use whenever the user asks for a UGC ad or creator script, a short-form vertical video ad script, a founder-led video, employee-generated content, or a customer testimonial video script — even if they never say 'UGC'. Covers B2C creator scripts and B2B formats. Do NOT use to score existing hooks (mbfinotti/advertising-skills@ad-hook-analyzer), to write static ad copy (mbfinotti/advertising-skills@ad-copy-variants), or to brief a designer (mbfinotti/advertising-skills@ad-creative-brief).
Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says “research,” “investigate,” “analyze in depth,” “compare X vs Y,” “what does the market look like for,” or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30–120 seconds. For quick fact-finding, use tavily-search instead
Deprecated alias. This skill was renamed to `deepline-research`. Use when a user or script still invokes `/deepline-pre-research`: immediately load and follow the `deepline-research` skill instead. Triggers: pre-research, source discovery, provider strategy, research data sources, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language.
Provides complete shadcn/ui component library patterns, including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns such as buttons, dialogs, dropdowns, tables, and complex form layouts.
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neondatabase/neon-js.
Flag ad formats that are a poor fit or commonly misused for a given objective and platform—formats the objective does not even expose, formats built for a different funnel stage, formats the team cannot produce—then, post-launch, separate a format problem from a creative or targeting problem. Use whenever the user asks which ad format to use, mentions carousel, Stories, in-feed vs in-stream video, a funnel-stage mismatch, a pre-launch format check, or says a format 'isn't working'—even if they never say 'format fit'. Covers B2B and B2C, with explicit launch blockers. Do NOT use to choose the channel itself (mbfinotti/advertising-skills@ad-platform-selection) or to brief the creative (mbfinotti/advertising-skills@ad-creative-brief).
Turn one core value proposition into genuinely distinct ad copy variants - headline, primary text, description, and CTA combinations - each labelled with angle, awareness stage, formula, and version so test results stay attributable. A real variant is a new angle, never a reworded line. Use whenever the user asks to write ad copy, needs headline or CTA variations, wants copy to A/B test, has ads that all sound the same, or needs a search ad headline set or an ML asset pool - even if they never say 'variants'. Covers B2B and B2C. Do NOT use for video or creator scripts (mbfinotti/advertising-skills@ugc-ad-scripts), a designer brief (mbfinotti/advertising-skills@ad-creative-brief), or test design (mbfinotti/advertising-skills@ad-creative-test-plan).
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.
