shortcuts-generator

Generate signable .shortcut plist files for Apple Shortcuts.app import.

5|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/cranecj/shortcuts-generator --skill shortcuts-generator-cranecj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shortcuts-generator
Source: https://github.com/cranecj/shortcuts-generator/tree/main
Command: npx skills add https://github.com/cranecj/shortcuts-generator --skill shortcuts-generator-cranecj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably creating macOS/iOS Apple Shortcuts programmatically by generating correct .shortcut plist files that can be signed and imported into Shortcuts.app, avoiding fragile manual editing.

Core Features & Use Cases

  • Valid .shortcut plist generation: Builds the required WFWorkflowActions structure with correct UUID wiring and variable references.
  • Signing-ready output: Produces a plist/XML shortcut file that can be signed via the Shortcuts CLI workflow.
  • High-coverage action knowledge: Uses comprehensive references for actions, AppIntents, messages actions, filters, parameter typing, control-flow patterns, and root plist formatting.
  • Use case: Generate a “find today’s screenshots → OCR → save results to a note” style automation end-to-end, using the documented action identifiers and parameter conventions.

Quick Start

Ask your agent to generate a Shortcut that “finds my screenshots from today, runs OCR, and saves the extracted text to a note,” then sign the generated .shortcut plist and import it into Shortcuts.app.

Frequently Asked Questions about shortcuts-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Apple Shortcuts programmatically without using the GUI?

You can generate Apple Shortcuts programmatically by creating valid .shortcut plist files with correct WFWorkflowActions structures, variable references, and UUID wiring. This produces signable output ready for Shortcuts.app import without needing the graphical editor.

What is the file structure required to build a valid .shortcut file for macOS or iOS?

A valid .shortcut file requires a plist root structure containing WFWorkflowActions. You must use correct action identifiers, UUID/outputUUID attachment wiring, WFSerializationType usage, and parameter typing to ensure the file is accepted by Shortcuts.app.

Can I use control flow and content filters when creating Shortcuts via plist generation?

Yes, plist generation supports composing multi-step workflows with control flow patterns like repeat, conditional, and menu actions. It also handles content filters for photos, files, reminders, and messages using documented parameter conventions.

How do I sign a generated .shortcut file for Shortcuts.app import?

To sign a generated .shortcut file, you use the Shortcuts CLI workflow, specifically the 'shortcuts sign' command. The plist generation process produces signing-ready output that is compatible with this CLI signing requirement.

Why does my programmatically generated Shortcut fail to import into Shortcuts.app?

Programmatically generated Shortcuts fail to import when the .shortcut plist lacks correct root keys, has invalid action identifiers, or contains broken UUID/outputUUID attachment wiring. Proper WFSerializationType usage is required to prevent these import errors.