cherri-language

Write, review, and debug Cherri code that compiles into Apple Shortcuts.

1|Updated May 25, 2020
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill cherri-language-titaneric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cherri-language
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/cherri-language
Command: npx skills add https://github.com/titaneric/dotfiles --skill cherri-language-titaneric

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing Apple Shortcuts programmatically requires learning the Cherri language's syntax, action signatures, includes, and compilation workflow, and mistakes like missing includes or invalid function scoping cause confusing compiler errors. ## Core Features & Use Cases - Authoring Cherri Code: Generate idiomatic .cherri files with correct includes, metadata defines, constants, variables, functions, and control flow. - Review and Debugging: Diagnose undefined action errors, type errors, function scope issues, and signing problems using compiler commands like cherri --debug and cherri --action=name. - Syntax Reference: Consult a bundled syntax reference covering types, interpolation, menus, raw actions, and best practices. - Use Case: Ask for a shortcut that shows device name, battery level, and system version, and receive a complete .cherri file with metadata defines plus the exact command to compile it. ## Quick Start Ask the assistant to write a Cherri shortcut that shows your device name and battery level, including the compile command.

Frequently Asked Questions about cherri-language

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

FAQPage Schema
How do I write an Apple Shortcut using the Cherri language?

Create a .cherri file with #include directives for needed action categories, #define metadata for name, color, and glyph, then write actions using constants and variables. Compile it with the command cherri file.cherri to produce the shortcut.

How do I fix an undefined action error in Cherri?

An undefined action error usually means the matching #include 'actions/category' directive is missing from your file. Verify the exact action signature locally with cherri --action=action_name or check the official docs at cherrilang.org.

What is the difference between constants and variables in Cherri?

Constants declared with const are immutable action output references that produce smaller shortcuts, while variables declared with @ can be mutated with operators like += and -=. Constants interpolate as {name} and variables as {@name}.

Why can't my Cherri function read outer variables?

Cherri functions run via runSelf() in isolated shortcut instances, so they cannot access outer variables. Pass all needed data as typed function arguments and return results with output().

Can I compile Cherri shortcuts on Linux or Windows?

Yes, the Cherri compiler runs on non-macOS platforms, but importing signed shortcuts requires the --hubsign flag or a configured signing server. On macOS you can compile and open directly with cherri file.cherri --open.