Loading...
Loading...
Found 1,934 Skills
Klaviyo platform help — AI-first B2C CRM and marketing automation for e-commerce with predictive analytics, 350+ integrations, and cross-channel messaging. Use when building e-commerce email/SMS automation, setting up Klaviyo flows or segments, configuring Shopify-Klaviyo integration, using predictive analytics (CLV, churn risk), managing forms or reviews, or working with the Klaviyo API. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), or email open/click tracking strategy (use /sales-email-tracking).
Comprehensive validation patterns for ASP.NET Core applications. Covers FluentValidation integration, DataAnnotations, IValidatableObject, IValidateOptions<T>, MediatR pipeline behavior, and client-side validation. Use when implementing validation in ASP.NET Core applications, setting up FluentValidation, creating custom validators, configuring options validation, or implementing cross-field validation.
When the user wants help with Google Ads attribution models, data-driven attribution, attribution windows, cross-channel attribution, how attribution affects Smart Bidding, multi-touch conversion paths, or understanding which campaigns are actually driving conversions. Triggers on 'attribution', 'attribution model', 'data-driven attribution', 'last click attribution', 'assisted conversions', 'conversion window', 'multi-touch', 'attribution model comparison', 'first click attribution', 'credit allocation', or 'which campaign is driving conversions'. For conversion tracking setup see google-ads-conversion-tracking. For Smart Bidding strategy see google-ads-bidding.
When the user wants to optimize yard operations, manage trailer parking, or improve dock door utilization. Also use when the user mentions "yard management," "trailer tracking," "yard jockey," "drop trailer program," "trailer pool," "dock scheduling," or "gate management." For cross-dock operations, see cross-docking. For warehouse design, see warehouse-design.
Upgrade any Pulumi provider to a newer version and reconcile the resulting diff. Use when users want to upgrade or update a provider (including editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml to bump a provider SDK), check for breaking changes before or during an upgrade, fix resources that broke after a provider upgrade, or resolve unexpected replacements, creates, or deletes in a post-upgrade preview. Applies to all providers (aws, azure-native, gcp, kubernetes, aws-native, cloudflare, datadog, etc.) — not just Tier 1. Do NOT use for querying which stacks use what package versions; use skill `package-usage` for cross-stack audits. Do NOT use for general infrastructure tasks.
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.
LoyaltyLion platform help — points, tiers, rewards, referrals, custom loyalty pages, receipt upload (omnichannel), AI recommendations, analytics, Klaviyo Events integration, Admin API, Headless API. Use when LoyaltyLion points not accruing correctly, tiers not promoting members, custom loyalty page not displaying, Klaviyo flows not triggering from LoyaltyLion events, API returning errors, or rewards not redeeming at checkout. Do NOT use for cross-platform loyalty strategy (use /sales-loyalty), cross-platform email marketing (use /sales-email-marketing), or connecting tools generally (use /sales-integration).
Wind MCP Data Bridge Skill (v1.1.0, 6 servers / 19 tools). Route by `server_type`: (1) `quote` for market data (A-shares/Hong Kong stocks snapshots, daily/weekly/monthly K-lines, minute-level data); (2) `fund_data` for fund-related data (profile/finances/holdings/performance/holders/management company); (3) `stock_data` for in-depth stock data (profile/financial fundamentals/equity structure/events/technical indicators/risk); (4) `financial_docs` for document RAG (announcements/financial news); (5) `economic_data` for EDB macro + industry economic indicators; (6) `analytics_data` for general NL → Wind data. WIND_API_KEY is required (obtained by logging into the Developer Center at aimarket.wind.com.cn). Trigger scenarios: A-shares/Hong Kong stock codes/K-lines/minute-level data, any dimension of funds, stock financial reports/valuation, listed company announcements/financial news, macroeconomic data, cross-comparison of targets. **Excluded**: US stocks/European stocks/Japanese stocks, exchange rates/futures quotes, cryptocurrencies, non-financial data.
Art-to-engine pipeline specialist - Masters shaders, VFX systems, LOD pipelines, performance budgeting, and cross-engine asset optimization
Full-funnel cross-border e-commerce strategist covering Amazon, Shopee, Lazada, AliExpress, Temu, and TikTok Shop operations, international logistics and overseas warehousing, compliance and taxation, multilingual listing optimization, brand globalization, and DTC independent site development.
Error-to-fix playbook for every known failure mode on the OpenFinance backend — Polymarket, Relay, Hyperliquid, Privy delegation, and Solana RPC issues. Use this the moment a call fails, returns an unexpected status, or behaves inconsistently with on-chain state. Triggers on ANY of these error signatures verbatim or in paraphrase. Polymarket: "allowance: 0 but on-chain shows max", "CLOB reports allowance 0", "approvals confirmed but order rejected", "404 upstream" on market orders, "tick size" rejection, "order size below minimum", USDC.e vs pUSD vs native USDC confusion, V1 vs V2 exchange confusion. Relay: "InstructionFallbackNotFound", "Custom:101", "Custom:6000", "AnchorError", "Blockhash not found", "TransactionExpired", "No valid authorization signatures were provided", "Solana wallet is not delegated to the app", 412 delegation errors, quote succeeded but execute failed, stuck funds on Solana, stuck funds cross-chain, topupGas forced off. Hyperliquid: "Insufficient perp account value", "price out of bounds", WebSocket stale data, spot vs perp balance confusion. General: any "why is X failing", "why does on-chain and API state disagree", "what does this error mean". Read this BEFORE assuming a bug in the MCP or backend — most of these errors are already catalogued with known fixes.
Fetch recent posts from one or more X/Twitter accounts through twitterapi.io, output structured JSON/CSV records, optionally sync records to Feishu/Lark Bitable through feishu-cli, and optionally guide recurring execution through OpenClaw, Codex automations, cron, or launchd. Use when the user wants to monitor X bloggers, collect recent tweets, export tweet metrics, append tweets to Feishu Bitable, or set up a scheduled Twitter/X account tracking workflow.