Loading...
Loading...
Found 1,914 Skills
Mailchimp platform help — email marketing campaigns, Customer Journey Builder automations, SMS marketing, audience management/CRM, landing pages, A/B testing, multivariate testing, transactional email (Mandrill), Content Studio, generative AI (Intuit Assist), retargeting ads, 300+ integrations. Use when asking 'how do I do X in Mailchimp', setting up Mailchimp campaigns, configuring Customer Journey Builder, managing Mailchimp audiences, using Mandrill transactional email, or troubleshooting Mailchimp deliverability. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), funnel strategy (use /sales-funnel), or connecting tools via middleware (use /sales-integration).
ClickHouse cluster migration planner. Use when planning data migration between ClickHouse clusters, including cross-cluster migrations, horizontal scaling, disk downgrade, availability zone changes, or migrating from self-built/non-Alibaba Cloud ClickHouse to Alibaba Cloud ClickHouse (Community or Enterprise Edition). Helps analyze migration conditions, select appropriate migration methods, and generate detailed migration plans.
Mailgun (Sinch) platform help — developer-first transactional email API and SMTP relay with inbound routing, webhooks, and Mailgun Optimize deliverability tools. Use when sending transactional email via Mailgun API or SMTP, configuring domains or DNS (DKIM/SPF), setting up inbound email routing, managing webhooks or templates, using Mailgun Optimize for inbox placement testing, or working with the Mailgun REST API. Do NOT use for general email deliverability strategy (use /sales-deliverability), cross-platform email marketing (use /sales-email-marketing), or email open/click tracking strategy (use /sales-email-tracking).
GetProspect platform help — B2B email finder, verifier, enrichment, and cold email outreach with 200M+ contacts and 26M+ companies. Includes LinkedIn Email Finder Extension, contact enrichment (40+ attributes), email verification (97% deliverability guarantee), and cold email sequences. Use when finding B2B emails, enriching leads, verifying emails, building cold email sequences, exporting leads from LinkedIn, or working with the GetProspect API. Do NOT use for cross-platform enrichment strategy (use /sales-enrich), email deliverability strategy (use /sales-deliverability), prospect list strategy (use /sales-prospect-list), or outbound cadence strategy (use /sales-cadence).
Kit (formerly ConvertKit) platform help — email marketing, visual automations, sequences, landing pages, forms, Creator Profile, Commerce (digital products, paid newsletters), Creator Recommendations, subscriber tagging and segmentation, engagement scoring, API. Use when asking 'how do I do X in Kit', 'how do I do X in ConvertKit', configuring Kit settings, setting up automations, managing subscribers, selling digital products, or using the Kit API. Do NOT use for cross-platform email marketing strategy (use /sales-email-marketing), cross-platform deliverability (use /sales-deliverability), funnel strategy (use /sales-funnel), newsletter monetization strategy (use /sales-newsletter), audience growth strategy (use /sales-audience-growth), or digital product strategy (use /sales-digital-products).
OpenWeb Ninja platform help — real-time public data API stack with 30+ APIs for web scraping, enrichment, and business data. Key APIs include Website Contacts Scraper, Email Search, Local Business Data (Google Maps), Real-Time Web Search (SERP), JSearch (job postings), and Product Data. Use when extracting emails/contacts from domains, searching Google Maps for local businesses, running web search via API, aggregating job postings, fetching product data, or working with any OpenWeb Ninja API. Do NOT use for cross-platform enrichment strategy (use /sales-enrich), prospect list building strategy (use /sales-prospect-list), or connecting tools (use /sales-integration).
CORS misconfiguration testing playbook. Use when analyzing cross-origin trust, credentialed browser reads, origin reflection, preflight policy bugs, and browser-based access to authenticated APIs.
Apply rigorous survey design principles including construct operationalization, Likert scale development, reliability and validity assessment, and common method variance control. Use this skill when the user designs questionnaires, develops measurement items, needs to evaluate Cronbach's alpha or AVE, or when they ask 'how do I operationalize this construct', 'is my scale reliable', or 'how do I control for CMV'.
Early rug-risk triage for token launches and small DeFi deployments from public data—liquidity lock and pool events, dev and sniper wallet clustering, contract authority and transfer-risk checks, coordinated exits, and evidence-backed risk scores. Use when the user asks for rug pull detection, pump-and-dump signals, launch red flags, LP removal forensics, or cross-chain profit exit tracing—not for front-running trades, harassing teams, or certifying scams without on-chain proof.
Identifies upsell and cross-sell opportunities within existing customer accounts. Analyzes product usage, feature gaps, team growth, industry benchmarks, and competitive pressure to surface revenue expansion plays scored by potential, effort, and likelihood. Generates an expansion-playbook.md with account-by-account opportunities, recommended pitch, timing, and approach.
Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports. Uses a fresh cross-model reviewer with web/DBLP/arXiv lookup to catch hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations (cite present but the cited paper does not establish the claim). Use when user says "审查引用", "check citations", "citation audit", "verify references", "引用核对", or before submission to ensure bibliography integrity.
Follow this sub-process for code optimization — handle tasks where 'behavior remains unchanged but structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step by step according to the method library, and obtain manual approval for each step'. Trigger scenarios: When the user mentions phrases like 'optimize / refactor / rewrite / split / poor performance / too long code' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).