Loading...
Loading...
Found 6,171 Skills
Generates production-grade Playwright automation scripts and E2E tests in TypeScript, JavaScript, Python, Java, or C#. Supports local execution and TestMu AI cloud across 3000+ browser/OS combinations and real mobile devices. Use when the user asks to write Playwright tests, automate browsers, run cross-browser tests, test on real devices, debug flaky tests, mock APIs, or do visual regression. Triggers on: "Playwright", "E2E test", "browser test", "run on cloud", "cross-browser", "TestMu", "LambdaTest", "test my app", "test on mobile", "real device".
Comprehensive guide to why and how AI agents should use email. Use when evaluating whether an agent needs email, comparing email infrastructure options (AgentMail vs Gmail API vs Resend vs SendGrid vs SES), understanding security risks like prompt injection via email and OAuth credential exposure, or exploring common agent email use cases such as customer support agents, sales outreach, verification flows, and browser automation.
Vitally platform help — Health Scores, Playbooks, Projects, Automation, AI copilot, NPS, Dashboards, REST API. Use when health scores aren't reflecting reality, playbook automations aren't triggering, Salesforce or HubSpot sync is broken, onboarding projects are stalling, NPS surveys aren't reaching users, Vitally AI summaries seem off, custom traits aren't updating via API, or dashboards show stale data. Do NOT use for general customer success strategy (use /sales-customer-success) or survey design methodology (use /sales-customer-feedback).
Read.ai platform help — meeting intelligence with engagement/sentiment analytics, Search Copilot across meetings/email/chat, Ada digital twin, REST API (beta) + MCP Server (`api.read.ai/mcp/`), OAuth auth, webhook automations (`meeting_end` events with HMAC signing), CRM sync to Salesforce/HubSpot, Zapier/n8n workflows, 20+ language transcription. Use when setting up Read.ai webhooks or API integration, connecting Read.ai transcripts to a CRM or data warehouse, configuring Read.ai engagement analytics for a sales team, comparing Read.ai pricing tiers, troubleshooting Read.ai auto-joining meetings without permission, or setting up the Read.ai MCP server with Claude or Cursor. Do NOT use for picking between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Platform-neutral guidance for using Open Browser Use, the open-source Chrome automation stack for AI agents. Use when an agent needs to install, verify, troubleshoot, or operate Open Browser Use through its browser extension, native CLI, JavaScript SDK, Python SDK, Go SDK, or Browser Use style JSON-RPC methods; use for tasks involving real Chrome tabs, user tab claiming, CDP commands, downloads, file choosers, clipboard helpers, or session cleanup.
Use when writing automation tests, functional tests, or any test in Unreal Engine. Also use when the user asks about "UE_LOG", logging, log categories, assertion, check, ensure, verify, DrawDebug, debug draw, console command, profiling, Unreal Insights, stat commands, or debugging techniques. See ue-module-build-system for test module setup, and ue-cpp-foundations for general C++ logging patterns.
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, dogfooding Open Design previews, QA, bug hunts, or reviewing app quality. Prefer local Open Design preview URLs unless the user explicitly asks for external browsing.
Use for any task requiring a real browser: viewing web pages, accessing login-gated sites, operating web UIs, scraping social media (Xiaohongshu/Weibo/Twitter/X, etc.), reading JS-rendered or dynamic pages, bypassing bot detection, form filling, e2e checks, and general web automation. Prefer this over WebFetch whenever the page needs JS execution, authenticated session, interaction, or stealth. Invoke via terminal CLI (`bridgic-browser ...`) or Python SDK (`from bridgic.browser.session import Browser`, `from bridgic.browser.tools import BrowserToolSetBuilder`). Also covers accessibility snapshot refs, CLI-SDK mapping/migration, and generating SDK code from CLI action steps.
SEO & content marketing automation skill suite with keyword research, technical audits, SERP analysis, and content optimization workflows
Mastodon automation — fediverse engagement, content-warned posts, instance-aware community participation, and boost-driven amplification.
CCXT cryptocurrency trading library. Use for cryptocurrency exchange APIs, trading, market data, order management, and crypto trading automation across 150+ exchanges. Supports JavaScript/Python/PHP.
Enables Claude to manage LinkedIn posts, profile, and professional networking through browser automation