Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use this skill any time the user wants to create, design, or produce slide presentations — as standalone files or embedded content. This includes: pitch decks, slide decks, keynote presentations, training materials, project proposals, quarterly reviews, weekly report slides, investor pitches, product launches, team kickoffs, business plans, onboarding decks, strategy presentations, sales pitches, conference talks, and any request involving 'slides' or 'PPT'. Also trigger when: user says 做PPT, 做个汇报, 写个演示文稿, 季度汇报, 竞品分析报告（要PPT）, 产品发布会, 培训材料, 周报. If slides, decks, or presentations need to be produced, use this skill.
Call 200+ curated AI models (GPT, Claude, Gemini, Grok, DeepSeek, Qwen, Kimi, GLM, MiniMax, plus image, video, embedding and rerank models) through APIYI's single OpenAI-compatible gateway at api.apiyi.com. Use this when the user mentions APIYI, API易, api.apiyi.com or an APIYI_API_KEY; wants one API key across multiple model vendors; is repointing an OpenAI, Anthropic or Google SDK base_url at a relay; or asks about APIYI base URLs, model IDs, token groups (分组), pricing, balance (余额), call logs, or gateway error codes.
Organize git changes into clean, atomic commits for better history. Use when the user has accumulated multiple changes and wants to split them into separate, logical commits. Triggers on “atomic commits”, “split commits”, “organize my changes”, “clean commit history”, or when many unrelated changes are staged together.
Audit a spreadsheet for formula accuracy, errors, and common mistakes. Scopes to a selected range, a single sheet, or the entire model (including financial-model integrity checks like BS balance, cash tie-out, and logic sanity). Triggers on "audit this sheet", "check my formulas", "find formula errors", "QA this spreadsheet", "sanity check this", "debug model", "model check", "model won't balance", "something's off in my model", "model review".
Expert knowledge for Azure Carbon Optimization development, including troubleshooting, best practices, security, and integrations and coding patterns. Use when exporting emissions via REST/Python, setting RBAC, or applying Azure Advisor carbon optimization guidance, and for other Azure Carbon Optimization development tasks. Not for Cost Management (use azure-cost-management), Azure Impact Reporting (use azure-impact-reporting), Azure Monitor (use azure-monitor), or Azure Policy (use azure-policy).
Expert knowledge for Azure Confidential Ledger development, including troubleshooting, decision making, architecture and design patterns, limits and quotas, security, integrations and coding patterns, and deployment. Use when configuring Entra authentication, MST payloads, Blob/Cosmos integrations, node attestation, or ARM/Terraform deployments, and for other Azure Confidential Ledger development tasks. Not for Azure Confidential Computing (use azure-confidential-computing), Azure Enclave (use azure-enclave), Azure Key Vault (use azure-key-vault), or Azure Attestation (use azure-attestation).
Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing lab VM images, ARM/CI-CD automation, RBAC/Key Vault security, hub-spoke networking, or quotas, and other Azure DevTest Labs related development tasks. Not for Azure Lab Services (use azure-lab-services), Azure Dev Box (use azure-dev-box), Azure Virtual Machines (use azure-virtual-machines), Azure Virtual Desktop (use azure-virtual-desktop).
Expert knowledge for Azure Extended Zones development including limits & quotas, security, and configuration. Use when registering subs, authoring Azure Policy, deploying Azure Firewall, CMK disk encryption, or quota requests, and other Azure Extended Zones related development tasks. Not for Azure Virtual Network (use azure-virtual-network), Azure Virtual WAN (use azure-virtual-wan), Azure Traffic Manager (use azure-traffic-manager).
Expert knowledge for Azure Managed Lustre development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when sizing AML filesystems, integrating Blob/CSI, tuning AKS clients, securing CMK/root squash, or fixing perf issues, and other Azure Managed Lustre related development tasks. Not for Azure NetApp Files (use azure-netapp-files), Azure Virtual Machines (use azure-virtual-machines), Azure Virtual Network (use azure-virtual-network).
Expert knowledge for Azure AI Metrics Advisor development, including decision making, limits and quotas, security, configuration, integrations and coding patterns. Use when configuring data feeds, tuning anomaly detection, managing alerts/hooks, or calling Metrics Advisor REST/SDKs, and other Azure AI Metrics Advisor related development tasks. Not for Azure AI Anomaly Detector (use azure-anomaly-detector), Azure Monitor (use azure-monitor), Azure Stream Analytics (use azure-stream-analytics).
Expert knowledge for Azure US Government development, including decision-making, architecture and design patterns, security, configuration, integration and coding patterns, and deployment. Use when choosing Azure Gov vs global, meeting FedRAMP/DoD IL5 requirements, using SACA patterns, Gov Marketplace, or sovereign APIs, and for other Azure US Government development tasks. Not for Azure Local (use azure-local), Azure Extended Zones (use azure-extended-zones), Azure Networking (use azure-networking), or Azure Virtual Network (use azure-virtual-network).
Expert knowledge for Azure AI Video Indexer development, including troubleshooting, best practices, decision making, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when configuring live camera analysis, custom AI insights, OpenAI summaries, Video Indexer APIs, or face redaction, and other Azure AI Video Indexer related development tasks. Not for Azure AI Vision (use azure-ai-vision), Azure AI Search (use azure-cognitive-search).
Subscribe to BingX USDT-M perpetual swap WebSocket market data streams including real-time trades, order book depth, K-lines, 24h ticker, latest price, mark price, best bid/ask, and incremental depth. Use when the user asks about real-time swap market data, live price feeds, streaming order books, or WebSocket subscriptions for perpetual futures.
Generates Tianyancha-style company and industry insight dashboards from researched enterprise data. Use when user asks for 天眼查, company lookup, enterprise analysis, hiring analysis, legal risk, financing, shareholders, intellectual property, investments, or industry company comparison.
Create a CawPlan version plan: create a version and optionally populate it with tickets, either from an explicit ticket list or by extracting work items from pasted OKRs/stage goals — deduplicating against the existing backlog and adding a rough, clearly-labeled effort estimate. Use when: the user asks to create a version plan, set up a new release, create a version with goals or tasks, plan a release train, or pastes OKRs/quarterly goals and asks to turn them into a version plan. NOT for: tracking an existing plan, creating standalone backlog tickets outside of a new version plan, querying product info, or metrics.
Help with CDS (Core Data Services) view entity development including data modeling, annotations, associations, compositions, access controls, aggregate expressions, built-in functions, and input parameters. Use when users ask about CDS views, CDS view entities, CDS annotations, CDS associations, CDS compositions, CDS access control, CDS metadata extensions, data modeling in ABAP, define view entity, define root view entity, semantic annotations, UI annotations, or building CDS data models for RAP or analytical scenarios. Triggers include "create a CDS view", "define view entity", "add an association", "CDS annotation", "access control", "composition", "CDS hierarchy", "CDS aggregate", "CDS functions", or "data model".
Run the full git workflow end-to-end without prompting: create a dated branch off the default branch (if needed), stage and commit changes with a descriptive message, push to origin, open a PR (honoring any repo PR template), and monitor CI checks until they pass. Use when the user asks to commit and open a PR, ship a change, push and PR, or run the checkout-commit-push-pr flow.
Grades a repository's GitHub Actions configuration against CI best practices (the CI Score: eleven pass/fail configuration facts computed from the repo's own workflow YAML) and hands back concrete fixes for every gap, ranked by impact and risk, each with an apply-now option and a paste-able agent prompt. Use when: (1) the user asks to grade or score their CI, or audit CI configuration against best practices ("grade my CI", "CI score", "CI best practices audit", "how healthy is my CI config"), (2) re-scoring after workflow changes. Requires a local checkout of the target repository. Do NOT trigger for: CI speed, cost, or wall-clock audits, "why is CI slow", or optimization-opportunity analysis (use ci-speedup); security audits or posture review (ci-score is not a security audit — exactly two rubric checks, action pinning and OIDC token scoping, happen to be security-related); writing new workflows from scratch; non-GitHub-Actions CI.
Automated code review workflow using OpenAI Codex CLI. Implements iterative fix-and-review cycles until code passes validation or reaches the iteration limit. Use when building features requiring automated code validation, security checks, or quality assurance through Codex CLI.
Scaffold or update an Adobe API Mesh configuration (mesh.json) in front of a Commerce app: add GraphQL/OpenAPI sources, extend an existing Commerce GraphQL type with a new field, and wire a cross-source resolver for it. Use when the user mentions API Mesh, mesh.json, extending a Commerce GraphQL type (e.g. adding a field to Order/CustomerOrder/Product), or stitching a runtime action's data into the storefront's GraphQL schema.
Build modern, composable, and accessible React UI components following the components.build specification. Use when creating, reviewing, or refactoring component libraries, design systems, or any reusable UI components. Triggers on tasks involving component APIs, composition patterns, accessibility, styling systems, or TypeScript props.
Guides a user through collecting the credentials needed to deploy their own copy of Open Harness, deploying this repo on Vercel, and completing first-run setup. Use for requests about deploying, self-hosting, configuring credentials, or getting started with a fork of this app.
Run `doca_bench` (DOCA 2.7.0 or newer) to measure throughput, bulk latency, precision latency, or maximum bandwidth for RDMA, Compress, AES-GCM, SHA, DMA, EC, Ethernet, Comch, or GPUNetIO on a host or BlueField Arm. Use it to discover enabled benchmark libraries, capture a reproducible command/version/device/environment baseline, compare stable runs against a declared tolerance, or diagnose configuration, device-binding, workload-precondition, and measurement failures. Trigger for requests such as measuring BlueField compression speed, NIC RDMA throughput, crypto latency, or a pre-upgrade baseline. Do not use for application end-to-end timing, custom benchmark code, DOCA installation, or binary patches.
Check a docs-content page against Elastic content type guidelines (overview, how-to, tutorial, troubleshooting, changelog), or classify a proposed page idea against the content types before drafting. Use when the user asks to check content type compliance, validate page structure, review a doc against content type standards, or decide which content type a planned page should use
Generate or improve meta descriptions in Elastic documentation frontmatter following SEO best practices. Use when adding description fields to doc pages, auditing missing descriptions, or improving metadata for search discoverability
Create or update a Lens chart documentation page following Elastic docs conventions. Use when writing a new chart type page (pie, bar, metric, gauge, heat map, etc.) or updating an existing one in explore-analyze/visualize/charts/. Relies on lens-chart-settings for verifying UI labels against source code
Optimize the opening of an Elastic documentation page — H1 title, opening paragraph, and requirements section — following doc type conventions. Use when writing or improving page intros, optimizing titles for discoverability, adding requirements sections, or when the user asks to improve the first lines of a doc page
Use when monitoring Xiaohongshu marketing campaign performance, tracking promotion effectiveness, analyzing advertising ROI, measuring influencer collaboration results, evaluating activity success rates, or optimizing marketing spend allocation
Entry into the graph: “get oriented,” “enter the graph,” “what does the graph say,” “in the graph,” “what method,” NKS, an unfamiliar Iskron term, kriya, vimarsha, relay. Establish the graph, location, role, and relationships. For a specific search for evidence, “we discussed,” advice, or “not in the graph,” use recall; if the location is unknown, this entry then leads to recall. Reading a record is not observing the world. Explain the methodology and orient in the graph; use before answering anything about the user's Iskron graph. Iskron tools are required.
Feishu smart calendar. calendar suggestion finds times when all attendees are available; calendar room-find filters meeting rooms by capacity/time; calendar rsvp accepts or declines invitations. Calls freebusy/suggestion + freebusy/room_find directly over HTTP (not exposed in SDK v3.5.3), with automatic 429 backoff (DoWithRetry). Use when the user asks to “find a meeting time,” “find available slots,” “find a meeting room,” “accept/decline a meeting invitation,” “freebusy,” or “check schedule conflicts.”
Native Markdown file operations for Feishu cloud drive (complementary to doc import/export). markdown create uploads a new .md to the drive; markdown fetch downloads a file as a local .md; markdown overwrite replaces an existing drive file with a local .md (preserving file_token and keeping the share link valid); markdown diff compares the latest or historical remote version locally without changing the remote file. Use the native .md file path when doc documents are unsuitable (image hosting, dense code blocks, version control). Drive upload_all + manually assembled Formdata multipart (SDK does not expose the file_token field). Use when the user asks to “upload markdown,” “download md,” “overwrite drive md,” “md diff,” or “compare markdown versions.”
Complete video transition system. PROACTIVELY activate for: (1) xfade transitions (40+ types), (2) Fade in/out effects, (3) Crossfades and dissolves, (4) Wipe transitions (directional), (5) Slide and push effects, (6) Circle/iris transitions, (7) Multi-clip transition sequences, (8) Slideshow creation, (9) Custom transition expressions, (10) Audio crossfade synchronization. Provides: Complete xfade type reference, offset calculation formulas, multi-clip examples, custom expression guide, troubleshooting for resolution/framerate mismatches. Ensures: Smooth professional transitions between video clips.
Fix manifest.json issues that the UI5 linter reports but cannot auto-fix. Use this skill when the linter outputs these rules: - `no-outdated-manifest-version` - For _version not being 2.x - `no-legacy-ui5-version-in-manifest` - For minUI5Version below 1.136 - `no-deprecated-library` - For deprecated libraries in dependencies - `no-deprecated-component` - For deprecated components in dependencies - `no-deprecated-api` - For deprecated view types, resources/js, deprecated model types - `no-removed-manifest-property` - For async flags in manifest v2 Trigger on manifest.json files with errors about version, libraries, components, view types. Automatically updates manifest.json to be modern UI5 compatible.
Work with GitLab CI/CD pipelines, jobs, and artifacts. Use when checking pipeline status, viewing job logs, debugging CI failures, triggering manual jobs, downloading artifacts, validating .gitlab-ci.yml, or managing pipeline runs. Triggers on pipeline, CI/CD, job, build, deployment, artifact, pipeline status, failed build, CI logs.
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.