Different AI

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

Set up the OpenWork assistant in Slack for an approved private-alpha organization using its existing app and individual account connections. Configure permissions and reply settings, link the requesting member, and verify completed answers in DMs and allowed channels.

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

• Setting up @openwork in a Slack workspace
• Linking a member's Slack and OpenWork accounts
• Configuring allowed channels and reply visibility

Set up OpenWork for a team, from creating an organization and inviting members to sharing AI models and skills. It covers dashboard setup and terminal setup, with human ownership of accounts and shared access to provider keys.

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

• Create an OpenWork organization and invite teammates
• Share AI models without distributing provider keys to members
• Create a skill and share it with a team

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

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

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

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

Control a running OpenWork app from the shell to inspect UI changes and reproduce chat states. Start fresh sessions, select models, send prompts, wait for completion, capture screenshots, and run JavaScript, with no visible window by default.

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

• Inspecting an OpenWork UI change
• Reproducing a chat state in a fresh session
• Capturing screenshots after a model finishes

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

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

Manage the AI models offered through OpenWork, including model additions, removals, aliases, and pricing discounts. Validate configuration consistency and trigger the GitHub workflow that refreshes models from models.dev, then report its merge or failure result.

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

• Adding or removing models offered through OpenWork
• Changing the charged price fraction for specific models
• Checking consistency between model lists and aliases

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

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

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

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

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

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

Build and maintain interfaces with shadcn/ui by finding, adding, and combining components. The skill uses project settings, component documentation, and change previews to guide styling, debugging, preset changes, and updates that preserve local edits.

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

• Building settings pages and dashboards from existing components
• Fixing form and dialog composition issues
• Updating components while preserving local edits

Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.

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

• Checking changes for customer and partner identities
• Reviewing documents and test data for identifying details
• Reporting disclosure locations without repeating identities

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

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

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

Review changed UI code against numbered rules in DESIGN.md. Findings identify the relevant rule, affected lines, and a small fix for issues such as wording, component reuse, visual styling, accessibility, or missing screenshot evidence.

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

• Checking UI changes against documented design rules
• Reviewing button labels and access restriction messages
• Spotting inconsistent components, colors, and motion