raycast/script-commands

Script Commands let you tailor Raycast to your needs. Think of them as little productivity boosts throughout your day.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 9th, 2026
Created on September 29th, 2020
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 950
Total Stargazers: 6,799 (+0)
Total Subscribers: 51 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.3 hours
Mean response time: 20.3 days
90th percentile: 3.9 days
Tracked items: 24

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • wontfix (3)
  • bug (1)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Raycast Script Commands is a collection of community-contributed scripts that extend Raycast, a desktop launcher application, with custom commands executable from anywhere on your system.

The tool solves the problem of repetitive tasks by allowing users to create and share lightweight scripts that automate everyday workflows. Rather than building full extensions, script commands let you write simple shell scripts that Raycast can execute through its launcher interface. This approach keeps the barrier to entry low while enabling quick productivity gains for tasks like data conversion, bookmark management, or triggering development workflows.

Script commands work best for users who want to customize Raycast without diving into extension development. They suit individual productivity needs and team-specific automation. The repository provides example scripts and community contributions that you can install directly into Raycast by selecting a script directory in the preferences. The tool recommends using ShellCheck to lint Bash scripts before sharing them. For more complex use cases requiring richer user interfaces or deeper integrations, the project points toward the Extensions API as an alternative.

The project maintains an active community repository of contributed scripts organized by application category. Development follows a structured approach where scripts must pass linting checks before acceptance, and template scripts requiring configuration are clearly marked in filenames. The repository provides clear documentation for both installing existing commands and creating new ones, with specific guidance on tooling and best practices.