Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Create engaging, authentic LinkedIn posts like a Top Voice. Use this skill when asked to write LinkedIn content, social media posts for LinkedIn, professional thought leadership content, or help with LinkedIn engagement strategy. Triggers include requests for LinkedIn posts, professional social content, thought leadership pieces, or viral/engaging LinkedIn content.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like “the xlsx in my downloads”) — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Generate webpages from a description — landing pages, portfolios, event pages. View, edit, and share with one click via YouMind. Use when user wants to "create webpage", "make website", "generate page", "landing page", "创建网页", "生成页面", "ウェブページ作成", "웹페이지 만들기".
This skill provides Zig 0.15.x API guidance and should be used when writing or reviewing Zig code. It ensures correct usage of Zig 0.15 APIs, preventing common mistakes from using outdated 0.11/0.12/0.13/0.14 patterns. Essential for ArrayList, std.Io.Writer/Reader (Writergate), HTTP client, Ed25519, JSON, and type introspection APIs.
Delegate work to A2A (Agent2Agent) agents from the command line with the `a2a` CLI (github.com/a2aproject/a2a-cli). Use when you need to hand a task to a specialized or remote agent, fetch an agent's card, send a message to an agent at a URL, stream or poll a running task, or check, list, resume, or cancel an A2A task. Not for building or serving an A2A agent, or for calling non-A2A HTTP APIs.
Use when the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions “A/B test,” “split test,” “experiment,” “test this change,” “variant copy,” “multivariate test,” “hypothesis,” “should I test this,” “which version is better,” “test two versions,” “statistical significance,” “how long should I run this test,” “growth experiments,” “experiment velocity,” “experiment backlog,” “ICE score,” “experimentation program,” or “experiment playbook.” Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
An integrated academic writing skill with two modes. (1) Formatting and polishing: paragraph-level academic editing, terminology consistency, formula normalization, and logic improvement, with output saved to the draft directory. (2) Humanization: humanize Chinese and English text, reduce formulaic phrasing, and optionally run a detection script. When polishing or rewriting the body of a paper, apply the humanizer-zh style rules by default. See the repository root README.md for the default output directory and academic integrity agreement.
Use when authoring or modifying a Datex Studio action (configurationTypeId=18, *-footprintFlow.json suffix) on a branch — server-tier transactional flow for CRUD, status updates, and any operation requiring atomicity. Owns the action-vs-function decision, the "Transaction must begin first" diagnostic (silent-swallow root cause), and the error-handling-is-load-bearing rule (transaction propagation). Triggers: "create an action", "write an xxx_action", "add a new action", "transactional flow", "CRUD action", "server-side action", "Transaction must begin first".
Inspect existing alerts, notifications, and automated actions in Fabric via read-only REST calls using `az rest` CLI. **Invoke this skill** whenever the user wants to: (1) list existing alerts in a workspace, (2) inspect how an alert or notification is configured, (3) read and decode an Activator/Reflex definition (ReflexEntities.json), (4) list rules, sources, and actions behind an alert, (5) understand why an alert fires or what action it takes. **Invoke this skill before answering questions** about an Activator/Reflex item in a Fabric workspace — the listing, lookup, and decoding workflows are part of this skill, not preamble to it. Triggers: "show my alerts", "what alerts do I have", "show me all activators", "inspect this alert", "show me the rule", "show me the action", "show me the source", "get reflex definition", "list activators", "list alerts", "list reflex items", "show activator items", "activator details", "find activator named", "inspect Power BI source", "metric definition behind this alert".
Wire Redis Agent Memory into an existing agent with redis-iris so it remembers users across sessions. Asks five questions (what to remember, what to share, what never to keep, how long to keep it, whether users can be forgotten), writes the answers to service.yaml, provisions the service from the terminal with `iris agent-memory service create`, then wires recall and write-back into the agent's turn in any framework. Use when the agent forgets users, uses InMemoryStore or a checkpointer only, keeps memory in a dict or local DB, or the user asks for long-term memory, recall, or right-to-erasure.
This skill helps users extract structured product listings from Amazon, including titles, ASINs, prices, ratings, and specifications. Use this skill when users want to search for products on Amazon, find the best selling brand products, track price changes for items, get a list of categories with high ratings, compare different brand products on Amazon, extract Amazon product data for market research, look for products in a specific language or marketplace, analyze competitor pricing for keywords, find featured products for search terms, get technical specifications like material or color for product lists.
Core AWS services for application developers. Covers S3 (storage, presigned URLs, lifecycle), Lambda (functions, layers, cold starts), IAM (roles, policies, least privilege), DynamoDB (single-table design, GSI/LSI, streams), SQS/SNS (queues, topics, fan-out), CloudFront (CDN, caching), RDS/Aurora (Postgres/MySQL, connection pooling), ECR/ECS/Fargate (containers), Route 53 (DNS), Secrets Manager, and CDK v2 (TypeScript IaC, constructs, stacks, testing). Use when building AWS infrastructure, writing CDK stacks, configuring IAM policies, designing DynamoDB tables, setting up Lambda functions, creating S3 presigned URLs, deploying containers on ECS/Fargate, or configuring CloudFront distributions.
Use when the user asks to look into, investigate, or research a bug, an idea, or a question before anything is built, or to audit or assess existing code or a repo. Also runs nested under write-ticket or review remediation. Returns findings in chat; writes no tickets or code.
Use when building or restyling devtools-style Vue 3 UIs with @antfu/design — wiring the composable UnoCSS preset, using the semantic token vocabulary (bg-base, color-base, badge-color-*, color-scale-*), choosing prefixed primitives (DisplayBadge, ActionButton, DisplayFilePath, OverlayModal, …), and keeping light/dark contrast and the "anti-slop" rules. Reach for it whenever generating or reviewing UI in a project that depends on @antfu/design.
Manage App Clips and App Clip default experiences using the `asc` CLI tool. Use this skill when: (1) Listing App Clips for an app: "asc app-clips list --app-id ID" (2) Listing default experiences for an App Clip: "asc app-clip-experiences list --app-clip-id ID" (3) Creating a default experience: "asc app-clip-experiences create --app-clip-id ID [--action OPEN|VIEW|PLAY]" (4) Deleting a default experience: "asc app-clip-experiences delete --experience-id ID" (5) Listing experience localizations: "asc app-clip-experience-localizations list --experience-id ID" (6) Creating an experience localization: "asc app-clip-experience-localizations create --experience-id ID --locale CODE [--subtitle TEXT]" (7) Deleting an experience localization: "asc app-clip-experience-localizations delete --localization-id ID" Trigger phrases: "app clip", "app clips", "clip experience", "clip localization", "default experience", "OPEN action", "VIEW action", "PLAY action", "App Clip card", "App Clip subtitle"
Manage App Store app info and per-locale metadata using the `asc` CLI tool. Use this skill when: (1) Listing app info records: "asc app-infos list --app-id ID" (2) Updating app categories: "asc app-infos update --app-info-id ID --primary-category 6014" (3) Browsing categories: "asc app-categories list --platform IOS" (4) Listing per-locale app metadata: "asc app-info-localizations list --app-info-id ID" (5) Creating a new locale entry: "asc app-info-localizations create --app-info-id ID --locale en-US --name 'My App'" (6) Updating name, subtitle, or privacy URLs: "asc app-info-localizations update --localization-id ID --name 'New Name'" (7) Deleting a locale entry: "asc app-info-localizations delete --localization-id ID" (8) Navigating to age rating: "asc age-rating get --app-info-id ID" (use getAgeRating affordance) (9) User says "update app name", "update subtitle", "set privacy policy URL", "list app info", "manage app metadata", "set category", "update category"
Manage App Store Connect authentication using the `asc` CLI tool. Use this skill when: (1) Logging in with an API key: "asc auth login", "save my credentials", "set up authentication" (2) Managing multiple accounts: "asc auth list", "switch account", "use work account", "add another account" (3) Switching the active account: "asc auth use NAME", "switch to personal account" (4) Logging out: "asc auth logout", "remove credentials", "remove account" (5) Verifying current credentials: "asc auth check", "which account am I using?" (6) Updating account settings: "asc auth update --vendor-number", "save my vendor number" (7) Explaining the credentials file format (~/.asc/credentials.json) (8) Troubleshooting 401 auth errors or "missing credentials" errors
Manage beta app review submissions and review contact details for TestFlight external testing using the `asc` CLI tool. Use this skill when: (1) Submitting a build for beta app review: "asc beta-review submissions create --build-id ID" (2) Checking beta review submission status: "asc beta-review submissions list --build-id ID" (3) Getting a specific submission: "asc beta-review submissions get --submission-id ID" (4) Getting beta review contact details: "asc beta-review detail get --app-id ID" (5) Updating beta review contact info or demo account: "asc beta-review detail update --detail-id ID ..." (6) Managing the per-locale **Beta App Description** and feedback metadata shown to TestFlight testers: "asc beta-app-localizations {list,get,create,update,delete}" (7) User says "submit for beta review", "TestFlight review", "beta review status", "beta review contact", "external testing review", "beta app description", "TestFlight description", or any beta app review task
Archive and export Xcode projects to IPA/PKG using the `asc` CLI tool, with optional upload to App Store Connect. Use this skill when: (1) Archiving an Xcode project: "asc builds archive --scheme MyApp" (2) Exporting an archive to IPA or PKG for distribution (3) Archive + export + upload in one step: "asc builds archive --scheme MyApp --upload --app-id ..." (4) User says "archive my app", "build for TestFlight", "export IPA", "archive and upload", "build and distribute", "create an IPA from my Xcode project" (5) User wants to go from Xcode project to TestFlight without manually running xcodebuild
Upload IPA/PKG builds to App Store Connect and manage the full build distribution workflow. Use this skill when: (1) Uploading a build: "asc builds upload --app-id ... --file MyApp.ipa ..." (2) Checking or listing build upload records: "asc builds uploads list/get/delete" (3) Linking a build to an App Store version before submission: "asc versions set-build" (4) Adding or removing a beta group from a build for TestFlight distribution (5) Setting TestFlight "What's New" notes: "asc builds update-beta-notes" (6) Setting Apple's export-compliance answer (ITSAppUsesNonExemptEncryption): "asc builds set-encryption-compliance" (7) User says "upload my build", "distribute to TestFlight", "set what's new", "link build to version", "missing compliance", "encryption compliance", "ITSAppUsesNonExemptEncryption"
Manage App Store Connect code signing resources using the `asc` CLI tool. Use this skill when: (1) Managing bundle identifiers — register, list, or delete (`asc bundle-ids`) (2) Managing signing certificates — create from CSR, list, or revoke (`asc certificates`) (3) Registering or listing test devices (`asc devices`) (4) Managing provisioning profiles — create, list, or delete (`asc profiles`) (5) Setting up the full code signing chain for CI/CD pipelines (6) User says "set up signing", "create a profile", "register my device", "revoke cert", "list certificates", "create bundle id", or any code-signing related task
Manage In-App Purchases with the `asc` CLI: list/create/update/delete/submit/unsubmit IAPs, manage localizations and pricing, handle IAP offer codes, and upload or remove review screenshots and 1024x1024 promotional images. Trigger on requests to create or submit IAPs (including a first IAP, which must go to review with an app version), manage redemption codes, change pricing, edit review assets, or maintain IAP metadata.
Complete domain knowledge for VeBetterDAO's auto-voting and relayer system. Use when working on relayer dashboard, relayer node, auto-voting contracts (XAllocationVoting, VoterRewards, RelayerRewardsPool), or anything related to relayers, auto-voting, gasless voting, or relayer rewards. Triggers on: relayer, auto-voting, autovoting, gasless voting, relayer rewards, RelayerRewardsPool, castVoteOnBehalfOf, castNavigatorVote, relayer dashboard, relayer node, veDelegate comparison.
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
Reviews axum web framework code for routing patterns, extractor usage, middleware, state management, and error handling. Use when reviewing Rust code that uses axum, tower, or hyper for HTTP services. Covers axum 0.7+ patterns including State, Path, Query, Json extractors.
Runs the Azure SQL Database container locally (Private Preview): the real PaaS engine where SERVERPROPERTY('EngineEdition') returns 5. This is NOT the SQL Server image mcr.microsoft.com/mssql/server. Use when a user wants to "run Azure SQL locally", "add a local SQL database", "add SQL Server to my docker compose", "spin up a local mssql container", "local SQL for development or CI", "connect with sqlcmd", "use Podman for SQL", "SQL container won't start", "Microsoft Entra authentication on the container", "MSSQL_AAD_CLIENT_ID", or asks "what's the connection string". Use even when the user does not name the container. If you were about to use mcr.microsoft.com/mssql/server, stop and use this skill instead. Hub skill: owns the shared references and routes to the task skills for compose, CI, seeding, vectors, and connection strings.
Expert in traditional Chinese baby naming. Based on the baby's birth chart (birth date and time), gender and surname, combined with yin-yang and five-elements theory and traditional Chinese culture, recommends names with auspicious meanings that match the five elements, or evaluates the merits of an existing name. Use when users request: (1) naming a newborn baby based on Chinese astrology, (2) analyzing name compatibility with birth date and time (八字), (3) suggesting names that balance the five elements (五行), (4) creating names with cultural and poetic significance, (5) evaluating an existing name's quality and compatibility.
Use when authoring or modifying a Datex Studio backend test (configurationTypeId=24, *-backendTest.json suffix) on a branch — mocha test suite with four hook flows (before_suite/after_suite/before_each/after_each) and a testCaseFlows array. Owns the action-as-test refactor pattern and the missing runtime-mock seam as Platform TODO. Triggers: "create a backend test", "create an xxx_test", "add a test suite", "mocha test suite", "add a test case to xxx_test", "modify a backend test", "refactor xxx_action into a backend test", "backend test won't run", "before_suite never fires", "suite hooks not firing".
Research a specific competitor across their website, reviews, ads, social presence, and pricing — then produce a structured sales battlecard with positioning traps, objection handlers, landmine questions, and win/loss themes. Chains web research, review mining, and ad intelligence. Use when sales needs competitive ammo or when entering a new market with established incumbents.
Use when building or rebuilding a page, header, footer, or template on an Oxygen 6 (Jenga) site, or when a previous attempt produced a blank page, one raw HTML block, or 'Unknown element'. Hands the agent the Oxygen 6 element schemas and the Template Content Area rule. Not for Oxygen Classic.
Ascend NPU CANN Toolkit + Kernels + NNAL installation and deployment skill. Supports two methods: installing from the run package downloaded from the official site, and extracting from a Docker image. Covers the whole process of driver checks, package download, installation, environment variable configuration, and verification. Invoke when the user needs to install the full CANN component set or a specific CANN version to a custom path.
Generate demo animation HTML pages with a sidebar narrative and a 3D card carousel. Supports multiple interaction modes such as scroll paging, Coverflow 3D and Focus expansion, with built-in effects like mode switching (e.g. transport/tunnel), highlighter markup and watermark icons. Suited to protocol flow demos, product feature showcases and step-by-step walkthroughs.
Manages Cargo.lock file updates and resolves --locked flag issues in CI/CD. Triggers when user mentions: - "cargo test --locked failed" - "cannot update the lock file" - "Cargo.lock is out of date" - "PR failed with --locked error" - "fix Cargo.lock"
Due diligence checklists for A-share investments and M&A transactions. Adapted from the original dd-checklist skill for Chinese market due diligence requirements, regulatory filings, and business practices. Triggers on "A股尽调清单", "尽调清单", "due diligence China", "DD checklist A-share", "尽调checklist [company]", or "due diligence questions [company]".
Debug Clerk-delivered SMS (phone verification codes, OTPs) using the sms.* Application Logs. Understand the delivery lifecycle — sms.accepted, sms.delivered, sms.failed, sms.undeliverable, sms.unconfirmed — read the normalized failure reason, and follow one message across events by its trace. Use when a user reports "I never got the code", a phone number won't verify, or SMS delivery to a country/carrier looks broken.
Tambo CLI reference for project setup and component installation. Agent-friendly with non-interactive mode and exit codes. Use when running tambo init, tambo add, npx tambo commands, or browsing the component library. For guided project creation with tech recommendations, use start-from-scratch skill. For adding Tambo to existing projects, use add-to-existing-project skill.
Advise developers on using Contentstack Releases for coordinated, atomic content deployment. Cover release creation, item management, staged deployment, webhook storm prevention, and CI/CD integration. Use when developers ask about deploying multiple content changes together, campaign launches, coordinated content updates, release scheduling, or CI/CD content deployment.
Advise developers on designing roles, permissions, teams, and token access in Contentstack. Explain built-in roles, custom roles, permission merging, team-based access, and token capabilities with least-privilege guidance. Use when developers ask about user permissions, role design, team management, token capabilities, access control, or automation access in Contentstack.
Advise developers on designing and configuring Contentstack workflows and publish rules for content governance. Cover stage design, transition restrictions, approval flows, publish governance, automation hooks, and common pitfalls. Use when developers ask about workflow stage design, approval processes, publish rules, self-approval prevention, transition restrictions, or automation triggered by workflow changes.
Run code quality checks (ruff, mypy, pytest) and optionally simplify code. This skill should be used when the user wants to check code quality, run linters, run tests, or simplify recently modified code. Triggered by /lint, /check, or /code-quality commands.
Set up, index, and manage SocratiCode codebase indexing. Use when the user wants to index a project, check infrastructure health, start/stop file watching, configure context artifacts, troubleshoot indexing issues, manage the code graph, or any SocratiCode administrative task. Activates when the user mentions indexing, setting up search, SocratiCode infrastructure, or managing the codebase index.
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.