private-desktop-release
Skill0 starsChanged 50 days agoMITView on GitHub
Set up or operate private macOS desktop releases with Developer ID signing, Apple notarization, installers, licensed updates, device administration, and CI publication. Use for first-time distribution setup or a new private release, especially Electron apps; not for Mac App Store submission.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- ai-tools-updateSkill
- antickSkill
- app-pentestSkill
- branch-statusSkill
- build-review-loopSkill
- ci-cd-triageSkill
- code-auditSkill
- code-buildSkill
- code-debugSkill
- code-hardeningSkill
- code-refactorSkill
- code-reviewSkill
- code-securitySkill
- commit-messageSkill
- conciseSkill
- create-issueSkill
- database-auditSkill
- deep-wiki-htmlSkill
- dependency-auditSkill
- dependency-override-cleanupSkill
- dependency-upgrade-majorSkill
- dependency-upgrade-minorSkill
- documentation-generationSkill
- electron-appSkill
- github-actions-lockSkill
- github-actions-security-auditSkill
- interviewSkill
- make-senseSkill
- new-skillSkill
- performance-auditSkill
- plan-reviewSkill
- pr-descriptionSkill
- public-desktop-releaseSkill
- reclaim-dev-spaceSkill
- save-omarchy-window-layoutSkill
- setup-vercel-analyticsSkill
- simplifySkill
- skill-reviewSkill
- soc2-readinessSkill
- spec-statusSkill
- submit-reviewSkill
- sync-branchSkill
- system-storage-auditSkill
- test-suite-hardeningSkill
- update-skillsSkill
- use-chromeSkill
- vercel-domain-cleanupSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a repeatable private distribution system, or release through an existing one.
- Distinctive: line 23
Read repository instructions and Git status first.
- Distinctive: line 46
Do not copy another app's domains, team IDs, keys, bucket, license policy, paths, versions, package manager or runner label.
- Distinctive: line 51
Do not assume Electron. Keep another framework's signing/update integration and consult its official docs.
- Distinctive: line 53
Verify version-sensitive packager options against installed source/schema and current official documentation.
- Distinctive: line 77
Leave the target project with working automation, documented secret *names*, a release procedure linked from its agent instructions, and an …
- Distinctive: line 87
Use adaptation examples to check that this workflow fits the user's app and request.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Private Desktop Release
Create a repeatable private distribution system, or release through an existing one. The outcome is an installable signed app, access-controlled updates, and honest evidence that the installed update works. Signing and notarization alone do not provide licensing, download privacy, or device administration.
Choose the task
- First setup or repair: inspect the app, fill the missing parts, and verify the complete path. Read all references relevant to the missing parts.
- Routine release: inspect the existing runbook and current configuration, then use release operations and verification. Reuse healthy Apple/storage setup.
- Planning or diagnosis only: produce the requested plan or findings without changing accounts, publishing, installing, or blocking devices.
Read repository instructions and Git status first. Preserve user changes and follow the repository's commit policy unless the user overrides it. A skill invocation does not itself authorize pushes, publication, account/legal actions, production migrations, credential revocation, or availability tests. Honor scope already authorized in the conversation; do not ask again for the same action. Prepare concrete reviewable changes before requesting any missing approval.
Map this app before building
Record a short release plan with the actual values and open decisions:
| Area | Inspect or decide |
| App | Framework, packager/updater and installed versions, bundle ID, executable, current version |
| Toolchain | Desktop and root package managers/lockfiles, Node/runtime pins, CI architecture |
| Channels | Production vs development identity, profiles, endpoints, installed users and update compatibility |
| Distribution | Requested OS/architectures, DMG/ZIP or existing formats, private audience |
| Access | Existing licensing/accounts, device seats, update entitlement, offline policy, admin controls |
| Services | API/database, private object storage, download page, release publication path |
| Apple | Correct personal/organization team, usable signing identity, notarization credentials |
| Automation | Repository, protected branch/environment, CI gates, immutable tag convention |
| Evidence | Existing installed baseline, safe test device/account, tests and release records |
Do not copy another app's domains, team IDs, keys, bucket, license policy, paths, versions, package manager or runner label. For example, Feather's desktop may use pnpm even when its root uses Bun; inspect both. Reuse its actual stack and account model. Keep legitimate existing installations working when changing contracts.
Do not assume Electron. Keep another framework's signing/update integration and consult its official docs; apply the same authorization and artifact invariants. Verify version-sensitive packager options against installed source/schema and current official documentation. Do not upgrade dependencies merely to copy an example from newer documentation.
Implement the missing layers
- Apple setup: create or reuse the signing identity, configure notarization and CI secrets, validate the correct team.
- Private access and administration: enforce licensed installer/feed access, private storage, device policy and audit history.
- Desktop integration: separate development identity, package native resources, implement the update state and quit lifecycle.
- Release operations: automate exact-commit CI, signing, verification, immutable publication and resumable retries.
- Verification: test policy failures and the real installed update, then hand over a project-specific runbook.
Reuse existing modules and service boundaries. Add migrations and API contracts where needed; admin UI is a client of server policy. Implement sensible failure states instead of a happy-path-only demo. Carry out authorized independent work while waiting for account access or another genuine external prerequisite.
Required handoff
Leave the target project with working automation, documented secret names, a release procedure linked from its agent instructions, and an acceptance record. Separate implemented, locally tested, hosted-tested, production-published and installed-tested results. Include concrete gaps and the next action for each.
Normal releases should require a version, verified source, tag and workflow run, not repeated Apple setup. Do not publish extra versions just to demonstrate that updating works. Test the prior installed release against the next real release; if no signed baseline exists, prepare an agreed signed test baseline first.
Use adaptation examples to check that this workflow fits the user's app and request. These are decision examples, not permission to operate the named repositories or production systems.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

