siri-shortcut-editing

Decode signed macOS Siri Shortcut archives to XML, edit workflow plists, and re-sign them.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Jansen611/Agent-Skills --skill siri-shortcut-editing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: siri-shortcut-editing
Source: https://github.com/Jansen611/Agent-Skills/tree/main/skills/siri-shortcut-editing
Command: npx skills add https://github.com/Jansen611/Agent-Skills --skill siri-shortcut-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Editing macOS Siri Shortcuts normally requires a fragile GUI workflow that is hard to repeat and easy to break, especially when the shortcut is signed and stored as a binary .shortcut archive.

Core Features & Use Cases

  • Decode signed .shortcut files to editable XML: Converts an AEA1-signed archive into a workflow bplist represented as XML.
  • Programmatically modify workflow logic: Lets you update actions, parameters, and variable wiring by editing the XML safely and deterministically.
  • Re-sign and repackage back into a valid .shortcut: Produces an importable signed shortcut, preserving the expected archive structure and extension constraints.
  • Use Case: Update a production shortcut that posts data to an API and refactors the variable/token wiring without manually re-creating every action in the Shortcuts app.

Quick Start

Ask the agent to edit MyShortcut.shortcut into MyShortcut.xml, apply your XML changes, then re-sign it back into MyShortcut.shortcut.

Frequently Asked Questions about siri-shortcut-editing

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

FAQPage Schema
How do I edit a signed macOS Siri Shortcut .shortcut file programmatically?

To edit a signed macOS Siri Shortcut .shortcut file programmatically, you must decode the AEA1 archive to XML, modify the embedded workflow bplist, and re-sign the result using macOS signing tools to ensure it remains importable.

Can I update Shortcut workflow parameters and variables without using the Shortcuts app GUI?

Yes, you can update Shortcut workflow parameters and variables without the GUI by decoding the signed archive into an editable XML representation, safely modifying the action logic deterministically, and re-signing the package.

What is the AEA1 decode pipeline used for in Siri Shortcut automation?

The AEA1 decode pipeline is used in Siri Shortcut automation to extract the binary workflow bplist from a signed .shortcut archive and represent it as XML, enabling safe and repeatable programmatic modifications.

Does re-signing an edited Siri Shortcut require specific macOS tools and extension handling?

Yes, re-signing an edited Siri Shortcut requires using the macOS shortcuts sign tool and strict .wflow extension handling to repackage the modified bplist back into a valid, importable .shortcut archive structure.

Why does editing a signed .shortcut archive manually break the import structure?

Editing a signed .shortcut archive manually breaks the import structure because the binary format requires an AEA1-aware decode pipeline to correctly extract and round-trip the XML-to-bplist data before re-signing.

Is this programmatic Shortcut editing approach suitable for automating repeatable maintenance across multiple workflows?

Yes, this programmatic Shortcut editing approach is suitable for automating repeatable maintenance across multiple workflows, allowing you to refactor action parameters and variable outputs deterministically without GUI drift.