Marketing & Growth

autom8minds Bundle

Expert guide for Schema.org structured data and JSON-LD implementation. Use when creating schema markup, validating structured data, implementing rich results (FAQ, HowTo, Product, Article, LocalBusiness, Breadcrumb, Organization, etc.), troubleshooting rich snippet eligibility, or understanding Google's structured data requirements.

cbrunnkvist Bundle

Create or restructure high-consequence software documentation and technical marketing without mixing their standards. Use for API references, architecture guides, READMEs, CLI/setup/troubleshooting guides, DevRel posts, launch announcements, landing pages, positioning, and executive technical summaries.

theopenco Bundle

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

quionie Skill

Write, structure, or optimize blog posts with SEO best practices. Use this skill when the user wants to write a blog post, create an article, draft a long-form piece, optimize content for search engines, build a content outline, or needs help with blog structure. Also trigger when the user mentions "SEO", "blog", "article", "long-form content", "content outline", "meta description", "heading structure", or wants to turn an idea into a published piece.

quionie Skill

Design and write email sequences, drip campaigns, and automated email flows. Use this skill when the user wants to create a welcome sequence, onboarding emails, launch sequence, nurture campaign, re-engagement flow, abandoned cart emails, or any multi-email automated series. Also trigger when the user says "email sequence", "drip campaign", "email flow", "welcome series", "email automation", "nurture sequence", "launch emails", or wants to write a series of connected emails.

romainsimon Bundle

Splits scarce time, budget or traffic across competing products, channels, campaigns or variants by treating them as a multi-armed bandit - Thompson sampling over beta posteriors, with optimism for anything not yet tried enough to judge. Use when deciding what to work on next, how to divide a marketing budget, which product to prioritise, whether to kill something that is underperforming, or when picking a winner among test variants.

christopherswarup Skill

Design or audit a GTM/marketing measurement system using a metric-class ladder (Activity, Output, Outcome, Impact) applied at the right organisational level (Org, Programme, Function, Tactic-type, Tactic), so every metric on a dashboard is tied to an actual decision. Use whenever a user is building a reporting dashboard, defining KPIs, auditing an existing report before it goes to leadership, or asks why metrics "look fine but nothing changes." Trigger this whenever a metric or dashboard is proposed without a stated decision it drives, or when Activity-level numbers (clicks, opens, follows) are being presented as if they proved business Impact.

christopherswarup Skill

