Loading...
Loading...
Found 1,352 Skills
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.
Explain, review, and author ERDA specification files based on parser-supported fields. Use when users need help understanding or editing dice.yml and pipeline.yml, want field-level guidance, or need answers grounded in the ERDA parser rather than marketplace summaries.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
将本地 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.
Look up information in SigNoz documentation. Make sure to use this skill whenever the user asks "how do I", "where in the docs", "what does the docs say about", "find docs for", or otherwise needs reference material on SigNoz instrumentation, OpenTelemetry setup, self-hosted deployment, API endpoints, auth headers, or troubleshooting steps — even if they don't say the word "docs" explicitly. Docs lookup only — for actions inside SigNoz, the agent will pick the matching `signoz-*` action skill.
Snyk integration. Manage Projects, Organizations. Use when the user wants to interact with Snyk data.
Core Oodle CLI usage — auth, output formats, time flags, file input, and common patterns for all oodle commands.
This skill should be used when the user asks to "set up oodle integration", "onboard to oodle", "integrate kubernetes with oodle", "connect AWS to oodle", "install oodle collector", or mentions setting up observability with Oodle. Discovers the environment, recommends matching integrations from available setup specs, and executes step-by-step installation. Not for querying existing metrics, logs, or traces (use /oodle-metrics-query, /oodle-logs, /oodle-traces instead).