Total 43,803 skills, DevOps & Cloud Services has 2707 skills
Showing 12 of 2707 skills
Diagnoses and resolves issues on GuaraCloud — failed deployments, crash loops, health check failures, image pull errors, OOM kills, and CLI errors. Use when the user reports something broken, a deployment failed, a service is unhealthy, or they see an error.
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
Guides the agent through Capgo native cloud build workflows for iOS and Android. Use when requesting a native build, configuring build credentials, updating signing material, or controlling build output upload behavior. Do not use for OTA bundle uploads or generic CI setup without Capgo builds.
Use when researching, compiling, or assessing best practices for any AWS service, building HA/DR/security checklists from official AWS documentation, or checking whether live AWS resources follow official recommendations. Requires aws-knowledge-mcp-server. Triggers on "best practices", "compile checklist", "summarize HA/DR best practices", "what are the best practices for", "find all best practices", "check my cluster", "audit my redis", "assess my redis", "assessment", "是否符合最佳实践", "检查现有资源", "查找最佳实践", "编译检查清单", "总结最佳实践", "帮我查找", "汇总成表", "帮我检查", "审计一下", "评估一下".
Check GPU usage on remote servers. Connect to servers via SSH, display video memory usage, running processes, and associated containers for each GPU card. Use this when the user says to check GPU, graphics card usage, or video memory usage.
Triage and fix failing Buildkite CI checks for RisingWave pull requests by extracting concrete failing tests, diffs, and error messages from Buildkite build/job logs and artifacts, then applying focused code or test fixes. Use when users ask to diagnose red Buildkite checks, investigate flaky/failing CI jobs, understand why a Buildkite build failed, or provide Buildkite/GitHub check URLs and want a concrete fix.
Interact with the DX (getdx.com) APIs to get and manage information about services and other entities in the Software Catalog, manage Scorecards to track system health, and perform data analysis on Engineering productivity.
Use when creating a new Zeabur project. Use when deploying templates to a new project. Use when user says "create project", "new project", or "set up a new environment".
Use when creating, editing, validating, or troubleshooting a Zeabur template YAML. Use when converting docker-compose to Zeabur template. Do NOT use for deploying templates (use zeabur-template-deploy instead).
Use when listing dedicated servers. Use when checking server status, IP, or provider info. Use when user says "show my servers", "SSH into server", or "check server status". Do NOT use for browsing purchasable servers (use zeabur-server-catalog instead).
Use when proxy shows dial tcp timeout or i/o timeout. Use when service port doesn't match proxy expectation.
Use when users need to publish NocoBase applications across environments with strict precheck gates, hard method confirmation, backup artifact selection, and migration template presets (`schema_only_all` / `user_overwrite_only` / `system_overwrite_only` / `full_overwrite`).