Loading...
Loading...
Found 971 Skills
Call the cloud OpenAPI of Pudu robots, supporting operations such as robot task distribution, status query, delivery, cruise, call, and statistical data analysis. When using, first check the credentials and cluster environment variables; if missing, prompt the user to supplement them, then call the corresponding interface according to the user's intention and display the results. Trigger scenarios: Use this skill when the user mentions keywords such as "Pudu robot", "pudu", "robot task distribution", "query robot status", "delivery task", "cruise task", "call robot", "lifting task", "errand", "Flash Cabinet", "advertisement playback", "advertisement configuration", "cabinet task", "cabinet SKU", "product SKU", "hatch door photo", "traffic control zone", "map list", "statistical data", "risk avoidance", "dashboard overview", "OpenAPI".
SpriteRendererComponent.SpriteRUID (world) and SpriteGUIRendererComponent.ImageRUID (UI) — native RUID type support (sprite / animationclip direct playback), thumbnail:// prefix for rendering avataritem / skeleton / animationclip as static thumbnail image, avatar item icon in inventory / shop / UI slot. Use when: assigning any RUID to a sprite renderer component, displaying an avatar item or resource as a thumbnail or icon, using animationclip directly in a renderer, rendering inventory item icons, displaying a thumbnail image in a world entity. Keywords: SpriteRUID, ImageRUID, thumbnail://, animationclip, RUID apply, RUID assign, thumbnail, item icon, sprite RUID, RUID to renderer
Use this skill for OKX Outcomes markets (YES/NO event contracts, formerly OKX Predictions) via the okx-outcomes binary. Triggers: 'list prediction events', '预测市场', 'event detail', 'place prediction order', '预测下单', 'buy YES', 'buy NO', '撤单 预测', 'split xp', '拆分 xp', 'merge YES NO', '赎回 预测', 'prediction positions', '预测持仓', 'live prediction price', '预测行情', 'OHLCV candles', 'K线', 'CTF', 'polymarket'. Auth: OAuth sign-in via 'okx outcomes auth login'; writes need a signing key configured by 'okx outcomes setup'. Do NOT use for OKX CEX event contracts (use okx-cex-trade event), spot/swap/futures (okx-cex-trade), crypto market data (okx-cex-market), or CEX portfolio (okx-cex-portfolio). Namespace required: account: balance/positions/order/orders/trades; clob: price/prices/midpoint/midpoints/spread/spreads/book/books; data: events/event/event-markets/market/trending/ticker/candles; ctf: split/merge/redeem; wallet: show; auth: login/refresh/status; setup: status/region/bind.
This skill should be used when the user asks about Stripe Connect configuration, charge patterns, dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (e.g. POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants/sellers/vendors, mentions connected account dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
When the user wants to analyze Google Ads performance by device, geography, day of week, hour of day, or any combination of these dimensions. Also triggers on 'device performance', 'mobile vs desktop', 'bid adjustments', 'geo performance', 'location targeting', 'dayparting', 'ad schedule', 'hourly performance', 'device modifiers', 'geo bid adjustments', 'best time to run ads', 'location exclusions', or 'campaign splits by device or geo'. For full campaign structure see google-ads-search. For Smart Bidding see google-ads-bidding.
Use when someone asks to generate a design, create a design asset, or make a design. Also triggers for ad creatives, banners, social media posts, thumbnails, display ads, posters, or any visual content. Orchestrates a 7-step workflow (1) resolves brand, (2) generates copy using content expert instructions, (3) generates images via handle-media or enhances provided images via enhance-media, (4) calls Sivi API with approved copy + assets for pixel-faithful design generation, (5) displays the generated variants with preview images and edit links, (6) creates campaign HTML, (7) writes a summary. If user already has approved copy, skips step 2. Supports both `designs-from-content` (copy-first, pixel-faithful text) and `designs-from-prompt` (direct generation, no copy or image generation). Unlike 95,000+ image models, Sivi's Large Design Model (LDM) generates on-brand, fully editable layered designs in any dimension. For copy-only without design generation, see write-copy. For multi-channel campaign sets, see create-campaign. For Amazon A+ content, see create-a-plus-content. For brand setup, see brand-context.
Guide non-technical ART+COM users from an idea to a shareable internal web prototype. Use when a user wants to create or extend a prototype, choose its target display and input, check or install web-development tools, create a GitLab project under gitlab.artcom.de/prototypes, connect a Netlify site, keep a deployed prototype private with a password and out of search engines, choose between Astro, React, React Three Fiber, or optionally add MQTT.
TanStack Router best practices for type-safe routing, file-based routing, data loading, search params, and navigation in React. Use when building React SPAs with complex routing, implementing type-safe search params, setting up route loaders, integrating with TanStack Query, or configuring code splitting and preloading.
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over ~10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs, waitForSubWorkflow, mode each vs all, or exposing a workflow as an agent tool. Covers typed sub-workflow inputs, all-vs-each execution, verb-first naming for discovery, stateless vs stateful design, and splitting by input shape.
Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send the image", Merge losing binary, or a CDN for chat images. Covers the $binary vs $json split, reading/writing binary, keeping binary alive across transforms with Merge, the agent-tool binary boundary, and the CDN/URL requirement for chat surfaces.
Search the FPF knowledge base and display hypothesis details with assurance information