Agent skill

Windows macOS Test Package

by swjybky in swjybky/deepwrite

按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包:使用 electron-builder 与 pnpm pack:test:,经 tools/run-test-package.mjs 编排,Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac…

Apache-2.0Auto-check passed

Install Windows macOS Test Package

skills CLI
$ npx skills add swjybky/deepwrite --skill windows-macos-test-package -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install swjybky/deepwrite windows-macos-test-package --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/swjybky/deepwrite.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/windows-macos-test-package .claude/skills/windows-macos-test-package && rm -rf skills-src

Use ~/.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/

Facts

Skill name
windows-macos-test-package
GitHub stars
586
Token cost
~778 tokens
SKILL.md length
228 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包:使用 electron-builder 与 pnpm pack:test:,经 tools/run-test-package.mjs 编排,Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac…

  • Calls pnpm

What it does

Windows macOS Test Package is an agent skill from swjybky/deepwrite. 按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包:使用 electron-builder 与 pnpm pack:test:,经 tools/run-test-package.mjs 编排,Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac 包”,或涉及测试安装包、electron-builder、pack:test、ad-hoc 签名、Gatekeeper、DMG 验证时;默认生成不会发布的测试包,正式包或发布包仅在用户明确要求并确认签名条件后处理。

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with macOS, Electron and pnpm. The licence is Apache-2.0.

Example prompts

  • “打 Win 包”
  • “打 Mac 包”
  • “/windows-macos-test-package”

What it can do on your machine

Read from SKILL.md and the folder at commit 69858fb. 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:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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

Windows macOS Test Package loads about 778 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 228 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~778

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

The full file from swjybky/deepwrite at commit 69858fb, republished under its Apache-2.0 licence (© swjybky). 228 words, ~778 tokens.

