'container' 검색 결과

Give selected NanoClaw agents access to Dial for sending SMS, making AI voice calls, and receiving verification codes. It installs the command-line tool and uses OneCLI to supply credentials and control which agents can use it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Send SMS from a chat request
• Ask an agent to place an AI voice call
• Receive phone verification codes inside an agent container

Connect a container agent to local Ollama models through MCP, a protocol for agent tools. The agent can list models and generate responses, with optional tools to download, delete, inspect, and check loaded models.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delegate response generation to a local model
• Check which Ollama models are installed
• Download or delete models through the agent

Install rtk in NanoClaw agent containers to compress development command output and reduce token use. A Claude Code hook automatically routes Bash calls through rtk, with runtime checks to verify installation and a command to inspect savings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reduce token use from development command output
• Automatically route Bash calls through rtk
• Configure rtk for multiple agent groups

Customize a project's Docker environment with personal tools such as vim, ripgrep, or jq. The skill prepares user override files, adds requested packages, and provides rebuild commands while keeping personal configuration out of Git.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding an editor or search tools to a container
• Keeping personal settings separate from shared files
• Customizing a source-built development environment

Explain which process holds a port or file lock, what started it, and what keeps it running. Uses the witr CLI to trace services, containers, and parent processes without stopping or changing anything.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding what holds an occupied port
• Tracing a development server left running
• Explaining an unknown or stuck process

Generate Terraform alerts for Cloud Run services, jobs, and worker pools using PromQL, a monitoring query language. Monitor errors, latency, resource usage, job failures, and queue delays, with configurable thresholds and explanations of when each alert triggers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitor Cloud Run service errors and latency
• Detect failed batch job executions
• Monitor worker pool backlogs and message age

Deploy and manage applications on Cloud Run using source code or container images. Choose services for web requests, jobs for tasks that finish, or worker pools for continuous background processing, with guidance on execution settings and deployment failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy a web application from source code or a container
• Create and run batch jobs with parallel tasks
• Deploy continuous queue-processing workers

Publish a built website or web app and provide a shareable URL through Kortix Apps, Cloudflare, or Vercel. Check the running build, security, external service requirements, and data storage limits before deploying with the user's explicit approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sharing a temporary demo of a static website
• Deploying an app with Kortix sign-in
• Publishing a framework app or container on Vercel

Helps deploy, manage, and troubleshoot applications on Kubernetes using kubectl and Helm. Covers container logs, resource settings, network access, and deployment strategies to investigate failures and review how applications run.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating repeatedly crashing containers
• Reviewing deployment and resource settings
• Troubleshooting service connectivity and DNS

Helps design and provision Microsoft Azure infrastructure using az CLI and Bicep configuration files. Covers choosing application hosting services, managing identities and secrets, designing networks, setting up monitoring, and organizing resources for cost management.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define repeatable infrastructure with Bicep
• Choose hosting services for web apps and containers
• Design identity permissions and secret storage

Manage OpenKruise in KubeSphere, from extension installation to troubleshooting. Generate SidecarSet configuration for adding helper containers and CloneSet configuration for application updates, including in-place changes and staged rollouts, with commands to apply and verify each configuration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Install OpenKruise and check its status
• Add and update helper containers with SidecarSet
• Stage application image updates with CloneSet

Install and configure WizTelemetry Logging in KubeSphere to collect container output and file logs. Use its API to filter logs by workload, time, or keywords, retrieve statistics, and export results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy log collection to selected clusters
• Enable collection of log files inside containers
• Search logs by keyword, workload, and time

Automate Docker Hub administration through Composio: create organizations and repositories, list teams, invite members, and configure webhooks that notify other services when container images are pushed to a repository.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a Docker Hub organization or repository
• Review repositories with filters and sorting
• List teams and invite organization members

Generate an OpenShell SBOM, an inventory of software components, with Syft. Fill missing license details from public registries, export CSV files for compliance review, and inspect or validate SBOMs attached to container images.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generating a dependency inventory for a release
• Filling missing dependency license information
• Exporting CSV files for license review

Evaluate language models on knowledge, math, coding, safety, and image understanding benchmarks. The skill guides reproducible runs in containers using local Docker, Slurm clusters, or cloud execution, with shared configurations for model comparison and result export.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing models on the same benchmark tasks
• Running a small evaluation sample before a full benchmark
• Running large evaluations on a Slurm cluster

Audit and fix four access-control problems in Convex apps: impersonation, missing ownership checks, sensitive data exposure, and writes into another user's container. Check the authentication foundation first, then verify changes with TypeScript.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether callers can impersonate another user
• Restrict document access to its owner
• Review queries that expose sensitive data

Develop and verify changes to Apache Beam's Python SDK. Set up a virtual environment, run tests, build installable packages or containers, and run data processing pipelines with the modified SDK.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up an Apache Beam Python SDK development environment
• Run unit and integration tests for SDK changes
• Build SDK packages and container images

Create buttons, cards, and panels with diagonally cut corners. It provides CSS shapes, border treatments, and sizing guidance to keep the geometry consistent while preserving readable labels, usable touch targets, and visible keyboard focus.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating sci-fi-style controls
• Unifying diagonal corners across cards and panels
• Adding gradient borders to clipped shapes

Publish HTTP apps or APIs running inside Worker containers through the Higress gateway. Configure exposed ports using the agt CLI or YAML, receive automatically generated domains for each port, and inspect or remove public access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Make a Worker's web app externally accessible
• Publish an API running in a Worker container
• Expose multiple ports on one Worker

Pick Jetson-compatible containers, vLLM runtime images, and Jetson AI Lab PyPI indexes; maps Orin SM 8.7 vs Thor SM 11.0 and JetPack-specific package choices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Clone the latest NVIDIA Holoscan Sensor Bridge repo, ask which supported devkit is being used, configure the host per platform, build the correct demo container, run it, and verify HSB connectivity by pinging 192.168.0.2. Use for Holoscan Sensor Bridge setup, build, container launch, and first-connectivity bring-up.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user is operating the DOCA Firefly Service container on BlueField — picking the four PTP configuration axes (role / profile / domain / interface), wiring the BlueField PHC + host follower + consumer workload pairing, deciding whether PTP-grade time is even needed (vs. chrony / NTP), or debugging a Firefly deployment where PTP isn't syncing or the host clock isn't following. Trigger even when the user does not explicitly mention "DOCA Firefly" or "PTP" — typical implicit phrasings include "container green but PTP never advances past LISTENING", "Firefly says synced but the host clock still drifts", "sync acquired but offset is tens of microseconds", "my Rivermax SMPTE workload needs PTP", or "is chrony good enough". Refuse and route elsewhere for installing DOCA, host-side chrony / ptp4l config bodies, PTP topology / boundary-clock design, building DOCA apps that read the disciplined PHC, or other DOCA services (DMS, Flow-Inspector, HBN) — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or how to capture state for a Developer Forum post. Trigger even when the user does not say "DOCA debug" — implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA install from a host that doesn't have one yet via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention "DOCA setup" — typical implicit phrasings include "just got a BlueField, what now", "code is built, how to run it", "pkg-config can't find doca-flow", "no free 2048 kB hugepages", "representor X not found", "on a Mac and want to learn DOCA". Refuse and route elsewhere for library API specifics (Flow pipes, RDMA queues), the modify-a-sample first-app workflow or DOCA_ERROR_* program-side debugging, and "where is X documented" knowledge-map questions — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.