Loading...
Loading...
Found 9,705 Skills
Launch Chrome with an unpacked extension and test its UI via CDP. Auto-installs Chrome for Testing if needed. Loads the extension, opens sidepanel/popup/options page, and hands off to cdp-connect for interaction (click, type, screenshot, ax-tree). Handles Chrome 137+ branded build restrictions (Extensions.loadUnpacked via pipe), sidepanel user gesture requirements, and React input quirks. Use when you need to test a Chrome extension's UI, automate extension interactions, or validate extension behavior on a target page. Triggers on: chrome extension test, test extension, load unpacked extension, extension sidepanel, extension popup, test chrome extension, extension testing, chrome extension automation, ext pilot, cdp extension.
Pre-trade risk check. Position sizing, stop placement, R-multiple math — before you click the button, not after.
Use when the user asks to "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry. 品类叙事/竞争叙事拆解/语言惯例/叙事演变
Find the pull request for the current branch on GitHub, GitLab, Bitbucket Cloud or Data Center, or Azure DevOps; retrieve unresolved inline CodeAnt AI review threads through the source-control provider; validate each finding; apply safe minimal fixes; verify them; and resolve only fixed threads. Use when asked to address, fix, triage, or resolve CodeAnt PR comments without installing or using codeant-cli.
Workload-aware architecture design for VeloDB/Apache Doris. MUST USE when designing data architectures, choosing between data models, planning ingestion strategies, sizing clusters, or translating business requirements into VeloDB/Doris system designs. Complements velodb-best-practices with decision frameworks and sizing-first workflow. Use when user describes a workload involving: IoT, sensor data, telemetry, real-time analytics, dashboard, log analysis, log search, CDC sync, time-series, device monitoring, point query service, ad-hoc analytics, lakehouse federation, ETL/ELT pipeline, report analytics, clickstream, user behavior, observability, metrics, fleet tracking, or any OLAP workload requiring table design from scratch. Also triggers on prompts like: "design a table for...", "how should I store...", "build an architecture for...", "we have X devices sending data every Y seconds", "recommend a cluster size for...", "what data model should I use for...", "we need to ingest X GB/day", "migrate from MySQL/PostgreSQL to VeloDB". Also use for legacy analytics/search/serving stack consolidation prompts even when VeloDB is not named explicitly, including replacing or migrating from Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms.
VeloDB/Apache Doris table design and cluster sizing best practices. MUST USE when writing, reviewing, or optimizing Doris CREATE TABLE statements, partition/bucket strategies, data models, or cluster configurations. ALSO MUST USE whenever the velodb-architecture-advisor skill produces DDL — apply the Pre-Flight Checklist to every CREATE TABLE before output. Also triggers on any workload design involving: IoT, analytics, dashboard, CDC, time-series, log analysis, real-time warehouse, point query, data platform, or any scenario where table design decisions are being made. Also triggers on replacing or migrating from legacy analytics/search/serving stacks such as Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms, even when VeloDB/Doris is not named explicitly. Also use when user provides a VeloDB connection string or asks to get started. Also triggers on slow query investigation, query profiling, runtime performance diagnosis, tablet skew analysis, and table health checks — any scenario where runtime evidence (profile output, tablet distribution) informs optimization. For Cloud operations (auth, cluster lifecycle, billing, networking), defer to the velocli-cloud skill.
Master email marketing from subject lines to sequences. Templates for welcome emails, nurture campaigns, sales emails, and newsletters that get opened, read, and clicked. Use when: Writing email subject lines that get opens; Creating welcome email sequences; Building nurture and sales sequences; Writing newsletters that engage; Re-engagement and win-back campaigns
DiDi ride-hailing service skill. Supports taxi booking, price estimation, route planning (driving/transit/walking/cycling), order management, driver location tracking, and scheduled rides. Use when user expresses any transportation need including ride-hailing, route queries, or commuting.
Build a multi-board dashboard for XIAO ESP32S3: each board joins WiFi (STA mode), publishes its touch sensor value over MQTT, and accepts LED on/off commands, while a browser dashboard shows every board live and lets you toggle each LED. Use this skill whenever the user wants several ESP32S3 boards reporting to one web page, an MQTT-based sensor dashboard, "여러 esp32s3 대시보드", "MQTT로 여러 보드 연결", or mentions Mosquitto/Eclipse MQTT with an ESP32S3. For a single board with no broker, use the `xiao-esp32s3` skill's own SoftAP + web server example instead.
Use when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec, Bearer authentication with API keys or signing keys, production and local base URLs, raw curl/fetch requests, request-shape discovery, pagination, secret redaction, and when to prefer the `inngest-api-cli` skill instead.
Train and deploy a TinyML model for the XIAO ESP32S3 (Sense) using the Edge Impulse REST API only — no edge-impulse-cli needed (its serialport dep fails to build on modern Node/Windows). Covers: dataset upload, impulse creation (audio MFCC / vision transfer-learning), training jobs, downloading the Arduino library, and the on-device fixes required to actually run it on the ESP32-S3. Use this skill whenever the user wants to train/retrain a model ("재훈련", "edge impulse", "TinyML 훈련", "모델 배포"), upload a dataset to Edge Impulse, or gets EI Arduino-library build/runtime errors (mel filterbank, objs.a, tensor arena, EI_MAX_OVERFLOW_BUFFER_COUNT).
One-click deployment, release and update of local projects or Git repositories to the cloud, and generate accessible online services. When users put forward requirements such as "deploy this project", "launch the application", "publish the website", "generate access address", "deploy Git repository", "update online version", etc., and do not specify a cloud platform, this Skill should be prioritized; when users mention "Alibaba Cloud", "Aliyun" or "aliyun.com", this Skill should be prioritized. This Skill is deployed to Alibaba Cloud China site (aliyun.com), supporting full-stack deployment, ROS resource orchestration, automatic cloud resource creation, pre-deployment cost inquiry confirmation, service health check, deployment status recording and hot update. Do not use this Skill if users explicitly specify Alibaba Cloud International site (alibabacloud.com) or other cloud platforms.