Cherry Studio Regression Tests
CherryHQ/cherry-studio
Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.
Checks a published OpenWork desktop release by booting the released macOS binaries through packaged journeys, verifying signing and updater manifests, and publishing evidence.
Install OpenWork Release Validation
$ npx skills add different-ai/openwork --skill validate-a-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai/openwork validate-a-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/validate-a-release .claude/skills/validate-a-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .claude/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add different-ai/openwork --skill validate-a-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai/openwork validate-a-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/validate-a-release .agents/skills/validate-a-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .agents/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill validate-a-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai/openwork validate-a-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/validate-a-release .cursor/skills/validate-a-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .cursor/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/different-ai/openwork.git --path .opencode/skills/validate-a-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add different-ai/openwork --skill validate-a-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai/openwork validate-a-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/validate-a-release .gemini/skills/validate-a-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .gemini/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install different-ai/openwork validate-a-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add different-ai/openwork --skill validate-a-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/validate-a-release .github/skills/validate-a-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .github/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill validate-a-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai/openwork validate-a-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/validate-a-release .opencode/skills/validate-a-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "validate-a-release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/validate-a-release into .opencode/skills/validate-a-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-a-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
validate-a-release- GitHub stars
- 24k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 591 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks a published OpenWork desktop release by booting the released macOS binaries through packaged journeys, verifying signing and updater manifests, and publishing evidence.
- Works in 5 steps: Download and unpack → Signing and notarization → Updater manifests → …
- Confirming a published OpenWork desktop release is safe to roll out
- SKILL.md covers 1. Download and unpack, 2. Signing and notarization, 3. Updater manifests and 4. Journeys (from the repo root), plus 2 more sections
- Calls pnpm, gh and git
What it does
Run after the release workflow reports a published GitHub release, this skill tests only the artifacts users download and never a local build. It needs a macOS arm64 host, MySQL on `127.0.0.1:3306` started with `pnpm dev:den:mysql`, an authenticated `gh` and a clean checkout, because the evidence is tied to its git HEAD. The agent downloads the enterprise and cloud mac-arm64 zips and the updater `.yml` files for the release under test, keeping the previous release in mind as the build existing users update from.
Checks run in order. `codesign` and `spctl` must report the apps as accepted and notarized under the Different AI Developer ID. Every manifest must carry the tested version and point to URLs that exist among the release assets, and any MISSING, MISMATCH or wrong version stops the run with a report. Packaged journeys then boot copies of the apps through `pnpm evals:e2e`, starting with a fresh enterprise install that shows the activation gate without render crashes. Extracted bundles are never launched directly, because the app can swap in a newer public release when it quits, so each journey gets a throwaway APFS clone.
When your agent uses it
- Confirming a published OpenWork desktop release is safe to roll out
- Verifying code signing and notarization of the released macOS apps
- Checking updater manifests against the assets attached to a release
- Booting released binaries through packaged first-launch journeys
Example prompts
- “Validate the latest OpenWork release before we announce it.”
- “Check that the updater manifests for this release point at assets that really exist.”
- “Verify signing and notarization on the released enterprise and cloud apps.”
Requirements
- A macOS arm64 machine
- MySQL on 127.0.0.1:3306, started with `pnpm dev:den:mysql`
- Authenticated GitHub CLI (`gh`) and a clean OpenWork checkout
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Download and unpack
- Signing and notarization
- Updater manifests
- Journeys (from the repo root)
- Publish evidence
What it can do on your machine
Read from SKILL.md and the folder at commit e7d03dd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmghgitopensslbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
OpenWork Release Validation loads about 1.7k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 591 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 591 words (~1,711 tokens).
“Run after release reports the GitHub release published. Every check runs on the artifacts users download, never on a local build. macOS arm64 host, MySQL on 127.0.0.1:3306 (pnpm dev:den:mysql), gh authenticated. Work from a clean checkout (evidence is bound to…”
- name
- validate-a-release
Files
Just SKILL.md in .opencode/skills/validate-a-release of different-ai/openwork.
Open the folder on GitHubat commit e7d03dd
Compare with similar skills
OpenWork Release Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OpenWork Release Validation this skilldifferent-ai/openwork | 24k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Cherry Studio Regression TestsCherryHQ/cherry-studio | 52k | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| CI CD And Automationdzhalaevd/Donatello | 135 | 7 repos | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Desktop Release Sync LandingEynzof/Hermes-CN-Desktop | 1.7k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Create Featurezacharyfmarion/openscad-studio | 238 | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Deploy Observabilityaliyun/alibabacloud-observability-mcp-server | 166 | — | ~2.6k | Automated safety check: Notes | None |
Similar skills
CI CD And Automation
dzhalaevd/Donatello
Automates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello.
Desktop Release Sync Landing
Eynzof/Hermes-CN-Desktop
Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users.
Create Feature
zacharyfmarion/openscad-studio
A skill your agent uses when the user asks to take a feature or bug fix from prompt to implementation, especially prompts like "/create a new feature", "build this feature end-to-end", "take this…
Deploy Observability
aliyun/alibabacloud-observability-mcp-server
Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).
Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
More from different-ai/openwork
All 32 skills in this repoOpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
OpenWork Model Alias Manager
different-ai/openwork
Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.
Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Daytona Sandbox Operations
different-ai/openwork
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Related
Categories
Questions about OpenWork Release Validation
What does OpenWork Release Validation do?
Checks a published OpenWork desktop release by booting the released macOS binaries through packaged journeys, verifying signing and updater manifests, and publishing evidence. Run after the release workflow reports a published GitHub release, this skill tests only the artifacts users download and never a local build.1:3306` started with `pnpm dev:den:mysql`, an authenticated `gh` and a clean checkout, because the evidence is tied to its git HEAD.
When should I use OpenWork Release Validation?
OpenWork Release Validation fits situations like: confirming a published OpenWork desktop release is safe to roll out; verifying code signing and notarization of the released macOS apps; checking updater manifests against the assets attached to a release; booting released binaries through packaged first-launch journeys.
How do I install OpenWork Release Validation in Claude Code?
Run `npx skills add different-ai/openwork --skill validate-a-release -a claude-code`. Or copy the skill folder (.opencode/skills/validate-a-release in different-ai/openwork) into .claude/skills/validate-a-release in your project. Claude Code loads it when a task matches its description.
How do I install OpenWork Release Validation in Codex?
Run `npx skills add different-ai/openwork --skill validate-a-release -a codex`. Or copy the skill folder (.opencode/skills/validate-a-release in different-ai/openwork) into .agents/skills/validate-a-release in your project. Codex loads it when a task matches its description.
Can I use OpenWork Release Validation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add different-ai/openwork --skill validate-a-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-a-release, .gemini/skills/validate-a-release, .github/skills/validate-a-release and .opencode/skills/validate-a-release in your project.
What does OpenWork Release Validation need to run?
Going by SKILL.md and its folder, OpenWork Release Validation needs the command-line tools its instructions call (pnpm, gh, git, openssl and bash). Our summary lists: A macOS arm64 machine; MySQL on 127.0.0.1:3306, started with `pnpm dev:den:mysql`; Authenticated GitHub CLI (`gh`) and a clean OpenWork checkout.
Does OpenWork Release Validation access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is OpenWork Release Validation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does OpenWork Release Validation use?
OpenWork Release Validation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does OpenWork Release Validation use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to OpenWork Release Validation?
Skills that share tags, products or a category with OpenWork Release Validation: Cherry Studio Regression Tests (CherryHQ/cherry-studio, 52k stars), CI CD And Automation (dzhalaevd/Donatello, 135 stars), Desktop Release Sync Landing (Eynzof/Hermes-CN-Desktop, 1.7k stars) and Create Feature (zacharyfmarion/openscad-studio, 238 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenWork Release Validation?
different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,920 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.
Source: different-ai/openwork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.