3.5K skills · sorted by relevance
Test marketing prompts against shared cases, score required content, prohibited phrases, and output format, and compare alternatives. Keep version history and diffs, use reusable templates, and check that prompt or model updates preserve output quality.
Plan, set up, audit, and debug analytics tracking with GA4 and Google Tag Manager. Define events and their parameters, configure conversion tracking, and investigate missing or duplicate data using structured checks and prioritized fixes.
Turn Git history into release notes and recommend the next version based on commit types and breaking changes. Check commit formatting, filter changes by package, and generate Markdown or JSON for automated release workflows.
Manage machine learning models and their versions in the Agent Platform Model Registry. List registered models, inspect details, upload new versions, update names or descriptions, and delete models through workflows that require confirmation for changes.
Guide a Kortix production release from choosing a version and writing release notes to testing on staging, merging the release pull request, and verifying production. Diagnose blocked promotions and direct fixes back to the dev branch.
Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.
Audit server-side advertising measurement by comparing browser and server events, checking duplicate handling, consent, and data quality. Reconcile platform diagnostics with source logs and business conversions, then return prioritized findings, owners, and verification steps.
Prepare and publish a Plannotator release with contributor credits, coordinated version updates, ordered builds, and tag-triggered publishing. The workflow also checks package contents, security scan results, and evidence showing how release files were built.
Updates Claude Code CLI release tracking within the Claude Code Ultimate Guide, following its documented workflows. It can also handle an explicitly requested guide version bump and report changes, verification results, and unresolved checks.
Build, test, and publish the Windows version of OpenMausBot, including its installer and automatic update files. Check packaged resources and installation behavior, mirror release files for older installations, and investigate users remaining on outdated versions.
Analyze Google Ads campaign history, conversion volume, and budgets to choose suitable bidding strategies for each campaign. Get recommended targets, reasons for each choice, and a transition plan covering timing and short-term risks.
Audit Facebook and Instagram advertising data for repeated-ad fatigue, overlapping audiences, campaign structure, and conversion tracking issues. Receive an account health summary, prioritized recommendations, and opportunities to increase budgets where performance supports expansion.
Prepare and validate a version update for @macro-inc/sdk, then track its automatic release after an authorized merge. Verify the published version and npm distribution label, and report whether the release is prepared, publishing, failed, or published.
Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.
The English summary is being prepared. Showing the original description.
Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
The English summary is being prepared. Showing the original description.
Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.
The English summary is being prepared. Showing the original description.
Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs. Use this skill whenever the user wants to write a landing page, sales page, hero section, or any conversion-focused web copy. Triggers on landing page, sales page, hero copy, value proposition, headline, subheadline, hero section, CTA copy, conversion copy, opt-in page, squeeze page. Also triggers when the user has a marketing campaign or product launch needing dedicated conversion copy. Use `cro-optimization` instead when the page already exists and the ask is to lift its conversion rate through testing rather than to write the copy.
The English summary is being prepared. Showing the original description.
Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to start, or when test results are ambiguous and need interpretation.
The English summary is being prepared. Showing the original description.
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (install_comfyui (action:"self_update"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way that smells like version drift ("panel is too old", a graph_/ui_ command the panel doesn't implement, a feature that works in the docs but not in the sidebar), or when the user asks to update/pin/unpin the panel. It checks the installed panel version against what THIS orchestrator build needs, RESPECTS an explicit version pin (warn-only, never move a pinned user), offers a clear way to unset the pin, runs the sync through the verified install_comfyui(action:'panel') path, and reports the version RE-READ from disk. Never claim a sync that did not happen.
The English summary is being prepared. Showing the original description.
Use when conversion TRACKING must be set up or fixed before spending — Meta Pixel and Conversions API, Google Ads conversions with Enhanced Conversions, GA4, TikTok Pixel and Events API, server-side GTM, consent mode for GDPR and CCPA, UTM conventions, iOS ATT attribution windows, and a pre-launch verification checklist. Trigger on 'tracking setup', 'pixel setup', 'CAPI', 'GA4 events', 'conversions are not being recorded', 'Meta and Shopify numbers do not match'. Also use when launch is imminent and nothing has been verified. Not for — auditing a live account broadly, see `21-ads-audit-global`; analyzing data once it flows, see `13-data-analysis-global`; the campaign hierarchy, see `52-account-structure-global`.
The English summary is being prepared. Showing the original description.
Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
The English summary is being prepared. Showing the original description.
Use when versioning Spring MVC or WebFlux APIs in Spring Boot 4 / Spring Framework 7. Covers built-in mapping versions, request version resolution, defaults, supported versions, and deprecation headers.
The English summary is being prepared. Showing the original description.
Version REST and GraphQL APIs. Use when a user asks to version an API, handle breaking changes, implement API deprecation, manage multiple API versions, or design an API evolution strategy.
The English summary is being prepared. Showing the original description.
World-class landing page expertise combining conversion rate optimization science, persuasive design psychology, and the craft of pages that turn visitors into customers. Landing pages are where marketing meets reality—the moment of truth where visitors decide. Great landing pages aren't just pretty—they're conversion machines. The best landing page designers understand that every element must earn its place, that friction is the enemy, and that the goal isn't to impress—it's to convert. Speed, clarity, and persuasion in perfect balance. Use when "landing page, conversion page, lead capture, signup page, pricing page, hero section, above the fold, CTA design, conversion rate, page optimization, lead gen page, squeeze page, sales page, landing-pages, conversion, CRO, design, optimization, lead-generation, signups, forms" mentioned.
The English summary is being prepared. Showing the original description.