Most starter templates hand you a blank canvas and wish you luck. This one comes pre-wired with the boring scaffolding that every serious shortcut ends up needing anyway: static variables, a prerequisite check, a real config system, and a built-in updater. You build on top of it instead of reinventing the plumbing each time.
What it actually does
Think of it as a skeleton you copy and fill in. Out of the box it sets up a block of standard static variables, runs a prerequisite software process before your logic fires, and reads user settings from a separate config file. Because that config lives in a schema-driven file rather than inside the shortcut, your customisations survive an update instead of getting wiped. When the schema gains a new option, the template notices and re-prompts you for it.
Updating is the other headline piece. A copy built from this template can check for a newer version, let you skip a release you don’t want, and defer the check to later if you’re busy.
Getting it set up
- Tap Add Shortcut on this page to open MoE Template in the Shortcuts app.
- Scroll the preview to the bottom and tap Add Shortcut to confirm the import.
- Run it once so the prerequisite process and config file get created.
- Rename the copy and start swapping in your own actions where the template marks them.
Running the shortcut
You don’t really “use” this one the way you’d use a download tool. You build with it. Duplicate the template, then drop your own logic into the body while leaving the scaffolding intact. The config and update sections are designed to keep working untouched, so the smart move is to extend rather than gut them.
Where the design really pays off is the config file. Settings are stored on the local file system, separate from the iCloud-synced shortcut, which is the same pattern the author uses across their other shortcuts for keeping secrets and preferences out of the shared copy. Edit the file, and the next run reads your values. Push out a template update later and those values stay put, because they were never baked into the shortcut to begin with.
One thing to flag: there’s no automatic distribution channel for the template itself. New versions don’t get pushed to you. You have to come back to the RoutineHub page manually to grab the latest build.
FAQ
Do I need any other apps to use this?
No extra apps. There are no listed dependencies, so a stock Shortcuts install is enough. Whatever you build on top of it might pull in other apps, but the scaffolding itself doesn’t.
What’s the point of the separate config file?
It keeps your settings from being overwritten when you install a newer template build. Being schema-based and file-based, the config lets the shortcut read your preferences from disk rather than hardcoding them. A side benefit: when a new option appears in the schema, you get re-prompted instead of silently missing it.
Why doesn’t it update itself automatically?
The version checker inside a copy can tell you something’s available and let you skip or defer it, but the template can’t reinstall itself from RoutineHub. For a brand-new version you open the page and download it again by hand.
