「env」の検索結果

Use when deciding which English agriculture / environment / earth-science journal skill to invoke next, comparing fit across the 30-journal agriculture-and-environment roadmap, or routing a manuscript before venue-specific re-framing. Routes by sub-field (agronomy / plant / soil / food / environment / earth / climate), contribution type, and evidence shape (field trial / lab assay / observational survey / model / dataset).

日本語の概要は準備中です。原文の説明を表示しています。

Use when targeting Agriculture, Ecosystems & Environment or deciding whether an agroecosystem-environment manuscript fits this venue. Encodes the journal's fit, the field-to-landscape environmental-outcome bar, data-reporting expectations, house style, official-submission re-check, and desk-reject heuristics.

日本語の概要は準備中です。原文の説明を表示しています。

Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host is bound to the source env, provisions a new **Platform Host** (recommended, idempotent) or a **Custom Host** via the BAP env-create API with the `D365_ProjectHost` template, or guides the user through PPAC install / `New custom host` (manual fallbacks). Polls lifecycle operations, verifies the host responds to Pipelines API calls, writes a host-check artifact other ALM skills consume. Use when asked to: "set up pipelines host", "ensure pipelines host", "no pipelines host", "install pipelines", "create pipelines host", "provision platform host", "provision custom host". Also invoked transparently by /power-pages:setup-pipeline when its host discovery step finds nothing.

日本語の概要は準備中です。原文の説明を表示しています。

Expert knowledge for Azure Deployment Environments development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when defining environment.yaml, configuring dev centers/projects, using ADE/Dev CLI, custom images, or CI/CD deployments, and other Azure Deployment Environments related development tasks. Not for Azure DevTest Labs (use azure-devtest-labs), Azure Dev Box (use azure-dev-box), Azure Managed Applications (use azure-managed-applications), Azure Resource Manager (use azure-resource-manager).

日本語の概要は準備中です。原文の説明を表示しています。

Fast Python environment management with uv (10-100x faster than pip). Triggers on: uv, venv, pip, pyproject, python environment, install package, dependencies.

日本語の概要は準備中です。原文の説明を表示しています。

Manage OpenViking collections (OV libraries) from the command line with `ov-cp` — list / create / get / update / usage / get the data-plane API key / delete, plus managing the users and account data spaces of an enterprise-tier library (list / create / register / update / delete), account-scoped users / API keys / usage, and configuring how a library is billed (AgentPlan AFP deduction vs Volcano pay-as-you-go, `--pay-type` / `--seat-id`). Use when the user wants to provision or inspect an OpenViking library, fetch a library's data-plane API key, do the create→get-key cold-start, manage a library's users or accounts / 数据空间, set or switch a library's billing, or otherwise drive the OpenViking control plane (topapi). Authenticates with an Ark AgentPlan ApiKey.

日本語の概要は準備中です。原文の説明を表示しています。

「Tell, Don't Ask」原則に基づくコードレビューと設計支援。オブジェクトの状態を問い合わせて 外部で判断するパターンを、オブジェクトに直接命じるパターンに変換する。カプセル化を強化し、 責任をデータを持つオブジェクトに集約する設計を促進する。コードレビュー、新規実装、 リファクタリング時にgetterの乱用やFeature Envyの改善が必要な場合に使用。 対象言語: Java, Kotlin, Scala, TypeScript, Python, Ruby, Go, Rust。 トリガー：「getterを減らしたい」「カプセル化を改善して」「Feature Envyを直して」 「オブジェクトに責任を持たせたい」「デメテルの法則」といったOOP設計関連リクエストで起動。

Evaluates environmental liability exposure with remediation cost estimation, regulatory compliance requirements, and insurance coverage assessment. Use when analyzing environmental liabilities, estimating cleanup costs, or assessing environmental risk.

日本語の概要は準備中です。原文の説明を表示しています。

