Results for “connector”

Sorts an email inbox into reply-now, reply-later, and ignore buckets, and drafts replies for urgent messages using an existing Gmail connector.

Use this skill when reviewing Model Context Protocol (MCP) servers, clients, connectors, tool manifests, hosted MCP deployments, OAuth flows, prompt/tool boundaries, or MCP marketplace choices for security, least privilege, data exposure, prompt injection, and destructive-action risk.

Model threat actors, intrusion sets, campaigns, and TTPs as a STIX 2.1 knowledge graph in OpenCTI using the pycti Python client, connectors, and import workers for structured cyber threat intelligence.

Data framework for building LLM applications with RAG. Specializes in document ingestion (300+ connectors), indexing, and querying. Features vector indices, query engines, agents, and multi-modal support. Use for document Q&A, chatbots, knowledge retrieval, or building RAG pipelines. Best for data-centric LLM applications.

Data framework for building LLM applications with RAG. Specializes in document ingestion (300+ connectors), indexing, and querying. Features vector indices, query engines, agents, and multi-modal support. Use for document Q&A, chatbots, knowledge retrieval, or building RAG pipelines. Best for data-centric LLM applications.

Deploy Palo Alto Networks Prisma Access for SASE-based zero trust network access using GlobalProtect agents, ZTNA Connectors, security policy enforcement, and integration with Strata Cloud Manager.

Deploy Zero Trust Network Access using Zscaler Private Access (ZPA) to replace traditional VPN with identity-based, context-aware access to private applications through the Zscaler Zero Trust Exchange.

Routing guide for the built-in QwenWork Connector tools (mcp__qw-builtin__qw_query / mcp__qw-builtin__qw_action). Load ONLY right before calling them to view or manage QwenWork's OWN tasks/sessions or app configuration, or when a qw tool result explicitly asks. Before loading, always check whether another skill or tool can do the job — if so, use that instead. Unless the user explicitly asks, never use it to view skills, plugins, MCP servers, or third-party connectors. Never load in any non-essential scenario (content creation, PPT/docs, coding, research, web tasks), even when the topic is QwenWork itself. If in doubt, do not load.

Create Jira issues such as tasks, stories, bugs, or subtasks from user intent. Use when a user asks to open, file, draft, or create a Jira ticket and needs fields validated, issue text composed, Jira API or connector calls made, and the created issue link returned.

Use when the user asks how to build with OpenAI products or APIs and needs current official documentation with citations, including Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities, limits, or migrations; prioritize an available official OpenAI documentation connector and restrict fallback browsing to official OpenAI domains.

Index of the org's MCP fabric — how the admin-mcp gateway, its meta-tools (admin_list_tools, admin_mcp_directory, admin_call_mcp), dynamic connectors, and the desktop IX Agency Tools tab fit together, plus the full table of all 38 MCP tiles. Start here when unsure which service/tool to use.

Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.

Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow through the openai-docs skill or an official OpenAI documentation connector before generating code.

Before any cold touch on a target account, find and rank every warm way in. Inventories your team's collective network, customers, past colleagues, investors, and community overlap, scores each path, picks one connector, and writes the forwardable intro request. Built for B2B sellers, customizable to your network sources and CRM. Trigger on "warm intro path", "who can intro me", "bridge before cold", "warm path into this account", "find a referral path".

Expert knowledge for Azure Sentinel development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring Sentinel data connectors, analytics rules, playbooks/Logic Apps, ASIM schemas, or SAP/AWS/GCP sources, and other Azure Sentinel related development tasks. Not for Azure Defender For Cloud (use azure-defender-for-cloud), Azure Security (use azure-security), Azure Monitor (use azure-monitor), Azure Network Watcher (use azure-network-watcher).

Use to get access to Rulebase and connect an AI client to it — signing up, finding your data region, installing the Rulebase MCP server in Claude Code, Claude Desktop or Cursor, and creating an API key for the REST API. Trigger for "connect Claude to Rulebase", "install the Rulebase MCP", "set up the Rulebase connector", "create a Rulebase API key", "how do I sign up for Rulebase", "Rulebase returns 401", "no token provided", or when Rulebase tools are missing from a session.

Expert knowledge for Azure Logic Apps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building Logic Apps with SAP/IBM/FTP connectors, B2B/EDI flows, AI/OpenAI calls, XML/JSON transforms, or DevOps CI/CD, and other Azure Logic Apps related development tasks. Not for Azure Functions (use azure-functions), Azure API Management (use azure-api-management), Azure Service Bus (use azure-service-bus), Azure Event Grid (use azure-event-grid).

The on-ramp for any Built GTM analyst skill when your tools are not connected yet. Tells you exactly what to paste or upload to run a given analysis today, in plain language, then hands the data to the right skill. Trigger on "I haven't connected my tools", "how do I run this without connecting", "what do I paste", "run this on my data", "I have a CSV", "bring my own data", or any moment a connector-dependent skill needs data and nothing is connected.

Turn a private skill you built for your own stack into a clean public version anyone can install and customize, while preserving your personal copy untouched. Strips the company-specific wiring (connectors, CRM field names, proprietary scores, IDs, tuned thresholds, internal vocabulary) and abstracts it into a documented "Customize this for yourself" setup block, keeping the method intact. Trigger on "publish this skill", "make a public version of", "genericize this skill", "share-ready version of", "turn my skill into a community version", "add this to the Built GTM Skills page".

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl — "what's the balance of <wallet>", "look up transaction <sig>", "token balance for <account>", "check this address on mainnet/devnet". End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, security checklists, and JSON-RPC curl lookups against public clusters. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.