「docker」の検索結果

Viteを使う開発で、設定ファイル、環境変数、APIへの接続、プラグイン、ビルド出力を整え、開発サーバーや依存関係の不具合調査を支援するスキル。

• 環境変数と開発用API転送の設定
• 開発サーバーの遅さや更新不良の調査
• 本番用ファイルの最適化と動作確認

NVIDIA GPU上で大規模言語モデルの応答生成を高速化し、APIとして提供する設定を支援します。量子化や一括処理、複数GPUへの分散も扱います。

• 言語モデルをチャットAPIで提供したいとき
• 多数のプロンプトを一括処理したいとき
• 量子化でメモリ使用量を抑えたいとき

ユーザー名を手がかりに400以上のSNSやサービスでアカウントを探し、見つかったページのリンクを整理します。名前の使用状況確認や公開情報の調査に使えます。

• 特定のユーザー名のアカウント探し
• サービスごとの名前の使用状況確認
• 許可を得た対象の公開情報調査

Modify or debug s6 services in the Hermes Docker image.

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

文章などを数値化して似た内容を探す検索をQdrantで実装。属性による絞り込みやAI回答用の資料検索から、大規模運用の設定・調整まで支援します。

• AI回答用の参考資料を検索したいとき
• カテゴリや日時で絞る類似検索
• リアルタイム推薦の実装

Zero-to-sensing path picker for RuView (WiFi-DensePose) — pick docker-demo, repo-build, or live-esp32 and run the next concrete step.

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

Onboarding and first-run for RuView (WiFi-DensePose) — Docker demo with simulated data, repo build, and the fastest path to a live sensing dashboard. Use when someone is new to RuView or wants the shortest path to "it works on my machine".

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

Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the `strix cloud` CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance reports, start PR reviews, buy credits, and set up schedules or webhooks. Use for managed, continuous, scheduled, team-tracked, or sandboxed-agent security testing.

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

Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.

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

Build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.

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

Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows. Use for DevOps, platform, container, pipeline, or release tasks.

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

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules.

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

Deploy MISP via Docker and configure feeds from sources like abuse.ch, AlienVault OTX, and CIRCL to aggregate, correlate, and distribute threat intelligence, including automated feed synchronization and STIX/TAXII-based integration with Splunk, Elasticsearch, and SOAR platforms. Use when standing up centralized IOC management or wiring multi-source threat feeds into a SIEM.

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

Install rtk token-compression proxy into agent containers. Routes Bash tool calls through rtk for 60–90% token savings on dev commands (git, cargo, pytest, docker, kubectl, etc.).

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

Detect which gbrain engine is in use (PGLite vs Postgres), prefer Postgres for agent-harness installs, install/provision Postgres (Supabase discovery via SUPABASE_ACCESS_TOKEN, local Postgres, opt-in Docker), and move an existing PGLite brain to Postgres with its history (plan, ask, run). Detection is one engine-free command; the install ladder is one flag.

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

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

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

Use when you need to visually interact with a GUI: test buttons, fill forms, verify visual layouts, fuzz web pages, automate user flows, take screenshots, or perform end-to-end QA on any application. Works on cloud VMs, Docker containers, local machines, and sandboxes. Needs the `cua` CLI (curl -fsSL https://cua.ai/install.sh | sh).

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

Zoom Video SDK for Linux - C++ headless bots, raw audio/video capture/injection, Qt/GTK integration, Docker support

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

ML engineering skill for productionizing models, building MLOps pipelines, and integrating LLMs. Covers model deployment, feature stores, drift monitoring, RAG systems, and cost optimization. Use when the user asks about deploying ML models to production, setting up MLOps infrastructure (MLflow, Kubeflow, Kubernetes, Docker), monitoring model performance or drift, building RAG pipelines, or integrating LLM APIs with retry logic and cost controls. Focused on production and operational concerns rather than model research or initial training.

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

Explains why a process is running and what started it, using the witr CLI. Use when a port is already in use (EADDRINUSE), a dev server or other process was left running, an unknown or stuck process needs explaining, or you need to know which service, container, shell, supervisor or scheduled job started a process, holds a port or holds a file lock. Use it instead of chaining lsof, ps, ss, netstat and docker ps.

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

Publish a website or web app from the sandbox to a public URL, and deploy to cloud providers — get a live link to share, ship a static site or SPA, put a built site online, or deploy a framework app / container. Use when the user says 'publish this', 'deploy it', 'put it online', 'give me a live URL', 'host this', 'share a preview link', or wants to make a site/app they (or you) just built reachable on the web. Covers the zero-account instant path (Cloudflare) and permanent hosting (Vercel, incl. any Dockerfile). Also owns the publish GUARDRAILS: never publish unprompted, how to honestly take a site down, the runtime-dependency and data-persistence checks, and the mandatory pre-publish security review. Prefers Kortix Apps (a stable Kortix URL behind Kortix sign-in) when the project has Apps on. Points at kortix-marketplace for other providers and deeper provider-specific skills.

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

Build, deploy and operate Kortix Apps through the pre-authenticated CLI or SDK: static sites and SPAs, Dockerfile or OCI servers, workers, and stateful backends (a database, a Convex backend) with persistent volumes, snapshots and built-in Kortix sign-in. Use when the user asks to publish, host, deploy, preview, inspect, scale, wake, suspend, roll back, debug, or remove an App; asks for a database, an API, a backend, a data model, auth, or 'store this'; asks for an internal tool, business app, CRM, tracker, dashboard, portal, or any app the team logs in to; before writing any Convex code; or asks what an App costs or how it runs.

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

Guide safe use of code_execution_remote for shell-backed execution on the connected A0 CLI host. Use when the user asks for their computer, local terminal, CLI host, remote shell, not Docker, or host-side Python/Node/terminal commands.

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

Control Agent Zero's Docker/Xpra desktop and GUI apps; not the user's host computer.

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