スキル（SKILL.md）を新規作成または更新し、リモートリポジトリへ PR を作成・更新する。SKILL.md は正常系、references に参考情報と異常系、scripts に利用スクリプトを置き、すべて汎用化してパラメータを .env.example に外出しする（実値は .env）。毎回同じ形のプロジェクトを作るスキルには templates/ を同梱し、汎用スキャフォルダー（scaffold_from_template.py）でテンプレートから生成して開始できるようにする。会社・個別プロジェクト情報を排除して秘匿化し、Step 番号は整数で統一。最後に番号整合・自動化観点（Learn は MCP で検証、ブラウザ操作は VS Code 統合ブラウザ）をレビューし、既存のオープン PR があればそれを更新してコンフリクトを避け、無関係なら新規 PR を作成しつつマージ順を提示する。

Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "install perlbrew", "set up Perl environment", "install Perl version", "manage Perl versions", "switch Perl version", "install plenv", or mentions Perl version management, development environment setup, or multiple Perl installations.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates environmental compliance requirements with permitting risk, mitigation obligations, and ESG assessment for infrastructure investments. Use when assessing environmental risk, evaluating permitting timelines, or analyzing environmental compliance.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates environmental liability exposure with remediation cost estimation, regulatory compliance requirements, and insurance coverage assessment. Use when analyzing environmental liabilities, estimating cleanup costs, or assessing environmental risk.

日本語の概要は準備中です。原文の説明を表示しています。

Install and verify the msmodeling development environment. Use when the user explicitly asks to install msmodeling dependencies, set up this repository, create `myenv` with `uv`, install this repository's `requirements.txt`, set project `PYTHONPATH`, or configure `HF_ENDPOINT`; if the user only says to install an environment, ask whether they mean msmodeling dependencies before proceeding.

日本語の概要は準備中です。原文の説明を表示しています。

Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an environmental scientist — scoping or reviewing a Phase I/Phase II environmental site assessment, interpreting soil or groundwater sampling results against regulatory action levels, drafting an environmental impact statement or NEPA scoping document, running a contaminant fate-and-transport screening calc, or assessing ecological risk to a receptor.

日本語の概要は準備中です。原文の説明を表示しています。

Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level environmental engineering covering water treatment, wastewater treatment, air quality, solid waste, site remediation, and environmental regulations.

日本語の概要は準備中です。原文の説明を表示しています。

Recreate the nuxt-crouton dev environment from scratch and survive its install/build traps — the pnpm toolchain, the cold-start sequence (why packages must build before apps prepare), the version catalog and workaround pins, the per-app typecheck rule, required env vars, and the known environment traps. Use when setting up a fresh clone/worktree, when "pnpm install" or "nuxt prepare" fails, when an app won't boot after install, when typecheck output looks insane, or when a tool "isn't available". Trigger phrases: "set up the repo from scratch", "why does typecheck show thousands of errors", "playwright install fails", "what pnpm/node version". (Exact error strings — "Could not load '@fyit/crouton'", "Cannot find module '@vue/compiler-sfc'" — route via crouton-diagnostics-index first; it points back here for depth.)

日本語の概要は準備中です。原文の説明を表示しています。

Use for environment validation: .env, config.yaml, paths, Python, Git — check + auto-fix + cron every 60min.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when validating API input, environment variables, form data, or DB responses at runtime boundaries. Trigger words: バリデーション, 入力検証, Zod, スキーマ, env 検証, 型強制, parse, safeParse, ランタイム境界.

Use this skill when handling secrets, API keys, environment variables, or ensuring server-only code never reaches the client bundle. Trigger words: シークレット, 秘密鍵, API キー, 環境変数, env, server-only, クライアント漏洩, NEXT_PUBLIC, バンドル.

Google Workspace CLI (gws) リファレンス。Rust 製。 `gws <service> <resource> <method>` 形式で Gmail / Drive / Calendar / Sheets / Docs / Chat 等 19 サービスを統一操作。Google Discovery Service 経由の動的コマンド生成。 `+` プレフィックスのヘルパーコマンド（+send, +agenda, +upload, +triage 等）、 ワークフロー合成（+standup-report, +meeting-prep, +weekly-digest）、 OAuth / サービスアカウント / CI ヘッドレス認証、env vars / .env / keyring 設定、 グローバルフラグ（--dry-run, --page-all, --sanitize）、exit codes、Model Armor 統合。

Apple SwiftUI 宣言的 UI フレームワークリファレンス。 View, VStack, HStack, ZStack, List, NavigationStack, TabView, State, Binding, Bindable, Environment, EnvironmentObject, sheet, fullScreenCover, modifier, animation, withAnimation, Animation, Transition, matchedGeometryEffect, PhaseAnimator, KeyframeAnimator。