Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Marketing & growth
Scan an AgentMail inbox for newsletter signals using configurable keyword campaigns. Extracts matched keywords, context snippets, and company mentions from incoming emails. Use for monitoring accounting industry newsletters for buying signals like acquisitions, migrations, and staffing news.
Use when a website needs paid traffic planning: campaigns, audience hypotheses, UTM maps, landing requirements, creative briefs, budget placeholders, and SEO/ads handoffs. Planning only; never launch campaigns, spend budget, or mutate ad accounts without explicit approval.
Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists.
Professional Markdown to WeChat Official Account (公众号) publisher with visual style presets. Use this skill whenever the user wants to: publish an article to WeChat, create a 公众号 draft, format a blog post or technical tutorial for WeChat, apply a visual style to Markdown, or says anything like "发布到微信", "推送到公众号", "微信文章", "publish to WeChat", "WeChat draft", "公众号推文", "wechat article", "微信公众号". Also trigger when the user asks to convert Markdown to a styled HTML document for WeChat, even if they don't say "publish" explicitly. Also trigger for translation/repost requests: "全文翻译", "转载", "translate and publish", "repost", or when the source article is in English and the user wants to publish it to WeChat. Also trigger for "视频号", "短视频", "竖屏视频", "生成视频", "video", "short video", or "WeChat Channels". This skill handles credentials, image uploads, 13 style presets (3 core + 7 extend + unlimited custom), automatic cover generation, full-article translation, and draft creation end-to-end.
Use this skill whenever creating outreach — a cold email, a LinkedIn message, a follow-up, or a multi-step sequence — for a company, a contact, a list, or a signal. Use it even when the user doesn't say "outreach": any request to write to, contact, message, or get in front of a prospect or account goes through here. Covers picking the hook, matching the org's voice, choosing the sequence shape, and staging everything for approval. Trigger phrasings: "reach out to", "draft outreach", "email this company", "message this prospect", "follow up with", "build a sequence", "contact these visitors". Also use it for strategic outreach questions ("how should our cold emails sound", "what cadence should we run") — the output is then a point of view grounded in the org's saved voice, not a sequence.
Reddit account cultivation for indie developers. Uses AppleScript to control real Chrome — undetectable by anti-bot systems. Checks karma, finds rising posts, drafts comments, and posts directly. Triggers on "/reddit-cultivate", "check my reddit", "reddit maintenance", "find reddit opportunities", "build reddit karma".
Scrape and search Reddit posts using Apify. Use when you need to find Reddit discussions, track competitor mentions, monitor product feedback, discover pain points, or analyze subreddit content. Supports keyword filtering, time-based searches, and subreddit-specific queries.
Design and audit referral, invite, affiliate, ambassador, creator, team-invite, waitlist, viral loop, reward, attribution, fraud-control, promotion, and lifecycle referral systems for SaaS, mobile apps, games, marketplaces, developer tools, and communities. Use when creating or improving referral programs that should grow users or revenue without spam, fake scarcity, abuse, or trust damage.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.
Analyze and improve retention cohorts for SaaS, mobile apps, games, developer tools, marketplaces, subscriptions, content products, and communities including activation cohorts, D1/D7/D30, weekly/monthly retention, rolling retention, resurrection, churn, segment bias, lifecycle events, monetization impact, cohort dashboards, and experiment readouts. Use when retention looks weak, confusing, misleading, or needs an action plan.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see tool-programmatic-seo. For adding structured data, see tool-schema-markup.
Mixmax platform help — sequences, email tracking, one-click meetings, rules engine, dialer, AI Compose, Salesforce/HubSpot integration, polls, reporting. Use when Mixmax sequences aren't sending, rules or automations aren't firing, Salesforce or HubSpot sync is broken, scheduling links aren't working, open/click tracking seems inaccurate, or Mixmax emails are landing in spam. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), meeting scheduling strategy (use /sales-meeting-scheduler), email tracking strategy (use /sales-email-tracking), or connecting Mixmax to other tools via Zapier (use /sales-integration).
Reply.io platform help — multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp), Jason AI SDR, B2B database, email warmup, deliverability tools, unified inbox, analytics, Salesforce/HubSpot integration, agency features. Use when Reply.io emails are landing in spam, sequences aren't getting replies, Jason AI isn't handling responses correctly, warmup isn't improving sender reputation, or Reply.io data isn't syncing to your CRM. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Reply.io to other tools via Zapier (use /sales-integration).
Seismic platform help — Enablement Cloud, content management, Learning & Coaching, Aura AI, Digital Sales Rooms, Meeting Intelligence, LiveSend, LiveDocs, Programs, Seismic Exchange, API & integrations. Use when reps can't find the right content in Seismic, Learning paths have low completion rates, Digital Sales Rooms aren't getting buyer engagement, LiveSend links aren't being opened, LiveDocs templates are breaking, enablement programs aren't moving the needle, or Seismic CRM sync is out of date. Do NOT use for general sales content strategy (use /sales-content), sales coaching frameworks (use /sales-coaching), cross-platform deal room strategy (use /sales-deal-room), or connecting tools via Zapier (use /sales-integration).
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
Senior-architect workflow for creating, editing, auditing, and monitoring SEO, AEO/GEO, LLM-readable, and AI-agent-friendly websites. Use when the user asks about SEO, technical SEO, organic visibility, AI search visibility, ChatGPT/Claude/Perplexity/Gemini readiness, robots.txt, sitemap.xml, llms.txt, schema.org/JSON-LD, canonical/noindex rules, crawl/indexation issues, Search Console/Bing Webmaster monitoring, server-log bot tracking, or making a site discoverable, quotable, machine-readable, and usable by AI agents.
Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass/fail reports.
Audit a web page, or crawl a whole site, for SEO and AEO gaps (crawlability, on-page, structured data, Core Web Vitals, AI-crawler access, answer extractability), then write a prioritized fix report and a long-term search and AI-visibility plan. Use when the user says "audit the SEO of <url>" (including a localhost URL), "check SEO before I deploy", "crawl my site for SEO issues", "why isn't this page ranking", "is my site ready for AI search or ChatGPT", "check my robots.txt for AI bots", or "did my SEO fixes land".
Collect and normalize search-demand inputs for public site projects before semantic-core work. Use when a UI/UX or SEO project needs seed keywords, SERP snapshots, autocomplete ideas, People Also Ask, related searches, or a dry-run keyword harvest with approval-gated external search APIs.
Configure SERP/search-demand source settings before keyword harvesting. Use when a UI/UX, SEO, or site project needs a user-facing source setup gate, OpenSERP self-host settings, proxy provider/API-key fields such as AKE, checkbox selection of Google/Yandex/Bing/DuckDuckGo/Ecosia/Baidu/manual sources, paid-proxy/budget limits, approval notes, or preflight checks before `serp-keyword-harvester` sends external queries.
Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.
Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.
Interview the user in ten questions or fewer and produce a social-context.md file that captures who they are, who they are talking to, what they post about, and what they refuse to post. Covers LinkedIn, X (Twitter), Instagram, Threads, TikTok, and YouTube — the interview decides which of those platforms actually matter. Use when the user says "set up my social context", "onboard me", "set up my socials", or "create my social profile". Every other skill in this collection reads social-context.md for brand voice and setup, so this is the skill to run first. Re-running it updates the existing file section by section and never overwrites the user's manual edits without asking.
Design deterministic technical SEO and schema.org guidance for crawlable public pages. Use this skill when the user asks for title and meta description rules, canonical and hreflang tags, JSON-LD schema, NewsArticle, Article, TechArticle, BreadcrumbList, WebSite, Organization, Person, OpenGraph, Twitter cards, sitemap, news-sitemap, RSS, robots.txt, llms.txt, publisher logo, ImageObject, or metadata templates that must match visible content.
Route high-level Twitter/X automation setup, readiness, starter-menu, and ambiguous workflow requests to independent flat peer skills after ThreadWave checks. Use for start ThreadWave, open ThreadWave, show the ThreadWave menu, or an exact standalone `threadwave` or `tw` request, plus Twitter automation setup, readiness, repair, and workflow selection. Do not use when the request already clearly asks to create/post tweets, create/send replies, or run the daily agent; activate twitter-post, twitter-reply, or twitter-agent directly. 中文：用于启动 ThreadWave、打开 ThreadWave 菜单、单独输入 `threadwave` 或 `tw`、推特自动化安装、就绪检查、修复和模糊工作流路由；明确的发推、回复或日常代理请求应直接使用对应的平级技能。
Design and audit usage-based pricing, metering, quotas, credits, overages, spend controls, billing events, cost drivers, value metrics, free allowances, invoices, expansion paths, abuse controls, and customer trust for SaaS, APIs, AI products, infrastructure tools, developer platforms, marketplaces, and consumption businesses. Use when pricing is tied to seats, usage, credits, API calls, storage, compute, messages, tokens, transactions, or metered value.
Generate videos from text prompts or images using each::sense AI. Create cinematic clips, product demos, social media reels, animations, and motion graphics. Supports text-to-video and image-to-video with audio. 8 specialized models including veo-3, kling-3-0, and sora-2-pro. Use for: social media content, product videos, trailers, animations, storytelling, marketing clips. Triggers: generate video, create video, text to video, ai video, video generation, image to video, animate image, make video, video from text, ai animation, motion, clip
Use when planning Google Search Console, Yandex Webmaster, Bing Webmaster, sitemap submission, verification records, ownership checks, and post-launch indexing monitoring. Planning only; do not submit, verify, or mutate webmaster accounts without explicit approval.
Capture a website and create a HyperFrames video from it. Use when: (1) a user provides a URL and wants a video, (2) someone says "capture this site", "turn this into a video", "make a promo from my site", (3) the user wants a social ad, product tour, or any video based on an existing website, (4) the user shares a link and asks for any kind of video content. Even if the user just pastes a URL — this is the skill to use.
Reviews and rewrites WordPress.org plugin readme.txt files for maximum quality. Use this skill whenever a user pastes, uploads, or references a WordPress plugin readme.txt, or asks to improve, audit, review, score, or optimize a plugin's WordPress.org listing page. Also trigger when the user says things like "make my plugin page better", "optimize my readme", "help me rank higher on WordPress.org", or "review my plugin listing". Always run the full audit + rewrite workflow unless the user explicitly asks for only one part.
Writing clone engine (Profile edition) - first initialize and generate your style Profile, then create WeChat official account / self-media content in your style. **Trigger scenarios**: - The user asks to write a WeChat official account article or self-media content - The user mentions "in my style", "write like me" - The user asks to remove the AI flavor and improve the writing style - The user wants to initialize/update their style Profile **Core capabilities**: - Supports multiple named Profiles: continuously add new ones without overwriting existing style assets - Initialize on first use: distill a style Profile + sample anchors from reference articles - Actively gather context first (repository + memory + material library), then write - Judge whether context is sufficient first, and only fill gaps with Socratic questioning when it is not - Single-threaded writing by default (the main agent completes the whole process in one thread, for more stable style) - Optional multi-threaded mode: generate three viral-structure drafts in parallel, then score and pick the best or merge in a controlled way - Avoid the "AI flavor" and keep a sense of authenticity and conversation - Automatic iteration: update the Profile with new reference articles/feedback
WeChat Official Account article publishing tool. Use the wxgzh CLI to publish Markdown articles to the Official Account drafts. Triggered when the user wants to publish an Official Account article, configure AppID/AppSecret, generate a cover image, convert Markdown to HTML, or manage multiple accounts.
X (Twitter) post comment analysis tool. Enter a tweet link or tweet ID to fetch first-level comment data, with cursor-based paging and four-dimension sentiment analysis (positive/negative/needs/competitors). Use when the user needs to view X (Twitter) tweet comments, analyze tweet sentiment, or understand user feedback. Trigger words: X comments, Twitter comments, tweet comments, X post comment analysis, comment lookup, comment analysis, comment sentiment, see comments, twitter comments, X tweets.
Break down and lay out user-provided articles, notes, tutorials, SOPs, checklists, web content or local documents into 3:4 multi-page Xiaohongshu image-text HTML. By default generates a complete self-contained HTML with more than 6 pages at 1080×1440 each that can be screenshotted page by page; supports 62 brand design styles and, before starting, offers the user matching style candidates and 6/7/8/9-page options to choose from. For requests such as "make Xiaohongshu image-text", "turn content into Xiaohongshu cards", "generate multi-page Xiaohongshu HTML", "make 3:4 knowledge cards", "lay out an article into a Xiaohongshu image set", "make tutorial image-text", "make screenshottable HTML".
Operate 蚁小二 multi-platform content distribution via the yxer CLI: account lookup, asset upload, pre-publish preparation, payload validation, cloud/local publishing, draft saving, material registration, publish-record troubleshooting, and skill sync.
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises), and LinkedIn content (pain-point posts, hiring announcements) — then aggregates results into a deduplicated leads.csv with the signal source, evidence URL, and detection timestamp per row. Split-schedule architecture — Apify Actor Tasks pull raw data on their own cadence, a Claude-side aggregation task normalizes, deduplicates against a blacklist, and appends new leads with a weekly-idempotent guard. Use when the user says "find companies with buying signals", "detect intent signals for outbound", "set up a weekly lead pipeline", "monitor hiring signals for lead gen", "track startup funding leads", "find LinkedIn buying signals", "schedule Apify Actors for prospecting", "build a signals-based lead list", or "set up buying-intent monitoring for my ICP".
Design, implement, debug, and harden integrations between AI agents and Bitrix24 REST API (webhooks, OAuth 2.0, scopes, events, batch, limits, REST 3.0). Use whenever the user wants to connect an AI assistant or agent to a Bitrix24 portal or act on one — for example create or update a lead, deal, contact or company; find duplicate contacts; log a call or activity; move a deal stage; generate a quote or invoice; attach products; send a chat message or user notification; build a chat-bot; manage tasks, projects or templates; upload files; run a business process; sync offline events; pick webhook or OAuth; or resolve Bitrix24 API errors (WRONG_AUTH_TYPE, QUERY_LIMIT_EXCEEDED, expired_token) and performance issues — even if Bitrix24 is not named explicitly. Do NOT use for other CRMs (Salesforce, HubSpot, amoCRM, Pipedrive, Zoho) — those have their own skills.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.