Marketing & Growth

buildsbymatt Skill

Run link building outreach through the MentionAgent MCP server. Use when asked to review outreach drafts, send the batch, answer publisher replies, check what is waiting in the inbox, close a placement, pause or resume sending, or change a campaign. Also use for "backlinks", "link building", "guest post replies", "who replied", "which emails need an answer", and anything mentioning MentionAgent.

sergeyitaly Skill

Give an honest, evidence-based verdict on whether the "Claude Skills Manager" VS Code extension (claude-skill-deployer) is actually delivering real value in THIS project — not a usage-count report of individual skills (see skill-usage-insights for that), but a judgment of the extension's own core mechanisms (adaptive skill suggestions/confidence scoring, task-focus, budget/cost gating, MCP-Force security mode, cross-agent sync, hooks pipeline) against real .claude/learning/ telemetry and the agent's own actual session experience. Use when asked "is this extension helping", "give feedback on Claude Skills Manager", "extension ROI", "does the extension actually do anything", "audit the extension's value", or similar. Produces a blunt, numbers-grounded report — not marketing copy.

ilog3 Bundle

Use when distilling a scholar, professor, research group, or intellectual lineage into an evidence-grounded research assistant for academic background mapping, topic selection, research-question generation, Survey or literature-review outlining, theory/method choice, and paper positioning. Trigger when the user mentions 学者蒸馏, 人物蒸馏 for academic research, scholar persona, academic style distillation, research background, 选题, Survey, literature review, professor profile, AMiner/Google Scholar/Semantic Scholar/OpenAlex profile, or wants to learn from a scholar's publications without impersonating them.

ilog3 Skill

Use when education research needs advanced quantitative modeling beyond common t-tests, ANOVA, chi-square, correlation, and simple regression. Covers multilevel/hierarchical linear models, SEM, latent variable models, mediation, moderation, moderated mediation, IRT, longitudinal/growth models, DID, propensity score adjustment, nested school/class/student data, and advanced model reporting. This second-layer execution skill supports quantitative, mixed-methods, intervention, learning analytics, psychometric, and program evaluation studies.

mart-cervants Bundle

Use when the user wants to create, set up, or configure a Saleshandy outreach sequence/campaign. Applies cold-email best practices (step cadence, timing, deliverability formatting) by default and always confirms sequence/step/account choices explicitly with the user before creating anything.

samraddhashrivastavatech Skill

Compare competing solutions/entities with an emphasis on positioning, strengths, and weaknesses. Use for market, product, and technology competition questions.

hajgen19 Skill

Budget-Check für Google Ads

hajgen19 Skill

Wochen-Check für die Google Search Console

hajgen19 Bundle

Run a state-of-the-art, SERP-first SEO keyword research for a single page, ending with a publication-ready content brief and outline. Use this skill whenever the user mentions keyword research, content brief, SEO outline, topic research, search intent analysis, SERP analysis, keyword clustering, cannibalization check, or wants to plan a new page or blog post for SEO. Triggers include "research keywords for", "build a brief for", "plan a page about", "analyze SERPs for", "find keywords around", or any German variants ("Keywordrecherche", "Briefing fuer", "SEO-Brief", "Recherche zu", "neue Seite ueber"). Works in phases with explicit user-confirmation between phases. Do NOT use for: site-wide keyword audits, link-building research, technical SEO audits, or PPC keyword research.

hajgen19 Skill

Prüft in GA4, ob Ereignisse oder Key Events plötzlich ausbleiben oder einbrechen – Hinweis auf kaputtes Tracking, per MCP oder CSV-Export. Nutzen bei Anomalie-Check, Tracking prüfen.

hajgen19 Skill

Chancen-Keywords aus der Search Console

hajgen19 Skill

Kannibalisierungs-Check mit der Search Console

hajgen19 Skill

Findet Seiten, die über 6–12 Monate am stärksten verloren haben und vorher stark waren – Update-Kandidaten, per MCP oder CSV-Export. Nutzen bei Update-Kandidaten, Content-Refresh.

hajgen19 Skill

Vergleicht in GA4 zwei frei wählbare Zeiträume nach Kanal und Landingpage, nennt Gewinner, Verlierer, Potenziale – per MCP oder CSV-Export. Nutzen bei GA4-Vergleich, wo wächst der Traffic.

hajgen19 Skill

Prüft den Indexierungsstatus von URLs in der Search Console und nennt nicht indexierte Seiten mit Grund – per MCP oder CSV-Export. Nutzen bei Indexierung prüfen, nach Deploy.

orcaqubits Skill

Build Next.js storefronts for Saleor — GraphQL client setup, channel routing, Tailwind CSS, server components, checkout flow, and SEO. Use when developing Saleor storefronts.

orcaqubits Skill

Build with Spree's headless Next.js storefront — the official `spree/storefront` repo (Next.js 16 App Router with Server Actions and Turbopack, React 19 Server Components, Tailwind CSS 4, TypeScript 5, `@spree/sdk`, Sentry), server-only auth (httpOnly JWT cookies + publishable key), MeiliSearch faceted catalog, one-page checkout with Apple/Google Pay/Klarna/Affirm/SEPA, multi-region market routing, GA4 + JSON-LD SEO, and Vercel/Docker deployment. Use when forking or customizing the storefront, or evaluating headless adoption.