Classify the origin of market demand for a product, offer, or segment — Dormant (market doesn't know it has the problem), Substitution (market solves it today with an inferior approach), or Active-Category (established, budgeted, actively shopping) — before setting messaging, campaign strategy, or lead-qualification thresholds. Use whenever a user is writing GTM messaging, designing a campaign, setting MQL/lead-scoring criteria, launching into a new segment, or asks why "more leads" or "more MQLs" isn't fixing a pipeline problem. Trigger this proactively whenever someone proposes lead-volume as a fix without having stated the demand type — misclassifying this is the single most common cause of GTM strategies that generate activity without revenue.

christopherswarup Skill

Build a defensible target-account or ABM list using a two-gate screen — first a market/segment attractiveness-and-readiness screen, then an account-level scoring screen — instead of jumping straight to naming accounts. Use whenever a user is building an ABM program, a target account list, a territory plan, or prioritizing which segments/accounts to pursue with sales or marketing effort. Trigger this whenever someone proposes an account list, a "who should we target" question, or an ABM program without first having screened the market/segment level — an account list built without that screen inherits "who could buy" waste that no amount of account-level scoring fixes afterward.

christopherswarup Skill

GTM Diagnostic Orchestrator

christopherswarup Skill

Diagnose or defend marketing's value across every audience it actually serves — buyers, existing customers, sales, product, executives, employees, and partners/influencers — not pipeline alone. Use whenever a user is defending a marketing budget, writing a marketing strategy or business case, responding to "what does marketing actually do," or planning marketing's role in a broader GTM motion. Trigger this whenever marketing's contribution is being evaluated using pipeline/lead metrics alone — that framing systematically undercounts real value and produces bad budget and headcount decisions.

guiloureiromkt Bundle

Audita um site inteiro em GEO (ser citado por ChatGPT/Perplexity/Gemini/Claude), SEO (técnico + conteúdo), MEDIÇÃO (Google Analytics instalado? formulário entrega o lead ou finge enviar?) e review de código — e RE-RODA em loop corrigindo até bater a nota-alvo, guiando o dono do site (mesmo leigo) a criar conta de Analytics e Search Console. Use SEMPRE que pedirem "audita o site X", "roda a auditoria no site", "checa o SEO/GEO de <domínio>", "meu site não aparece no ChatGPT", "por que não ranqueio", "review de código do site", "melhora a pontuação do site", "o site tem texto de outra marca / sobrou coisa do template", "o site pede chave de API", "meu site tem Google Analytics?", "o formulário está funcionando?", "não chega lead pelo site", "como instalo o Search Console", ou quando um site acabou de ser construído/entregue e precisa passar no crivo antes de virar oficial. Serve site NO AR (URL), pasta estática local e repositório (Next.js, Astro, WordPress, HTML puro — agnóstico de stack), com checks específic

guiloureiromkt Bundle

Entrevista guiada de diagnóstico de negócio em 3 fases. Use sempre que o usuário quiser descobrir o que trava o crescimento do negócio dele (ou de um cliente), disser "diagnóstico do meu negócio", "audita meu marketing", "por que não estou crescendo", "o que testar primeiro", "monta um diagnóstico", "hipóteses pra testar", ou compartilhar o contexto de uma empresa pedindo análise. Conduz uma entrevista em 6 dimensões (Negócio Real · Problema · Concorrência · Histórico · Dados · Objetivos Não-Ditos), destila tudo em 5-8 hipóteses testáveis (formato "Se X, então Y, verificado por Z"), prioriza da 1 à 4 (o que testar primeiro) e entrega um plano de verificação por semanas.

hameddk Bundle

Use when auditing the context-size, token-budget, or latency of ANY repository from its docs/ folder and its Claude Code session transcripts — questions like "how big is our docs corpus", "why are sessions on this repo getting slow or expensive", corpus growth, giant-doc tail, onboarding read-amplification, or context-vs-latency. Read-only; produces a measured report. For an agent-playbook role/skill static-load audit, pair with token-playbook-calculation.

harzva Bundle

Design and rewrite polished GitHub README homepages for repositories and profile READMEs, especially Chinese/English open-source projects. Use when the user asks to beautify, redesign, improve, package, market, add a README logo or wordmark, or make a README more professional, visual, persuasive, scannable, or GitHub Pages-like. Focus on README aesthetics, layout, badges, screenshots, logo/wordmark identity, project positioning, information architecture, and Markdown/HTML that renders well on GitHub.

iamursky Bundle

Redigiert und verbessert deutschsprachige Geschäfts- und Fachtexte nach den Prinzipien des Informationsstils — einem leserzentrierten Redaktionsansatz von Maxim Iljachow. Aktiviert sich, wenn der Nutzer einen Geschäftstext bearbeiten, prüfen, kürzen oder verbessern lassen möchte: E-Mails, Landingpages, Unternehmensbeschreibungen, Pressemitteilungen, Lebensläufe, Anschreiben, Berichte, Präsentationen, Kaltakquise-Mails, Social-Media-Texte. Wird ebenfalls ausgelöst durch Stichworte wie „Informationsstil", „Iljachow", „Ilyahov", „Glavred", „Füllwörter", „Floskeln", „Behördendeutsch", „Nominalstil", „Denglisch", oder bei Bitten wie „mach den Text knackiger", „bring das auf den Punkt", „in einfache Sprache übersetzen", „Marketing-Sprech rausnehmen". Funktioniert sowohl für komplette Überarbeitungen als auch für gezieltes Feedback ohne Umschreiben. Kann auf russische oder englische Texte angewandt werden, wenn der Nutzer das ausdrücklich wünscht.

ilexlyu Bundle

广告提案交付质检与复盘 Skill。Use when a proposal, PPT outline, deck draft, campaign plan, strategy document, or client pitch is ready for review, QA, final delivery, or post-project learning. It checks logic, sources, page clarity, risk, client fit, and extracts reusable assets, customer preferences, and future Skills from the project.

ilexlyu Bundle

广告创意方法论 Skill。Use when the user already has a strategic insight, proposition, product angle, brand POV, or campaign strategy and needs to translate that strategy into persuasive creative expression, campaign territories, customer-facing narratives, platform content angles, or big idea candidates. It uses institution-style thinking lenses including Ogilvy/Deck of Brilliance, Hua & Hua, McKinsey, and Mountains public narrative, rather than generic brainstorming.

ilexlyu Bundle

广告策略洞察生成与评审 Skill。Use when research materials, fact tables, consumer data, competitor notes, or client inputs are ready and the user needs strategic insights, POVs, campaign angles, pitch strategy, or a judged Top 3 insight set. It turns facts into opinionated strategic statements with evidence, counterarguments, fit, and action implications.

ilexlyu Bundle

广告提案结构与客户叙事 Skill。Use when strategy insights and creative directions exist and the user needs a client-ready pitch structure, PPT outline, slide-by-slide proposal logic, executive summary, talk track, or persuasive narrative for marketing, branding, ecommerce, social, or campaign proposals. It turns scattered ideas into a deck flow that a client can understand and buy.

ilexlyu Bundle

广告提案行业资料搜集 Skill。Use when the user needs research for an advertising proposal, pitch deck, brand strategy, ecommerce proposal, campaign plan, consumer insight, competitor scan, industry trend, platform ecosystem, or PPT evidence base. It searches authoritative report sources first, builds a cited material table, records source quality and year limits, and prepares facts for insight generation.

ilexlyu Bundle

面向策略、创意、内容与品牌团队的广告提案执行总控 Skill。Use when the user provides an advertising, marketing, branding, ecommerce, social campaign, launch, or client brief and wants a proposal, pitch deck, campaign plan, workflow, or review. Diagnose the assignment, route dynamically across research, insight, creative, narrative, visual, and delivery review, execute available stages, preserve evidence and assumptions, validate each handoff, and continue to the requested deliverable unless a material blocker requires user input.

ezzatmakar Bundle

Run a developer-focused technical SEO and GEO (Generative Engine Optimization) audit on a live website or a codebase, and produce one per-page README report — covering crawlability, indexability, rendering/SSR, Core Web Vitals, structured data, metadata, semantic HTML, redirects/HTTP, AI-crawler access and llms.txt — with every finding rated by severity and carrying a concrete code-level fix. Use when asked to audit SEO, check technical SEO, run an SEO health check, audit AI/LLM visibility, GEO, generative engine optimization, answer engine optimization, Core Web Vitals, render-blocking, indexability, crawlability, structured data, or "why isn't this page ranking / showing up in AI answers." Technical only — do not use for content, keyword, or editorial advice.

fern-api Skill

File a structured bug report during the Fern marketing site testing session. Use this whenever a tester says "I found a bug", "file a bug", "report this issue", "log a defect", or runs /file-bug. Walks the tester through capturing repro steps, expected vs. observed behavior, optional screenshot, then writes a JSON report under `testing/bugs/<tester>/<slug>.json`, copies the screenshot into `testing/screenshots/<tester>/<slug>.png`, commits, and pushes.

fern-api Bundle

Draft a new Fern blog post. Use whenever the user says "write a post", "draft a blog post", "/write-post", "new blog about X", or asks for a blog-length piece for buildwithfern.com. Produces an MDX file under content/blog/<slug>.mdx with valid frontmatter, applies the Fern marketing voice from AGENTS.md by default, and stops short of committing. Only applies Kapil's voice when explicitly requested.

fern-api Skill

Scaffold a paid acquisition campaign for a Fern landing page under `campaigns/<slug>/`. Use whenever the user says "create a campaign for X", "launch a campaign on /lp/X", "spin up paid ads for X", or "/launch-campaign". Mirrors the leave-stainless / agent-ready / fern-vs-speakeasy structure with brief, LinkedIn + Google copy, creative briefs in the Hiroshi Yoshida house style, results scaffolding, and a prefix entry in `campaigns/README.md`. Stops short of committing.

fern-api Skill

Edit and improve SEO blog posts. Use this skill ONLY when the user says "SEO blog post" / "SEO blog", or asks to edit or review an SEO post. Do NOT trigger for general blog editing, Fern marketing blog posts, or other writing tasks. Typical triggers: "edit this SEO post", "review this SEO blog", "edit this SEO blog post".

fern-api Skill

Write a new SEO blog post from the top idea in the SEO ideas queue (seo/ideas.mdx). Use this skill ONLY when the user wants to write an SEO blog post, e.g. "write an SEO blog post", "write the next SEO post", "draft the next SEO blog", "draft an SEO post", or "/seo-blog-writer". This skill WRITES the first draft; the separate seo-blog-editor skill edits it afterward. Do NOT trigger for general blog writing, Fern marketing blog posts (use write-post), case studies, or other writing tasks.

fern-api Skill

Write customer case studies for Fern (a Postman company). Use this skill when the user asks to draft, write, or edit a case study, customer story, or customer success story for Fern. Triggers include: "case study", "customer story", "write up this customer", "draft a case study from these notes", or any request to turn interview notes or customer data into a structured case study. Also use when the user provides raw interview notes and asks to turn them into a publishable piece. Do NOT use for blog posts, changelog entries, LinkedIn posts, or general marketing copy.

fern-api Skill

Write employee profile blog posts for Fern (a Postman company), specifically with a "customer to employee/contributor" framing. Use this skill when the user asks to draft, write, or edit an employee profile, team profile, team spotlight, or "meet the team" post for Fern's blog. Triggers include: "employee profile", "team profile", "write up this person", "draft a profile from these notes", "customer to employee", "customer turned engineer", or any request to turn interview notes about a Fern team member into a publishable blog post. Also use when the user provides raw interview transcripts or meeting notes about a Fern employee and asks to turn them into a blog post or profile. Do NOT use for case studies, changelog entries, LinkedIn posts, or general marketing copy.

imraywang Bundle

把一个已经写好的落地页 / 官网 / B2B 询盘站从"代码就绪"带到"线上可访问、SEO 就绪、数据流通、可交接"。先按"谁长期维护"选技术路线(纯静态 / headless CMS+前端 / 全栈),再走一份带真实静默失败坑位的上线 checklist:Vercel 部署、域名 DNS 切换、ISR/revalidate 数据流、SEO metadata、表单询盘链路,直到真机验证通过并交接给客户。当用户要把站上线、部署 Next 到 Vercel、接 headless WordPress/CMS、做上线前检查、切换域名、或问"这个站能不能发了"时使用。触发:/ray-launch 「项目路径或站点类型」。不用于:本地开发调试与写业务代码、纯后端服务/API 部署(那更接近 /ray-vps)、内容创作或选题。

itallstartedwithaidea Skill

ALWAYS load this skill at the start of ANY advertising-related conversation. This skill ensures MiniAgent's specialized skills are used instead of generic responses. Trigger for ANY mention of: Google Ads, Meta Ads, Microsoft Ads, Amazon Ads, advertising, PPC, paid media, ad spend, campaign, ROAS, CPA, impressions, clicks, conversions, keywords, bidding, budget, Quality Score, or any advertising platform.

itallstartedwithaidea Skill

Use when ANY Google Ads data needs to be analyzed — campaign performance, keyword analysis, Quality Score review, budget pacing, search term reports, auction insights, impression share, or when the user mentions Google Ads metrics, ROAS, CPA, CTR, impressions, clicks, conversions, cost_micros, GAQL, or ad performance in any context. Also trigger when discussing PPC strategy, account structure, advertising performance, ad spend, bid strategy, or campaign optimization. If the user has a Google Ads account or mentions any advertising platform, this skill should activate.

itallstartedwithaidea Skill

Use for complete, end-to-end advertising workflows that span multiple skills — full account audits with action plans, campaign launches with verification, optimization cycles, or any multi-step advertising process. Trigger when the task requires analysis AND changes AND verification, or when the user wants a complete workflow rather than a single answer.

jcosta33 Skill

Write or revise a restartable goal contract for one multi-pull-request delivery campaign. Use when one durable objective needs dependency-aware, write-disjoint streams, a project-native progress ledger, and enforceable delivery gates. Do not use when the goal completes in one pull request, or when the user asks only for a plan artifact.

jcosta33 Skill

Research a decision until evidence can carry it. Use when comparing options, evaluating APIs or products, sizing markets, mapping competitors, studying customers, synthesizing reviews, inspecting UX, or testing positioning. Do not use as the owner of settled fact-checking, present-state audits, or intent authoring.