Loading...
Loading...
Found 123 Skills
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.
Help desk and customer service platform comparison and selection — choosing the right ticketing and support platform (Zendesk, Freshdesk, Intercom, Help Scout, Zoho Desk, Front, Hiver, Jira Service Management, Gorgias, Tidio, HappyFox, Kustomer, LiveAgent, Crisp, Pylon). Use when comparing help desk platforms for a support team, deciding between Zendesk vs Freshdesk vs Intercom, evaluating which support tool fits your team size and budget, choosing a help desk for e-commerce or SaaS, migrating from one help desk to another, or wondering which platform has the best AI or automation. Do NOT use for platform-specific configuration (use /sales-zendesk or the relevant platform skill), CCaaS/contact center selection (use /sales-ccaas-selection), or live chat strategy (use /sales-live-chat).
Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira/Confluence app that "stopped working". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word "Forge" but describe a Jira panel or Confluence macro acting up.
Search and retrieve context from Airweave collections. Use when users ask about their data in connected apps (Slack, GitHub, Notion, Jira, Confluence, Google Drive, Salesforce, databases, etc.), need to find documents or information from their workspace, want answers based on their company data, or need you to check app data for context to complete a task.
Universal fallback for executing actions across 1,000+ apps when no other skill is available. Use this skill ONLY when user requests an action on an app/service not covered by other skills (e.g., Notion, Asana, Trello, HubSpot, Airtable, Linear, Monday, Zendesk, Intercom, Stripe, Shopify, QuickBooks, Zoom, Microsoft 365, Dropbox, Box, Figma, Jira, Confluence, etc.). Do NOT use if another skill already handles the service. Triggers on requests to connect to external apps, execute actions on third-party services, or when user asks "can you actually do X" for an unsupported service.
Connect to any external app and perform actions on it. Use when the user wants to interact with external services like Slack, Linear, HubSpot, Salesforce, Jira, GitHub, Google Sheets, or any other app — send messages, create tasks, sync data, manage contacts, or perform any API operation.
6 production-ready project management skills for Atlassian users: senior PM with portfolio management, scrum master with velocity forecasting, Jira expert with JQL mastery, Confluence expert, Atlassian admin, and template creator. MCP integration for live Jira/Confluence automation. Works with Claude Code, Codex CLI, and OpenClaw.
Autonomous development agent that picks tasks from a project board (Jira, ClickUp, GitHub Issues), explores the codebase, implements the solution, opens a PR, and notifies the team. Configurable per-project via project files in ~/.config/delivering-tickets/projects/. Use this skill when the user asks to "work on a ticket", "pick up a task", "implement issue X", "work autonomously on the board", "take the next task", or any variation of autonomous task execution from a project board. Also triggers when the user mentions delivering-tickets, project configuration, or wants to set up autonomous development workflows for their team. Available commands: /delivering-tickets (start), /delivering-tickets:check (check replies), /delivering-tickets:status (workflow status), /delivering-tickets:setup (verify environment), /delivering-tickets:project (manage projects). Do NOT use for general coding without a ticket, standalone code reviews, project setup without a board configured, or questions unrelated to task execution from a project board.
Build apps that integrate with external services via Membrane. Use when the user wants to add integrations to their product — let their customers connect to Slack, HubSpot, Salesforce, GitHub, Google Sheets, Jira, or any other app, execute actions, sync data, or handle webhooks. Covers backend token generation, frontend connection UI, running actions, data collections, and AI agent tooling.
Sets up and operates Airbyte Agent Connectors — strongly typed Python packages for accessing 51+ third-party SaaS APIs through a unified entity-action interface. Supported services include Salesforce, HubSpot, Stripe, GitHub, Slack, Jira, Shopify, Zendesk, Google Ads, Notion, Linear, Intercom, Gong, and 36 more connectors spanning CRM, billing, payments, e-commerce, marketing, analytics, project management, helpdesk, developer tools, HR, and communication platforms. Make sure to use this skill when the user wants to connect to any SaaS API, install an airbyte-agent connector package, integrate third-party service data into a Python application or AI agent, query or search records from any supported service, or configure Airbyte MCP tools for Claude. Covers Platform Mode (Airbyte Cloud) and OSS Mode (local Python SDK).
Beads (bd) distributed git-backed issue tracker for AI agents: hash-based IDs, dependency graphs, worktrees, molecules, sync, GitLab/Linear/Jira. Keywords: bd, beads, issue tracker, git-backed, dependencies, molecules, worktree, sync, AI agents.
Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.