스킬 찾기

Verify OpenWork changes by running the real product and following user or client actions. Choose suitable tests, capture screenshots and reports, and demonstrate that the check fails on dev but passes on the changed branch.

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

• Verifying real product behavior before opening a PR
• Preparing screenshots and test evidence for a reviewer
• Checking a fix against dev and the changed branch

Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.

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

• Screening an outside contributor’s pull request before execution
• Checking encoded code and unexplained network calls
• Reviewing dependency changes and installation scripts

Install the free OpenWork desktop app on macOS, Windows, or Linux using the appropriate download for the computer. Guide initial setup, folder authorization, model selection, and a first task such as summarizing local files.

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

• Installing OpenWork on a personal computer
• Choosing an installer for the OS and CPU
• Setting up a work folder and model

Attach screenshots, images, or videos to GitHub pull requests and issues using GitHub CLI. It also covers embedding images within comment text, adding alternative text, and retrieving an uploaded asset’s URL from the posted comment.

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

• Attach a screenshot to a pull request
• Add a video to an issue report
• Embed an image within a GitHub comment

Capture UI journeys in Daytona as labeled screenshots and optional video clips. Organize them into a browsable HTML page for PR presentations, helping reviewers follow user actions and compare behavior before and after a change.

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

• Sharing UI steps through a labeled screenshot page
• Recording streaming text, loading states, or animations
• Presenting before-and-after UI behavior in a PR

Investigate failed tests, type checks, builds, and CI jobs by recording exact evidence and repeating checks in a clean comparison environment. Use the results to distinguish existing failures, newly introduced problems, environment issues, and unresolved cases.

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

• Checking whether a failing test was already broken
• Investigating a failure that appears only in CI
• Distinguishing timeouts from environment problems

Measure chat layout jumps while a response runs by tracking the Working line through CDP, a browser debugging connection. Count upward movements and compare the same prompt before and after changes to status lines, step rows, or folding behavior.

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

• Checking layout jumps after changing progress displays
• Measuring jumps caused by collapsing content
• Comparing flicker before and after a UI change

Checks published OpenWork desktop downloads for mac-arm64, verifying developer signatures, Apple notarization, and update metadata. It checks versions, download references, and file hashes, then records evidence to support a release rollout decision.

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

• Checking signatures and notarization on published downloads
• Verifying update versions, asset references, and hashes
• Recording release verification evidence in a PR or issue

Find and use skills, shared tools, and connected services available in an OpenWork organization. Match a requested outcome to an available capability, run it with the required parameters, and explain any connection or permission steps.

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

• Finding skills available within an OpenWork organization
• Searching shared tools and connected services by intended outcome
• Running available OpenWork Cloud operations

Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.

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

• Connecting browser tools to a local Electron development app
• Inspecting screen state during debugging
• Entering a task in the composer and running it

Review code changes for compatibility between a desktop app and den, its cloud API. It flags changes that could break published apps, identifies desktop features depending on unavailable APIs, and explains the required rollout order.

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

• Review API changes for compatibility with published desktop apps
• Check whether desktop features depend on an unavailable API
• Identify missing desktop support for new API features

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

Reproduce model connection failures and interrupted responses in the desktop app using a local fault server and test providers. Check error messages and retry behavior for refused connections, DNS failures, HTTP errors, stalled requests, and cut streams.

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

• Checking error messages for model connection failures
• Testing responses to rate limits and server errors
• Reproducing stalled requests and interrupted replies

Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.

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

• Running a single end-to-end test
• Verifying the exact commit intended for a PR
• Investigating skipped tests and missing prerequisites

Review changed test specifications for cases where broken behavior could still pass. Report concrete gaps supported by the changes and implementation, with a minimal fix and an observable condition for resolving each advisory finding.

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

• Reviewing whether changed tests prove their stated behavior
• Finding UI tests that bypass the interaction being tested
• Checking whether save tests observe newly saved data

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

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

Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.

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

• Adding custom tools to OpenWork
• Creating a plugin to save and list notes
• Running custom code before or after tool execution

Guides review of pull requests from external forks, covering code ownership, contribution terms, security-sensitive changes, and tests tied to the reviewed commit. It produces a review record and supports moving changes to a maintainer branch when needed.

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

• Reviewing external contributions before approval
• Checking code provenance and contribution terms
• Verifying security reviews and tests for a specific commit

Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.

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

• Check error messages and retry progress
• Inspect text retained after an interrupted reply
• Review grouped parallel tool calls

Set up a Windows sandbox in Daytona to test OpenWork with a simulated corporate certificate authority. Check successful and broken HTTPS connections, the desktop app’s use of Windows trust, and certificate handling in runtimes it launches.

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

• Reproducing corporate certificate failures on Windows
• Checking OpenWork’s use of trusted Windows certificates
• Comparing valid and broken HTTPS certificate chains

Read design review notes attached to a pull request’s screenshots, locate the affected components, and fix the product code using the team’s design rules. Repeat the review and inspect screenshots to verify the result.

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

• Resolving design notes on a pull request
• Reproducing reported layout problems locally
• Fixing shared components behind repeated UI issues

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

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

• Registering a feature before implementation
• Releasing a feature to selected organizations
• Separating cloud and self-hosted availability

Create or revise pull request descriptions using a fixed template and concise language. It organizes the user problem, previous behavior, implementation, release note, and verification details so reviewers can understand the change before reading the diff.

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

• Write a concise description for a new pull request
• Shorten a lengthy pull request description
• Write a release note describing a visible user change