@different-ai
Organization
Fun with LLMs
38 skills1 repository 24.2K
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.
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.
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.
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.
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.
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.
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.
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.
Write tests that demonstrate a pull request’s user-visible changes through before-and-after steps, screenshots, and recorded observations. Extend an existing core journey or create a one-off proof that helps reviewers understand the outcome and access boundaries.
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.
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.
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.
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.
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.
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.
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.
Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.
Introduce new users to OpenWork with explanations suited to their technical background. Cover file summaries, document creation, and organization, plus setup guidance for models, skills, plugins, and connections to external tools.
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.
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.
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.
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.
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.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)