Loading...
Loading...
Found 1,352 Skills
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.
**WORKFLOW SKILL** — Manage Aspire AppHost lifecycle and recover from file locks, port conflicts, and orphaned processes. WHEN: "start my Aspire app", "aspire start", "aspire stop", "aspire wait", "restart the API service", "file lock error", "MSB3491", "CS2012", "port already in use", "upgrade Aspire CLI", "aspire update --self", "proxies missing in aspire ps", "--include-hidden", "aspire integration list", "aspire integration search", "default watch", "hot reload". INVOKES: aspire CLI (start, stop, wait, ps, resource, integration, add, init, doctor, update, restore). DO NOT USE FOR: deploy / publish / destroy / pipeline steps (use aspire-deployment), logs / traces / metrics / dashboard run (use aspire-monitoring), AppHost code edits or resource wiring (use aspireify). FOR SINGLE OPERATIONS: Run the aspire CLI command directly.
Provides guidance for authoring Apache Airflow DAGs in Managed Service for Apache Airflow (MSAA; formerly Cloud Composer). Covers environment context discovery, Airflow 2 vs 3 compatibility, authoring best practices, and local/remote validation processes. Use when creating or extending an Airflow DAG. Don't use when authoring Python code unrelated to Airflow DAGs.
Use when a project contains okteto.yaml or okteto.yml, or when the user mentions Okteto, dev environments, or an okteto command. Also use before running kubectl, helm, or docker build in a repo that has an Okteto manifest; when okteto up hangs or seems stuck; when parallel git worktrees collide over the same environment; or when deciding whether okteto destroy or okteto namespace delete is safe to run.
Okteto Preview Environment skill. Use when someone wants a live, shareable environment for a branch or pull request — "deploy a preview for this PR", "give me a URL for branch X", posting a preview link back to a PR or thread — or when setting up PR preview automation in CI (GitHub Actions or GitLab). Use alongside the `okteto` skill: for editing, syncing, and iterating on code, defer to that skill's dev environments. Requires an Okteto context; previews are an Okteto Platform feature.
Use when a project has NO okteto.yaml/okteto.yml and the user wants it on Okteto — e.g. "get this repo onto Okteto", "set up a dev environment for this", "create an Okteto manifest", "onboard this service". Also use when okteto deploy fails because no manifest exists. Do NOT use if okteto.yaml or okteto.yml already exists — that is the okteto skill's domain.
One-click deploy, publish, and update a local project or Git repository to Alibaba Cloud International (alibabacloud.com), producing an accessible online service with a public IP. Supports full-stack ROS orchestration, automatic cloud-resource provisioning, pre-deployment price confirmation, service health checks, deployment-state recording, hot updates, and optional domain + HTTPS setup. Use when: the user asks to deploy a project to the cloud, put an app online, publish a website, generate an access URL, deploy a Git repo, or update an online version and has NOT named a specific cloud platform; or the user mentions "Alibaba Cloud", "alibabacloud.com", or the international site. Do not use when: the user explicitly targets Aliyun China (aliyun.com), AWS, GCP, Azure, or another specific cloud platform.
Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.
Deploy validated metadata to a Production Salesforce org without re-running tests. TRIGGER when the user wants to deploy to production, says 'quick deploy', 'promote', 'ship to prod', or has just validated and wants to push the change live. REQUIRES a recent `sf project deploy validate` job ID (≤10 days old, ≤3 days for --use-most-recent). DO NOT TRIGGER for sandbox/scratch deploys (use platform-metadata-deploy) or unvalidated deploys (use platform-deploy-validate first).
Recommend webhook subscriptions and safe automation patterns for PlanetScale alerts, anomalies, schema recommendations, deploy requests, and agent workflows.
Route run.cloud work to the focused mobile-session or sandbox skill. Use when a request mentions run.cloud generally, spans both products, or does not yet distinguish remote iOS and Android sessions from microVM sandboxes.
Operate run.cloud microVM sandboxes with the CLI or TypeScript SDK. Use for creating isolated compute, running commands, moving files, managing snapshots or images, exposing ports, using SSH or desktop automation, attaching secrets, sizing resources, or cleaning up sandboxes.