Loading...
Loading...
Found 1,335 Skills
Tideways integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tideways data.
Rafay Systems integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rafay Systems data.
Kubernetes clusters, pods, nodes, workloads, storage, networking, and resource relationships. Query K8s inventory, diagnose degraded deployments and pod failures, investigate rollouts, audit ingress and network policies.
Vultr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vultr data.
New Relic integration. Manage Accounts. Use when the user wants to interact with New Relic data.
Expert knowledge for Chaos Studio development including troubleshooting, limits & quotas, security, configuration, and integrations & coding patterns. Use when defining ARM/Bicep experiments, deploying Chaos Agents, using CLI/REST, or integrating with Azure Monitor, and other Chaos Studio related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Site Recovery (use azure-site-recovery).
Use when services stuck on Waiting for database migrations to complete. Use when app expects separate migrator service.
Set up CI/CD workflows via interactive questionnaire — unit tests, build, coverage, linting, deploy, and custom actions
Termius integration. Manage data, records, and automate workflows. Use when the user wants to interact with Termius data.
将本地 Next.js 项目通过 PM2 部署到阿里云 ECS。当用户想把 Next.js 应用部署或重新部署到 ECS 实例时使用。
Creates Taubyte resources non-interactively via `tau new` for domain, website, library, function, application, database, storage, messaging, and service. Encodes the project-vs-application scope rule, the database `min < max` constraint, the website/library `--generate-repository` + import sequence, and the forbidden `--generated-fqdn-prefix` flag. Use when adding any resource to a Taubyte project's config repo.
Application-developer GitOps work for OpenChoreo — onboarding Components (BYO image or source-build), authoring Workloads and `workload.yaml` descriptors, attaching PE-authored Traits, wiring component dependencies, generating ComponentReleases and ReleaseBindings via `occ` file-mode, promoting releases across Environments (single, project-wide, bulk), applying per-environment overrides, opening PRs upstream, and verifying Flux reconciliation. Use when the user says 'add a component to the GitOps repo', 'release my service via Git', 'open a PR for this Workload change', 'promote to staging via Git', 'bulk-promote my project', 'roll back a release', or operates a developer-side change from inside a scaffolded GitOps repo.