Download SKILL.mdSave it as .claude/skills/windows-macos-test-package/SKILL.md (or your agent's skills folder).
name
windows-macos-test-package
description
按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包:使用 electron-builder 与 pnpm pack:test:*,经 tools/run-test-package.mjs 编排,Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac 包”,或涉及测试安装包、electron-builder、pack:test、ad-hoc 签名、Gatekeeper、DMG 验证时;默认生成不会发布的测试包,正式包或发布包仅在用户明确要求并确认签名条件后处理。

Windows 与 macOS 测试安装包

用户提出打包、打测试包、打 Win 包、打 Mac 包,或修改测试安装包流程时,按下列规则执行。递增版本、清理旧包、发 GitHub Release 或更新 update.json 时,同时遵循 package-patch-release。

  • 当前桌面端是 Electron 工程,统一使用 electron-builder 和 apps/desktop/electron-builder.yml 打包;不得使用旧 Write Claw / DeepSeekWrite 项目的 Python、PyInstaller 或旧 DMG 脚本。
  • 用户只说“打包”“打测试包”“打 Win 包”或“打 Mac 包”时,默认生成不会发布的测试包。Windows 测试包可以不做代码签名;Mac 测试包必须对完整 .app 做 ad-hoc 签名,但不做 Apple 公证。只有用户明确要求“正式包”“发布包”并提供或确认签名条件后,才配置 Developer ID 签名、公证或上传发布。
  • 打包前必须从仓库根目录运行对应的 pnpm pack:test:* 命令。命令会先执行 pnpm verify,不得跳过类型检查、边界检查、测试和构建,也不得直接复用无法确认是否最新的 apps/desktop/out。
  • pnpm pack:test:* 必须通过 tools/run-test-package.mjs 统一编排,不得把脚本退回为直接串联 electron-builder。编排器会显式锁定打包用 Electron 版本,并在成功或失败退出前通过 tools/ensure-electron-runtime.mjs 恢复、验证当前主机的开发 Electron;打包完成后 pnpm dev 必须仍可启动。
  • 指令与命令映射:未指定平台的“打包”或“打全部测试包”使用 pnpm pack:test;Windows x64 使用 pnpm pack:test:win;Mac Apple Silicon / arm64 使用 pnpm pack:test:mac:arm64;Mac Intel / x64 使用 pnpm pack:test:mac:x64;同时生成两种 Mac 架构使用 pnpm pack:test:mac。
  • Windows 测试包优先在 Windows x64 环境构建;Mac 包必须在 macOS 构建。在 Apple Silicon Mac 上构建或运行 Intel 包时,需要具备可用的 x86_64 / Rosetta 环境。
  • 测试包输出目录固定为 apps/desktop/release/,文件名必须保留 DeepWrite-<version>-<os>-<arch>-test.<ext> 格式,不得临时改名覆盖其他架构或版本。
  • apps/desktop/scripts/electron-builder-before-build.cjs 会阻止 electron-builder 把 pnpm 依赖树重复装进 ASAR,因为当前运行时依赖已由 electron-vite 编译到 out。如果以后引入未打包的运行时依赖或原生 Node 模块,必须同步调整该钩子和 files 配置,并增加对应的安装包内运行验证。
  • Mac 测试包使用 apps/desktop/electron-builder.yml 中的 identity: "-" 让 electron-builder 对 Electron Framework、Helpers 和顶层 App Bundle 完成 ad-hoc 签名,并设置 hardenedRuntime: false、notarize: false。不得改回 identity: null:完全跳过签名会让 x64 App 未签名、arm64 App 只保留不完整的 linker ad-hoc 签名,经微信、浏览器等渠道下载并触发 Gatekeeper 后,可能被误报为“应用已损坏”。
  • 旧 Write Claw / DeepSeekWrite 打包流程中可借鉴的只有“组装完整 .app 后执行 codesign --force --deep --sign -,再执行 codesign --verify --deep --strict”这一签名原则;当前 Electron 工程应优先使用 electron-builder 原生的 identity: "-",不得重新引入旧 PyInstaller 或 DMG 脚本。
  • apps/desktop/scripts/verify-test-package.mjs 必须同时验证 DMG 校验和、codesign --verify --deep --strict 成功,并确认顶层 App Bundle 的签名详情包含 Signature=adhoc。只运行 apps/desktop/release/mac*/DeepWrite.app 的冒烟流程不能证明微信下载后的安装体验,因为未隔离的构建目录不会触发 Gatekeeper。
  • ad-hoc 签名只修复 App Bundle 的代码完整性,不会建立 Apple 信任链,也不能替代 Developer ID 签名和公证。通过微信、浏览器等渠道接收后,文件可能被重新添加 com.apple.quarantine;测试者仍可能需要右键打开、在“隐私与安全性”中选择仍要打开,或在确认包可信后手动移除隔离属性。不得声称 ad-hoc 测试包可以在所有 Mac 上无提示直接打开。
  • 交付 Mac 测试包前检查本地生成的 DMG 是否意外继承了旧文件的 com.apple.quarantine,若存在则从发布产物移除;但必须明确,传输工具可能在接收端重新添加该属性。
  • 成功标准:对应安装包存在且非空;同时检查生成的未打包应用目录,并尽可能运行安装包内的 DeepWrite 冒烟流程,确认主进程、Renderer、Preload 以及 core / agent / tool 三个 Utility 均可启动。若受当前操作系统限制无法运行目标平台产物,必须明确报告“只完成构建,未完成目标平台运行验证”。
  • 打包失败时报告失败的平台、架构、具体步骤和关键终端输出;不得在缺少签名凭据、目标平台环境或验证结果时声称正式发布包可用。

© swjybky, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/windows-macos-test-package of swjybky/deepwrite.

Open the folder on GitHubat commit 69858fb

Compare with similar skills

Windows macOS Test Package 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.

Windows macOS Test Package compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Windows macOS Test Package this skillswjybky/deepwrite586—~778Automated safety check: PassApache-2.0
Electron Releasepedronauck/skills634—~1.6kAutomated safety check: NotesNone
Desktop ElectronOpenHands/OpenHands90k—~302Automated safety check: PassMIT
Windows Releasemilind-soni/OpenMausBot4.2k—~1.5kAutomated safety check: PassApache-2.0
Tinyjstarwin/tinyjsapp707—~2.9kAutomated safety check: PassMIT
OpenGUI Installer for DSHCore-Mate/OpenGUI1.8k—~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Electron Release

    pedronauck/skills

    Expert guide for Electron production builds, code signing, notarization, auto-updates, and release workflows.

    634 GitHub stars~1.6k tokensUpdated 25 days ago
    MobileAuto-check: notes
  • Desktop Electron

    OpenHands/OpenHands

    This skill should be used when the user asks to "change the desktop app", "package Electron", "build a universal macOS app", "bundle Node or uv", "fix Electron startup", or changes electron/…

    90k GitHub stars~302 tokensUpdated today
    Auto-check passed
  • Windows Release

    milind-soni/OpenMausBot

    Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical OpenMausBot release and its legacy updater mirror.

    4.2k GitHub stars~1.5k tokensUpdated today
    MobileAuto-check passed
  • Tinyjs

    tarwin/tinyjsapp

    Build and modify tinyjs desktop apps — tiny macOS (and beta Windows/Linux) apps with a txiki.js JavaScript backend and a native webview window.

    707 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • OpenGUI Installer for DSH

    Core-Mate/OpenGUI

    Installs and verifies the latest stable OpenGUI release in a DeepSeek Harness web profile on macOS without disturbing existing plugins or settings.

    1.8k GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • 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.

    24k GitHub stars~780 tokensUpdated today
    Testing & QAAuto-check passed

More from swjybky/deepwrite

  • 构建并验证 DeepWrite Windows、macOS 测试安装包,按失败阶段诊断和恢复。用于打包、测试包、Win/Mac 包及相关流程修改;版本递增和发布另用 package-patch-release。

    586 GitHub stars~999 tokensUpdated yesterday
    Auto-check passed
  • Package Patch Release

    swjybky/deepwrite

    为 DeepWrite 桌面端递增一个 SemVer 补丁版本,安全清理上一个版本的测试打包残留,使用项目规定的 pnpm pack:test 命令构建并验证新安装包,按用户要求决定是否创建并发布 GitHub Release;Release 完整可下载后更新根目录 update.json,并通过路径限定提交和推送,保证该提交只包含…

    586 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Package Patch Release

    swjybky/deepwrite

    为 DeepWrite 递增补丁版本、清理旧产物、修复错误并继续打包;按授权发布 GitHub Release,发布验证后仅提交推送 update.json。用于打包新版本、提高一小个版本、清理旧包发布或更新发布清单。

    586 GitHub stars~675 tokensUpdated yesterday
    Auto-check passed
  • Git Commit

    swjybky/deepwrite

    在 DeepWrite 创建 Git 提交、推送、Pull Request 或合并时使用,核对变更范围、项目校验、提交身份与署名。

    586 GitHub stars~250 tokensUpdated yesterday
    Auto-check passed

Questions about Windows macOS Test Package

What does Windows macOS Test Package do?

按 DeepWrite 桌面端约定构建 Windows 与 macOS 测试安装包:使用 electron-builder 与 pnpm pack:test:,经 tools/run-test-package.mjs 编排,Mac 测试包做 ad-hoc 签名且不做 Apple 公证。用于用户提出“打包”“打测试包”“打 Win 包”“打 Mac…. Windows macOS Test Package is an agent skill from swjybky/deepwrite.

How do I install Windows macOS Test Package in Claude Code?

Run `npx skills add swjybky/deepwrite --skill windows-macos-test-package -a claude-code`. Or copy the skill folder (.claude/skills/windows-macos-test-package in swjybky/deepwrite) into .claude/skills/windows-macos-test-package in your project. Claude Code loads it when a task matches its description.

How do I install Windows macOS Test Package in Codex?

Run `npx skills add swjybky/deepwrite --skill windows-macos-test-package -a codex`. Or copy the skill folder (.claude/skills/windows-macos-test-package in swjybky/deepwrite) into .agents/skills/windows-macos-test-package in your project. Codex loads it when a task matches its description.

Can I use Windows macOS Test Package 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 swjybky/deepwrite --skill windows-macos-test-package -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/windows-macos-test-package, .gemini/skills/windows-macos-test-package, .github/skills/windows-macos-test-package and .opencode/skills/windows-macos-test-package in your project.

What does Windows macOS Test Package need to run?

Going by SKILL.md and its folder, Windows macOS Test Package needs the command-line tools its instructions call (pnpm).

Does Windows macOS Test Package access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Windows macOS Test Package 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 Windows macOS Test Package use?

Windows macOS Test Package is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Windows macOS Test Package use?

About 778 tokens (SKILL.md is roughly 3.1k 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 Windows macOS Test Package?

Skills that share tags, products or a category with Windows macOS Test Package: Electron Release (pedronauck/skills, 634 stars), Desktop Electron (OpenHands/OpenHands, 90k stars), Windows Release (milind-soni/OpenMausBot, 4.2k stars) and Tinyjs (tarwin/tinyjsapp, 707 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Windows macOS Test Package?

swjybky (a GitHub user) maintains it in swjybky/deepwrite, which has 586 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: swjybky/deepwrite on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.