mcpField
D
desktop-os-integration

desktop-os-integration

github.com/sylphxaiDevelopment154 installsUpdated today
Repository

About desktop-os-integration

desktop-os-integration is a skill for reviewing desktop software integration with operating systems. It helps product and release teams assess installation, updates, permissions, data handling, and platform-specific readiness, and produce tests and blockers.

Key features

  1. 01Review installation and update behavior
  2. 02Assess permissions, storage, and credentials
  3. 03Check notifications, startup, and file handling
  4. 04Define signing and rollback release gates
  5. 05Create OS readiness and regression plans

Use cases

  1. 01Reviewing desktop app release readiness
  2. 02Planning cross-OS regression tests
  3. 03Identifying integration and security blockers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill desktop-os-integration

After installing, type/desktop-os-integrationin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/desktop-os-integration-matrix.md

Details

From the project README

Desktop OS Integration

Use this skill to make desktop software feel trustworthy on the user's machine.

Workflow

  1. Identify OS targets, distribution channel, install model, local data risk, and enterprise constraints.
  2. Read references/desktop-os-integration-matrix.md.
  3. Review install/update/uninstall, permissions, storage, credentials, notifications, startup, files, and backup.
  4. Separate platform conventions from product-specific choices.
  5. Define release gates for signing, notarization, updater safety, crash reporting, rollback, and enterprise controls.
  6. Produce OS-specific readiness matrix, explicit regression test plan, and blockers.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide background behavior, startup persistence, or data retention.
  • Do not store secrets in plain local files.
  • Uninstall and backup behavior must be intentional.
  • Do not approve release without update, rollback, permission reset, and cross-OS compatibility tests.

Output format

OS targets:
Distribution:

Integration matrix:
- <area> -> macOS, Windows, shared behavior

Blockers:
- <blocker>

User-facing settings:
- <setting>

Regression test plan:
- Install/update/rollback/uninstall:
- Permissions reset/degraded mode:
- File association/deep link/drag-and-drop:
- Login item/tray/menu bar/notifications:
- Enterprise/silent install/support diagnostics:

Comments

Markdown supported