Loading...
Loading...
Found 1,465 Skills
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).
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection
Agent skill for automation-smart-agent - invoke with $agent-automation-smart-agent
Set up and maintain hk git hook manager in any repository. Use when adding pre-commit hooks, configuring linters, setting up code quality automation, working with hk.pkl, or maintaining existing hook configurations. Triggers on tasks involving hk, git hooks, pre-commit checks, commit-msg validation, or linting pipelines.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, and transactional-email workflows. Trigger on phrases like "Loops API", "Loops SDK", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Generate enterprise-grade documentation for NetSuite SDF projects. Analyze scripts, object XML files, `manifest.xml`, and SuiteQL queries to produce README.md, architecture diagrams (Mermaid/ASCII), deployment guides, and troubleshooting tables. Can integrate with post-deployment documentation workflows when automation (for example, hooks) is available.
Command-line interface for n8n workflow automation platform. Manages workflows, executions, credentials, variables, and tags. Based on n8n Public API v1.1.1 (n8n >= 1.0.0).
Elastic Email integration. Manage Users, Contacts, Campaigns, Automations, Suppressions, Domains and more. Use when the user wants to interact with Elastic Email data.
Jamie platform help — bot-free AI meeting note-taker, REST API with personal and workspace keys, webhook automations, CRM sync to HubSpot/Salesforce/Attio, MCP server for Claude/ChatGPT/Cursor. Use when setting up Jamie for a sales team, connecting Jamie webhooks to Make.com or a custom endpoint, pulling meeting transcripts and summaries via Jamie API, syncing Jamie action items to Asana or CRM, troubleshooting Jamie not recording or missing speakers, comparing Jamie pricing tiers, or configuring Jamie speaker recognition. Do NOT use for choosing between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
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).
Automate infrastructure, CI/CD, and deployment workflows. USE when building pipelines, environment automation, infrastructure as code, or deployment procedures.
Designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.