Trigger OnlySwitch built-in actions from plain-language requests on macOS. The skill selects the matching action ID and opens an app link to toggle settings or run actions such as emptying the trash.
Invoke OnlySwitch built-in switches or buttons via deeplink. Use when the user asks to toggle or trigger an OnlySwitch action (e.g. empty trash, keep awake, dark mode, mute, hide desktop, clear clipboard, eject discs, Xcode derived data, and any other built-in switch or button). Resolve the request to the correct switch id and open the onlyswitch deeplink.
Review the instructions the agent will receive before you install.
Invoke OnlySwitch built-in switches or one-shot buttons by opening its deeplink. OnlySwitch must be installed and allowed to handle the onlyswitch:// URL scheme.
Resolve intent to switch id
Map the user's request to a single built-in switch/button using references/switch-ids.md. Match phrases like "empty trash", "toggle keep awake", "mute mic", "clear xcode cache" to the correct id (e.g. empty trash → 16384, keep awake → 16).
Open the deeplink
Run on the user's machine (macOS):
open "onlyswitch://run?type=builtIn&id=<id>"
Replace <id> with the numeric id from the reference table. Example for "empty trash":
open "onlyswitch://run?type=builtIn&id=16384"
Confirm
Tell the user which action was triggered (e.g. "Emptied trash via OnlySwitch" or "Toggled Keep Awake via OnlySwitch").
SwitchType in the OnlySwitch app (see project's SwitchType.swift for the source of truth; this skill's reference table is derived from it).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review Apple platform app code for potential App Store rejection issues before submission. Check privacy, payments, safety, performance, and design using guideline references, risk categories, code examples, and a pre-submission checklist.
Review Swift async/await code, which runs tasks without blocking while waiting. Check shared state, task structure, cancellation, streams, and migration issues, then receive file-specific findings with before-and-after fixes and a prioritized summary.
Write and review unit and integration tests with Swift Testing. Check assertions, asynchronous behavior, and test structure, or convert existing XCTest tests using guidance on modern APIs and project conventions.
Review SwiftUI code for outdated APIs, data flow, navigation, accessibility, and performance. Receive findings grouped by file, with line references, brief before-and-after fixes, and a prioritized summary of the changes that matter most.
Turn specifications into a detailed implementation plan before coding. Break work into small tasks with exact file paths, code, test commands, and interfaces so another developer or agent can follow the plan.