Loading...
Loading...
Found 1,134 Skills
PluginEval quality methodology — dimensions, rubrics, statistical methods, and scoring formulas. Use this skill when understanding how plugin quality is measured, when interpreting a low score on a specific dimension, when deciding how to improve a skill's triggering accuracy or orchestration fitness, when calibrating scoring thresholds for your marketplace, or when explaining quality badges to external partners like Neon.
Email engagement tracking for sales — open tracking, click tracking, attachment views, real-time notifications, follow-up timing, and engagement analytics. Use when setting up email tracking, interpreting open/click data, Mixmax tracking, Woodpecker tracking, timing follow-ups based on engagement, understanding tracking limitations (Apple MPP, pixel blocking), Reply.io tracking, or choosing a tracking tool. For Yesware-specific help, use /sales-yesware. Do NOT use for email deliverability (use /sales-deliverability), cadence design (use /sales-cadence), or buying intent signals beyond email (use /sales-intent).
Interpret Qwilr engagement signals and decide what to do next. Use when a prospect viewed or didn't view a proposal, analyzing Qwilr analytics, understanding proposal engagement patterns, figuring out why a buyer went dark after a proposal, deciding when to follow up after sending a proposal, understanding read receipts on proposals, or seeing who viewed a Qwilr quote.
Design a Qwilr deal room for complex multi-stakeholder B2B deals. Use when setting up a deal room, building a Qwilr deal room, creating a digital sales room, managing a multi-stakeholder deal, building buyer enablement content, creating a mutual action plan, or packaging an enterprise deal.
Map the buying committee at a target account — identify decision-makers, influencers, champions, and blockers, then recommend a multi-threading strategy. Use when mapping stakeholders at a deal, finding the right entry point at a target account, multi-threading an enterprise deal, understanding who's involved in a purchase decision, or planning account penetration. Do NOT use for building prospect lists across many accounts (use /sales-prospect-list), general account research (use /sales-research), or deal health assessment (use /sales-deal-inspect).
Apollo.io platform help — config, integrations, CRM sync, API, analytics, dialer, Chrome extension, credit management, admin. Use when asking 'how do I do X in Apollo', configuring Apollo settings, troubleshooting Apollo integrations, managing Apollo credits, or using the Apollo API. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), interpreting buying signals (use /sales-intent), or designing outbound sequences (use /sales-cadence).
Enrich contacts and companies with verified emails, phones, and firmographic data. Also covers CRM data hygiene, deduplication, and bulk enrichment. Use when enriching leads, finding email addresses, cleaning CRM data, doing bulk enrichment, optimizing enrichment credits, setting up auto-enrichment, or fixing stale contact data. Do NOT use for building new prospect lists from scratch (use /sales-prospect-list), interpreting buying signals (use /sales-intent), or general Apollo platform help (use /sales-apollo).
Prospeo platform help — person enrichment, company enrichment, person search, company search, bulk enrichment, Chrome extension, LinkedIn Sales Navigator extraction, 5-step email verification, intent signals, API. Use when asking 'how do I do X in Prospeo', configuring Prospeo settings, managing enrichment, using the Prospeo API, or troubleshooting Prospeo issues. Do NOT use for building prospect lists (use /sales-prospect-list), enrichment strategy across tools (use /sales-enrich), cross-platform deliverability (use /sales-deliverability), or interpreting buying signals (use /sales-intent).
Production-first enterprise skill for The Composable Architecture (TCA) with SwiftUI (iOS 16+, TCA 1.7+). This skill should be used when building new TCA features with @Reducer macro, decomposing god reducers, implementing StackState/StackAction navigation or tree-based @Presents navigation, writing TestStore tests, migrating legacy TCA code to modern @ObservableState patterns, debugging TCA performance issues, managing side effects and dependencies with @DependencyClient, or reviewing TCA code for anti-patterns. Use this skill any time someone works with TCA reducers, stores, effects, or dependencies — AI tools consistently generate outdated pre-1.7 TCA patterns, so this skill is essential for correct code.
Implement the Syncfusion Angular ListBox component for selection and data display. Use this when building interactive list interfaces with single or multiple selection modes. This skill covers drag-and-drop functionality, grouped data display, icons and templates, filtering, and accessibility support for enterprise-grade list components in Angular applications.
Enterprise skill for iOS production error observability and logging (iOS 15+, Swift 5.5+). Use this skill when writing or reviewing error handling code, adding logging to iOS apps, replacing print() with os.Logger, configuring crash reporting SDKs (Sentry, Crashlytics, PostHog), fixing silent error patterns (try?, Task {} swallowing errors, Combine pipelines dying), adding privacy annotations to logs, integrating MetricKit, implementing retry logic with observability, handling errors in SwiftUI .task {} modifiers, or auditing catch blocks for proper error reporting. Use this skill any time someone writes a catch block, uses try?, creates a Task {}, sets up error handling, or mentions logging, crash reporting, or error tracking in an iOS context — even if they just say 'add error handling' or 'why is this failing silently.'
Answer customer questions about Apollo products (OSS and enterprise) using public documentation and GraphOS MCP Tools. Use this skill when: (1) a customer asks a question about Apollo Router, Server, Client, GraphOS, Federation, Connectors, Rover, or MCP Server, (2) triaging a support question from Slack, Jira, or another channel, (3) researching Apollo product capabilities or configuration, (4) helping a customer troubleshoot an Apollo-related issue.