learningmatter-mit Bundle

Simulate non-conservative phase-fields (grain growth and phase transformations) using the Allen-Cahn equation.

emanuelegreco29 Bundle

Frontend engineering guidance - component architecture, state management, CSS/styling architecture, forms and validation, routing, responsive/mobile design, frontend performance, SEO/AI-visibility, and accessibility. Use for any UI/component/frontend-structure question, including what to test on the frontend (see codexpiator-testing-qa for general testing strategy/TDD discipline instead).

breroz Bundle

Optimize a website's source files (and, once live, the deployed site) for traditional search and AI/answer-engine visibility by directly editing the code rather than just producing an audit report. Triggered by the literal slash command /seo-aeo. When invoked, detect whether the user is pointing at local files or a repo (pre-deploy mode) or a live URL (post-launch mode), then run the matching workflow. In file mode it edits metadata, headings, schema, AEO content blocks, robots.txt, sitemap, and internal links in place. In live mode it runs real Core Web Vitals, indexing, SERP, and AI-citation validation against the deployed site.

breroz Skill

Use this skill when a user wants to generate bold, scroll-stopping, viral-ready image concepts and production-ready AI image generation prompts (for tools like Ideogram, Midjourney, or DALL·E). Triggers include: "create image prompts", "generate visual concepts", "make viral images", "social media visuals", "ad creative concepts", "image prompts for my brand", "create visuals for my product", "generate image ideas", "campaign visuals", "hero image concepts", "scroll-stopping visuals", or any request to turn a brand or product into striking, share-worthy visual content. Always use this skill when the user uploads or pastes a Brand Style Guide and/or Implementation Guide and wants visual concepts or image prompts generated from them. Also triggers when someone asks for paid social ad creative, organic content visuals, or landing page hero image concepts.

toolmonsters Bundle

Builds B2B positioning and messaging (value proposition, differentiation, how to describe what you sell) from rules weighted by how many of the 20 most-watched videos on the topic repeat each one, and flags where experts disagree so you A/B test instead of guessing. Use when the user says "position my product", "write our value proposition", "how do we stand out from competitors", "fix our messaging", "describe what we sell", or "B2B positioning".

samber Bundle

Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume. Use whenever the user asks what developers actually search for, wants keywords for a developer tool, API, SDK or docs site, an error-message keyword list, demand sizing for a technical topic, or which docs pages to create from search demand - even if they never say "keyword". Does not write the pages. Do NOT use for on-page or docs-site SEO - use samber/developer-relations-skills@docs-seo.

shaashiekumha Bundle

Expert guide and integration toolkit for Payhip e-commerce platform (help.payhip.com). Use when setting up or managing Payhip stores, products (digital downloads, courses, memberships, physical, coaching, bundles), custom domains, embed buttons/modals, direct checkout links, license keys API, webhooks, affiliate marketing, EU/UK VAT compliance, or building custom developer integrations with Payhip.

samber Bundle

Design a B2B SaaS marketplace operator's launch and ongoing app co-marketing program - sizing and gating the founding launch cohort, the keynote-anchored reveal and partner embargoes, featured-placement and app-of-the-month spotlight governance, and the budget split between marketplace-wide demand generation and rationed per-partner co-marketing (MDF, paid catalogs, tier gates). Use whenever the user mentions launching an app marketplace, picking launch partners, featured apps, partner spotlights, MDF, or a joint launch announcement - even if they never say "marketplace launch". Operator side only. Do NOT use for a vendor optimizing its own listing elsewhere - use samber/developer-platform-skills@integration-listing-optimization instead.

samber Bundle

Runs on-page and technical SEO for a documentation site - indexability, canonicals and hreflang across versioned and translated pages, redirects, the generator's title and description templates, internal linking, and an owner-assigned fix list against an agreed pass threshold. Use whenever someone says "docs SEO", "our docs don't rank", "documentation search optimization", "the old version of our docs outranks the current one", "our docs pages aren't indexed", "fix the canonicals on our docs", "docs sitemap problems", "hreflang on our translated docs" or "preview docs got indexed" - even if they never say SEO. Covers versioned, translated and auto-generated reference docs. Not keyword research - use samber/developer-relations-skills@developer-keyword-research.

samber Bundle

Plans and runs an open-source project launch end to end - name and license clearance, the readiness gate, positioning and one-liner, channel sequencing, the launch-day war room, star-velocity and GitHub Trending mechanics, and post-launch measurement. Use whenever someone is about to release, announce, open-source or "Show HN" a repository, asks how to reach GitHub Trending, wants the first real users or stars for a new library, is planning a Product Hunt post or a multi-day launch week, or asks why a launch fell flat (even if they only say they are pushing a repo public). Covers individual-developer and company adoption. Not ongoing distribution afterwards - use samber/developer-relations-skills@oss-distribution-strategy instead.

