agentleFS
Sign inStart free
artemnovichkovartemnovichkov/shortcuts-skill/skills/shortcuts/SKILL.md

shortcuts

Skill3 starsChanged 42 days agoMITView on GitHub

Manage and interact with macOS Shortcuts. Use this skill when the user wants to list available shortcuts, view a shortcut in the Shortcuts app, or run a shortcut. Supports running shortcuts with or without input parameters.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. AcKeskin/contexture★ 2same name
    2. jootsing-research/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the shortcuts list command to display all available shortcuts on the system.

    line 14
  2. Very specific:

    Use the shortcuts view command to open a specific shortcut in the Shortcuts app for editing or inspection.

    line 36
  3. Distinctive:

    Use quotes around the shortcut name if it contains spaces

    line 50
  4. Very specific:

    Use the shortcuts run command to execute a shortcut.

    line 59
  5. Distinctive:

    If a shortcut name doesn't exist, you'll see an error like:

    line 101
  6. Distinctive:

    Verify the exact name (including capitalization)

    line 108
  7. Distinctive:

    Use quotes if the name contains spaces

    line 109
  8. Distinctive:

    Always use quotes around shortcut names that contain spaces

    line 114
  9. Very specific:

    Use shortcuts list first if you're unsure of the exact name

    line 115
  10. Distinctive:

    Batch processing: Run shortcuts in loops or scripts for automation

    line 122
  11. Distinctive:

    Integration with other tools: Use shortcuts as part of larger workflows

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

macOS Shortcuts Skill

This skill provides integration with macOS Shortcuts, allowing you to list, view, and run shortcuts directly from the command line.

Available Commands

1. List Available Shortcuts

Use the shortcuts list command to display all available shortcuts on the system.

Command:

shortcuts list

When to use:

  • User asks to see all shortcuts
  • User wants to know what shortcuts are available
  • User needs to find a specific shortcut name

Example output:

My Morning Routine
Send Weekly Report
Process Screenshots
Convert to PDF

2. View Shortcut in Shortcuts App

Use the shortcuts view command to open a specific shortcut in the Shortcuts app for editing or inspection.

Command:

shortcuts view "<shortcut-name>"

When to use:

  • User wants to see how a shortcut is configured
  • User wants to edit a shortcut
  • User wants to inspect a shortcut's actions

Important:

  • The shortcut name must match exactly (case-sensitive)
  • Use quotes around the shortcut name if it contains spaces

Example:

shortcuts view "My Morning Routine"

3. Run a Shortcut

Use the shortcuts run command to execute a shortcut. You can optionally provide input to the shortcut.

Command (without input):

shortcuts run "<shortcut-name>"

Command (with input):

shortcuts run "<shortcut-name>" --input-path <file-path>

Or with text input:

echo "some text" | shortcuts run "<shortcut-name>"

When to use:

  • User wants to execute a shortcut
  • User needs to run a shortcut with specific input
  • User wants to automate a task using an existing shortcut

Important:

  • The shortcut name must match exactly (case-sensitive)
  • Use quotes around the shortcut name if it contains spaces
  • Some shortcuts may require input, while others don't
  • The output depends on what the shortcut returns

Examples:

# Run a simple shortcut
shortcuts run "Convert to PDF"

# Run a shortcut with file input
shortcuts run "Process Image" --input-path /path/to/image.jpg

# Run a shortcut with text input
echo "Hello World" | shortcuts run "Translate to Spanish"

Error Handling

If a shortcut name doesn't exist, you'll see an error like:

The shortcut "Name" could not be found.

In this case:

  1. First run shortcuts list to see available shortcuts
  2. Verify the exact name (including capitalization)
  3. Use quotes if the name contains spaces

Tips

  • Shortcut names are case-sensitive
  • Always use quotes around shortcut names that contain spaces
  • Use shortcuts list first if you're unsure of the exact name
  • Some shortcuts may take time to execute, so be patient
  • Shortcuts can return various types of output (text, files, etc.)

Common Use Cases

  1. Listing shortcuts before running: First list all shortcuts to find the exact name, then run it
  2. Batch processing: Run shortcuts in loops or scripts for automation
  3. Integration with other tools: Use shortcuts as part of larger workflows
  4. Quick automation: Access powerful macOS automation without leaving the terminal

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free