Loading...
Loading...
Found 588 Skills
Live SEO data via DataForSEO MCP server. SERP analysis (Google, Bing, Yahoo, YouTube), keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis (Lighthouse, content parsing), competitor analysis, content analysis, business listings, AI visibility (ChatGPT scraper, LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "competitor data", "AI visibility check", "LLM mentions", or "real search data".
Reply.io platform help — multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp), Jason AI SDR, B2B database, email warmup, deliverability tools, unified inbox, analytics, Salesforce/HubSpot integration, agency features. Use when asking 'how do I do X in Reply.io', setting up Reply.io sequences, configuring Jason AI, connecting Reply.io to Salesforce or HubSpot, using Reply.io warmup, or troubleshooting Reply.io deliverability. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Reply.io to other tools via Zapier (use /sales-integration).
Scoring formulas and analytical frameworks for GitHub workflow agents. Covers repository health scoring (0-100, A-F grades), priority scoring for issues/PRs/discussions, confidence levels for analytics findings, delta tracking (Fixed/New/Persistent/Regressed), velocity metrics, contributor metrics, bottleneck detection, and trend classification. Use when computing scores, tracking remediation progress, building prioritized dashboards, or detecting workflow bottlenecks.
Mobile and web push notification strategy — opt-in optimization, rich push, segmentation, timing, frequency capping, deep linking, A/B testing, and analytics. Covers strategy and implementation across Braze, OneSignal, Airship, Firebase/FCM, Customer.io, Klaviyo, Iterable, and MoEngage. Use when designing push notification strategy, improving push opt-in rates, building push campaigns, choosing a push provider, or optimizing push engagement. Do NOT use for in-app messages (use /sales-in-app-messaging), email marketing (use /sales-email-marketing), SMS/WhatsApp messaging (use /sales-braze or platform-specific skill), or cold outbound (use /sales-cadence). For Braze-specific help, use /sales-braze. For Customer.io-specific help, use /sales-customerio.
This skill should be used when the user asks about Hyperliquid whale positions, Hyperliquid liquidations, Hyperliquid open interest, Hyperliquid trader analytics, Hyperliquid taker data, smart money on Hyperliquid, or any Hyperliquid-specific query. Use when user says: 'Hyperliquid whales', 'HL whale positions', 'HL liquidations', 'HL open interest', 'HL trader', 'smart money', 'Hyperliquid大户', 'HL鲸鱼', 'HL持仓', 'HL清算', 'HL持仓量', 'HL交易员'. For general crypto prices/news, use market.
Run ClickHouse queries for analytics, metrics analysis, and event data exploration. Use when you need to query ClickHouse directly, analyze metrics, check event tracking data, or test query performance. Read-only by default.
Interact with the SocialCrawl API — a unified social media data API covering 21 platforms and 105 endpoints. Fetch profiles, posts, comments, search results, and analytics from TikTok, Instagram, YouTube, Facebook, Twitter/X, LinkedIn, Reddit, Threads, Pinterest, and 12 more platforms through a single API. Use when the user wants to: (1) fetch social media data (profiles, posts, comments, search), (2) generate code that calls the SocialCrawl API, (3) understand SocialCrawl endpoints, pricing, or capabilities, (4) check their SocialCrawl credit balance, or mentions "SocialCrawl", "social crawl", or "social media API".
Describes how blockchain analytics platforms work in practice, typical use cases (markets, compliance, law enforcement, tax, market integrity), tool layers like visualizers and tracers, and limitations of heuristic attribution. Use when the user asks about blockchain analytics for AML, transaction monitoring, forensic tracing, institutional ops, or taint-style analysis at a high level.
Run KQL queries against Fabric Eventhouse for real-time intelligence and time-series analytics using `az rest` against the Kusto REST API. Covers KQL operators (where, summarize, join, render), Eventhouse schema discovery (.show tables), time-series patterns with bin(), and ingestion monitoring. Use when the user wants to: 1. Run read-only KQL queries against an Eventhouse or KQL Database 2. Discover Eventhouse table schema and metadata 3. Analyse real-time or time-series data with KQL operators 4. Monitor ingestion health and active KQL queries 5. Export KQL results to JSON Triggers: "kql query", "kusto query", "eventhouse query", "kql database", "real-time intelligence", "time-series kql", "query eventhouse", "explore eventhouse", "show tables kql"
Operate DefiLlama public analytics APIs through UXC with a curated OpenAPI schema and read-first guardrails.
Alibaba Cloud SLS (Simple Log Service) log query & analysis skill. Use this skill to help users write, explain, optimize, execute, or troubleshoot SLS index search, SQL analytics, and SPL scan/pipeline statements through the aliyun CLI. Triggers: "SLS 查询", "SLS 分析", "日志查询", "日志分析", "log query", "analyze sls logs", "aliyun log query".
Pendo platform help — product analytics, in-app guides, session replay, NPS/CSAT surveys, feature adoption tracking, Leo AI. Use when Pendo guides aren't showing, feature tagging is tedious, analytics data looks wrong, users aren't completing onboarding, NPS scores are flat, need help with Pendo API or aggregation queries, setting up Pendo for the first time, or comparing Pendo to Appcues or WalkMe. Do NOT use for in-app messaging strategy across platforms (use /sales-in-app-messaging) or general customer feedback strategy (use /sales-customer-feedback).