인프라·DevOps 스킬

Prepares an OpenWork Cloud/Den demo on Daytona with Acme Robotics sample data. It checks service health and sign-in, keeps the sandbox active, and returns URLs and credentials ready to share with demo participants.

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

• Preparing a cloud demo with sample organization data
• Checking demo health endpoints and account sign-in
• Keeping a demo active and organizing access details

Set up and troubleshoot Daytona sandbox environments, which provide isolated spaces for running applications. The skill covers CLI authentication, persistent desktop and server sandboxes, diagnostic logs, shared secrets storage, snapshot refreshes, and environment deletion.

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

• Troubleshooting Daytona authentication and organization selection
• Keeping an Electron or server sandbox available for debugging
• Preparing shared secrets storage for sandboxes

Create disposable OpenWork previews for hands-on review of app and Den changes. Choose local, Daytona, or Freestyle environments as supported, reopen existing previews, update supported frontend changes while preserving progress, and reset or stop environments when finished.

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

• Trying OpenWork changes before merging a PR
• Reviewing signup and team administration flows
• Testing the desktop app together with Den

Load API keys, tokens, and other secrets from Infisical into a shell or a specific command. The skill covers finding secret names, checking availability, and passing values to commands without displaying or logging them.

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

• Loading a missing API key before running a command
• Passing secrets only to the process that needs them
• Checking secret names and availability without displaying values

Publish an OpenWork version through Git tags and GitHub Actions without creating version-update commits. Review outstanding fixes, monitor builds and publication, check release assets, and recover failed distribution steps using procedures that protect already published desktop installers.

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

• Publishing a patch, minor, or major OpenWork release
• Reviewing open fixes before creating a release tag
• Recovering distribution steps for an existing release tag

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

Prepare a software release from the dev branch by turning commits into a changelog, updating the version, and creating a pull request to main. The workflow also covers release tags, branch synchronization, and Homebrew package updates.

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

• Preparing a patch, minor, or major release
• Turning changes into a user-facing changelog
• Updating Homebrew packages after publishing binaries

Deploy n8n on a Linux server using Docker Compose and Caddy for automatic HTTPS. Covers single-instance setups, workers for parallel execution, secret management, deployment checks, updates, backups, and restoration.

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

• Installing n8n on a VPS
• Running workflows in parallel with workers
• Publishing n8n with automatic HTTPS

Manage which n8n instance an MCP session targets when working across production, staging, teams, or clients. Guides instance switching, checks before credential changes, and recovery from unexpected missing data or ambiguous credential writes.

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

• Switching between production and staging
• Checking the target before credential changes
• Investigating unexpected missing data

Retry commands that fail with network errors through proxychains4, a tool that routes connections through a proxy. The skill also guides proxy configuration and troubleshooting when downloads, package installations, or Git operations cannot connect.

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

• Retrying a failed Git clone through a proxy
• Installing packages when pip or npm cannot connect
• Troubleshooting download timeouts and DNS failures

Prepare a daily NemoClaw maintenance plan by ranking pending pull requests and issues, checking work carried over from earlier versions, and selecting release targets. Produce a queue with owners, next actions, and merge readiness.

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

• Plan the day's maintenance work
• Find work carried over from earlier releases
• Rank pull requests for review

Analyze saved NemoClaw CI timings to rank consistently slow command-line tests and compare base-image publication with reuse. Read-only analyzers report execution times, runner queues, and sample coverage as bounded JSON output.

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

• Finding consistently slow command-line tests
• Ranking test files by execution time
• Comparing base-image publication with reuse

Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.

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

• Prepare an end-of-day release handoff
• Consolidate documentation for merged changes
• Review unfinished work and verification status

Prepare and create a signed NemoClaw release tag for a requested version, then monitor release workflows, documentation, and published images. It records maintainer decisions and drafts an announcement after verifying the remote tag.

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

• Preparing a tag for a requested release version
• Recording documentation and end-to-end test decisions
• Checking workflows and images after tagging

Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.

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

• Classifying a failed GitHub Actions job
• Inspecting saved artifacts for failure evidence
• Gathering initial evidence for an E2E failure

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

Guide a macOS app release through versioning, signing, Apple notarization, update feed checks, and Homebrew updates. Includes CodexBar release scripts, published asset verification, and preparation of the next unreleased version.

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

• Releasing a signed and notarized macOS app
• Verifying update feeds and published release assets
• Updating Homebrew app and CLI packages

Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.

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

• Preparing a desktop app release
• Checking whether Rust changes require a CLI release
• Updating MCP versions and checking publication

Check Screenpipe's process, API, screen capture, and audio transcription status. Inspect logs, storage, resource usage, and processing metrics to identify problems, then report the findings with relevant errors and suggested fixes.

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

• Check whether Screenpipe is running
• Investigate missing screen captures
• Diagnose missing audio transcriptions

Reconstruct an incident timeline from recorded screens and conversations, supported by available logs and monitoring. Organize symptoms, changes, response actions, and recovery evidence while distinguishing observed facts from suspected causes.

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

• Reconstructing events around a system incident
• Reviewing response actions and recovery evidence
• Separating observed facts from suspected causes

Prepare a stable Paseo release by following the documented release flow and completion checklist. Use it for a fresh patch or minor release, or to promote a beta version to stable.

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

• Release a new stable patch version of Paseo
• Release a new stable minor version of Paseo
• Promote a Paseo beta version to stable

Prepare a beta release of Paseo by following the project's release documentation. The skill directs the agent through the beta workflow and its completion checklist, keeping the task tied to the documented process.

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

• Preparing a Paseo beta release
• Following the documented beta release workflow
• Working through the beta release completion checklist

Analyze configuration and operational metrics for Managed Service for Apache Airflow environments. Use CPU, memory, disk, restart, and workflow parsing data to recommend resource sizing and configuration changes based on observed bottlenecks and environment health.

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

• Review environment sizing and scaling settings
• Investigate frequent component restarts
• Find bottlenecks in workflow file parsing

Builds an Apigee proxy that inspects an agent’s model requests and responses through Google Cloud Agent Gateway. It measures token usage by model, identifies callers, and can add prompt screening or a cache for similar prompts.

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

• Measure token usage by model
• Identify callers behind model requests
• Add Model Armor prompt screening