Loading...
Loading...
Found 36 Skills
Use when users need NocoBase bootstrap and runtime lifecycle with nb CLI only.
Create reproducible, cross-platform development environments with Flox — a declarative environment manager built on Nix. ALWAYS use this skill when the user needs to: set up a project with system-level dependencies (compilers, databases, native libraries like openssl, libvips, BLAS, LAPACK); configure reproducible toolchains for Python, Node.js, Rust, Go, C/C++, Java, Ruby, Elixir, PHP, or any language; manage environments that must work identically across macOS and Linux; pin exact package versions for a team; run local services (PostgreSQL, Redis, Kafka) alongside development tools; onboard new developers with a single command; or solve 'works on my machine' problems. Especially valuable for AI-assisted and vibe coding — Flox lets agents install tools into a project-scoped environment without sudo, system pollution, or sandbox restrictions, and the resulting environment is committed to the repo so anyone can reproduce it instantly. Use this skill even if the user doesn't mention Flox — if they describe needing reproducible, declarative, cross-platform dev environments with system packages, this is the right tool. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub.
Deploy and debug Eve-compatible apps via the CLI, with a focus on staging environments.
KIRIKAE ローカル開発プロキシの環境管理スキル。 curl経由でAdmin API (localhost:4000) を操作し、環境の一覧表示・追加・切り替え・リネーム・更新・削除を行う。 使用タイミング: (1) 開発環境のプロキシ先を切り替えたい (2) 新しいポートを登録したい (3) 環境のラベル名を変更したい (4) 登録済み環境を確認したい (5) 環境を削除したい トリガーキーワード: kirikae、切替、プロキシ切替、環境切替、ポート登録、ポート切替
Integrates GuaraCloud into local development workflows — project linking, remote shell access, port forwarding, log streaming, and environment management. Use when the user wants to connect their local environment to GuaraCloud, tail logs, exec into a container, or forward ports.
Comprehensive package and environment management using pixi - a fast, modern, cross-platform package manager. Use when working with pixi projects for (1) Project initialization and configuration, (2) Package management (adding, removing, updating conda/PyPI packages), (3) Environment management (creating, activating, managing multiple environments), (4) Feature management (defining and composing feature sets), (5) Task execution and management, (6) Global tool installation, (7) Dependency resolution and lock file management, or any other pixi-related operations. Supports Python, C++, R, Rust, Node.js and other languages via conda-forge ecosystem.
Deploy Databricks jobs and pipelines with Asset Bundles. Use when deploying jobs to different environments, managing deployments, or setting up deployment automation. Trigger with phrases like "databricks deploy", "asset bundles", "databricks deployment", "deploy to production", "bundle deploy".
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
Use when users need to prepare a NocoBase environment, install and start an app, bootstrap local nocobase-ctl runtime, manage app environments (add/use/current/list), upgrade a single instance, or diagnose environment-level failures.
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
Shared Base for Aike Smart Parking Open Platform (openydt) CLI: First-time use of openydt, profile configuration, signature (v2/v3) and multi-environment (test/dev/prod) setup, response envelope and status code/business code handling, exit codes, rate limiting and retry, write operation security rules. Triggered when users first use openydt, configure/switch profiles, handle signature or environment issues, interpret status/resultCode, encounter rate limiting or authentication failures, or before performing any parking lot write operations. All openydt domain skills should read this base first.
Configure Clerk for multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing multiple Clerk instances, or implementing environment promotion. Trigger with phrases like "clerk environments", "clerk staging", "clerk dev prod", "clerk multi-environment".