Create signed macOS Shortcut files from workflow specifications.
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill shortcut-mujtaba3b
Please help me install this Agent Skill. Skill: shortcut Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/eng/skills/shortcut Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill shortcut-mujtaba3b
This Skill removes the friction of hand-building Apple Shortcuts in Shortcuts.app by turning a spec into a signed, importable workflow that can be installed with one manual click.
Ask the skill to turn your command or workflow spec into a signed macOS Shortcut, then open it for import and verify it after you click Add Shortcut.
High-intent search queries and answers about installing and using this skill.
To create signed macOS Shortcuts from a spec, you define a .shortcut-formatted input with correct workflow metadata and input-class declarations. The process authoring plist XML, wires UUIDs, and uses Shortcuts CLI signing to produce an installable workflow file.
Yes, you can build Run Shell Script bridges in macOS Shortcuts to launch your existing CLI or script. These signed workflows can be triggered from the menu bar, a hotkey, Siri, or a shortcuts:// URL.
Programmatically authoring an Apple Shortcut plist involves writing XML with the correct workflow structure, wiring UUID connections, and defining action parameters. This bypasses manual assembly in Shortcuts.app by generating the underlying plist directly.
To verify a macOS Shortcut was built and signed correctly, you check if the signing process produced a valid .shortcut file and confirm import handoff. Verification ensures the shortcut is runnable and handles pitfalls like stripped PATH or duplicate names.
Generating a .shortcut file requires a mandatory manual Add Shortcut click during import handoff. While authoring and signing are automated via the Shortcuts CLI, the final installation step requires user interaction within the Shortcuts.app interface.
A shell script bridge might fail when imported as a signed macOS Shortcut due to common pitfalls like a stripped PATH environment, incorrect input wiring, or duplicate workflow names. Verification checks confirm the shortcut is runnable and safely handle these errors.
CharlesWiltgenExpose iOS app functionality to Siri, Shortcuts, and Spotlight via App Intents.
Jansen611Decode signed macOS Siri Shortcut archives to XML, edit workflow plists, and re-sign them.
nsnguyenIntegrate Siri and App Intents for voice-driven meeting queries and note search.
cranecjGenerate signable .shortcut plist files for Apple Shortcuts.app import.
