raycast-compat

Shim the @raycast/api to Orchestra equivalents for Raycast extension compatibility.

3|1|Updated Feb 27, 2026

Search Tags:#compatibility #migration #extension #raycast #quick actions #api shim

One-click install

npx skills add https://github.com/orchestra-mcp/framework --skill raycast-compat

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: raycast-compat
Source: https://github.com/orchestra-mcp/framework/tree/main/.claude/skills/raycast-compat
Command: npx skills add https://github.com/orchestra-mcp/framework --skill raycast-compat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables the use of existing Raycast extensions within the Orchestra environment, significantly expanding the available tools and utilities without requiring developers to rewrite them.

Core Features & Use Cases

Raycast API Shimming: Provides compatibility for core Raycast APIs like List, ActionPanel, and showToast, mapping them to Orchestra's equivalents.
Extension Migration: Simplifies the process of porting Raycast extensions to Orchestra by handling API differences.
Quick Actions: Allows for the creation and execution of quick-action style extensions, similar to Raycast's functionality.
Use Case: You can now leverage a vast library of community-built Raycast extensions for tasks like managing notes, interacting with APIs, or performing system utilities directly within your Orchestra IDE.

Quick Start

Migrate a Raycast extension by replacing the @raycast/api import with @orchestra/raycast-compat in your project's package.json.

Frequently Asked Questions about raycast-compat

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

FAQPage Schema

How do I run Raycast extensions in Orchestra?▼

To run Raycast extensions in Orchestra, use a compatibility layer that shims `@raycast/api` to Orchestra equivalents, allowing direct execution without rewriting the extension code.

Can I use Raycast ActionPanel and List components in Orchestra?▼

Yes, Raycast API components like `List`, `ActionPanel`, and `showToast` are mapped to Orchestra's internal systems, enabling UI components and notifications to function correctly.

Does porting Raycast extensions to Orchestra require rewriting the entire extension?▼

No, porting Raycast extensions to Orchestra does not require a full rewrite because the compatibility shim handles API differences by mapping Raycast APIs directly to Orchestra equivalents.

What are the limitations of using a Raycast API shim in Orchestra?▼

The Raycast API shim supports features like lists, forms, actions, and notifications, but any Raycast APIs without dedicated Orchestra equivalents may not be fully functional during migration.