samber Bundle

Audits an existing developer documentation set's structure - a page-by-page inventory classified against the Diátaxis modes (tutorial, how-to, reference, explanation), mixed-mode and misplaced pages, coverage gaps per product surface, navigation drift against the file tree, a CNCF TechDocs rubric score, and a prioritized remediation queue. Use whenever the user mentions a docs structure or content audit, docs information architecture, Diátaxis, "our documentation is a mess", a docs gap analysis, what docs are missing, where a page should live, or reorganizing a documentation site - even if they only say "our docs are hard to navigate". Not for writing pages. Do NOT use for docs search ranking - use samber/developer-relations-skills@docs-seo.

samber Bundle

Turns support tickets, issue history and error telemetry into troubleshooting and error-reference pages a developer finds by pasting the error string - symptom, conditions, cause, fix and verification entries, an error-code catalog generated from one source of truth, and fixes wired back into the product's own error output. Use whenever the user mentions troubleshooting docs, documenting error codes, error message pages, a known-issues page, building an FAQ from support tickets, or "we answer the same question every week" - even if they only say "users keep hitting this error". Not for debugging a live incident. Do NOT use for docs search ranking - use samber/developer-relations-skills@docs-seo.

samber Bundle

Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list. Use whenever someone asks whether to start doing DevRel, what a new devrel program should do first, why devrel work is busy but not landing, how to justify the program to an exec, which pillar deserves the next investment, who to hire next, or whether to outsource content, events or community - even if they never say "strategy". Not the first-90-days plan - use samber/developer-relations-skills@developer-relations-kickoff. Not metrics, org chart or budget math.

macfarlanem-cloud Skill

Use whenever the user asks for a rubric, scoring guide, checklist, or "criteria for success" for any assignment, discussion, project, or presentation, or asks to convert a points-only grading scheme into a rubric. Produces transparent rubrics with growth-mindset rating columns (You did it, Almost, Getting close, Not yet), the same number of columns on every row, criteria a learner can self-check before submitting, and learner-facing language. Also use when building the rubric in Canvas. Do not use for institutional program review rubrics or peer-review instruments.

seryozh Bundle

Open a creative problem into genuinely distinct, audience-aware directions, test each direction against the factual floor and real experience, recommend the strongest path, and lock a committed brief once a direction is chosen. Use for visual, editorial, product, messaging, campaign, naming, experience, format, or strategy work that needs lateral exploration before precise execution, or when the current solution space feels generic or stuck. Do not invoke when a clear approved specification only needs exact implementation.

samber Bundle

Designs the go-to-market motion for a developer-facing product - bottom-up self-serve adoption, developer-influenced sales, top-down with developer proof, or ecosystem-mediated distribution - plus the self-serve entry, the developer-to-buyer handoff rule and the land-and-expand path. Use whenever a founder, devrel or growth owner asks how developer adoption turns into revenue, whether to go bottom-up or hire sales, when to contact a free user, why signups are high and paid accounts flat, or how landed teams expand across an enterprise - even if they only say "our funnel is broken". Not price points - use samber/developer-relations-skills@devtools-pricing-strategy.

samber Bundle

Designs the developer relations org - which function DevRel reports to (marketing, product, engineering, CEO, sales) and what that line starves, the shape (centralized, split, embedded, hub-and-spoke), the coverage map across advocacy, community, docs and education, the interlocks with product, docs, support and sales, and the trigger for the next re-org. Use whenever someone asks where DevRel should sit, who DevRel should report to, how to structure or restructure a devrel team, which devrel roles to staff at this size, whether to embed advocates in product teams, why devrel keeps getting pulled into other teams' work, or how devrel and docs divide ownership - even if they only say the team feels wrong. Not the budget split - use samber/developer-relations-skills@devrel-budget-allocation.

samber Bundle

Writes or edits a technical blog post a skeptical developer audience will believe - the right post pattern, evidence behind every claim, published trade-offs and limitations, runnable snippets, and no marketing voice. Use whenever the user wants an engineering blog post, a technical article, a "how we built it" or "we rewrote it in X" story, a debugging write-up, a public postmortem, a benchmark post, or a product post that must not read as marketing, and when they ask to review, edit, de-jargon or de-market an existing technical draft - even if they only call it "the article". Not a teaching tutorial - use samber/developer-relations-skills@developer-tutorial. Not release notes, a migration guide, a case study or a talk.

samber Bundle

Chooses the business model for a developer tool - proprietary SaaS, open core, hosted open source, support and LTS subscription, dual licensing, source-available, consumption metering, marketplace take-rate, OEM licensing - and the go-to-market each one forces. Use whenever a founder or exec asks how a developer tool should make money, whether open core or a managed cloud fits better, where the line between free and paid belongs, whether to open-source the product at all, or why adoption is high and revenue flat, and on any monetization, revenue model or commercial open source question - even if they never say "business model". Not price points, packaging or free-tier limits - use samber/developer-relations-skills@devtools-pricing-strategy.