skillissue.sh

house / Raycast

✓ hosted skill bundledesktopv1.0.0MIT17 KB
skills/raycast/SKILL.md

No official Raycast MCP. The skill is file-native + deeplink operations.

InstallCLI + MCP
CLIRun from your local shell.
$autovault add jack-arturo/skillissue@775e1e1620d2730c8a67e8b7958448e3e888dfc2:skills/raycast/SKILL.md --sync-profiles
MCPPaste into an agent MCP tool call.
>add_skill({ source: "github", identifier: "jack-arturo/skillissue@775e1e1620d2730c8a67e8b7958448e3e888dfc2:skills/raycast/SKILL.md" })
Choose CLI for a shell install or MCP for an agent tool call.
Source
Example type
bundle
hosted skill bundle
Bundle files
4
SKILL.md + resources
Resources
3
inspectable source files
Declared agents
3
from frontmatter
Source
house
pinned GitHub bundle
SKILL.mdview raw →
---
name: raycast
description: >-
  Operate Raycast on Jack's Mac via deeplinks, Script Commands, AI
  providers.yaml/Skills/Commands/Agents, PromptLab, clipboard history, or
  Superwhisper toggle. Delegate Autohub script install to raycast-autojack.
license: MIT
tags:
  - raycast
  - desktop
  - macos
  - deeplink
  - script-commands
  - ai
  - autohub
agents:
  - claude-code
  - codex
  - autojack
category: desktop
metadata:
  version: "1.0.0"
  app_bundle: com.raycast.macos
  app_path: /Applications/Raycast.app
  related_skill: raycast-autojack
capabilities:
  network: false
  filesystem: readwrite
  tools:
    - Bash
    - Python
requires-secrets: []
resources:
  - path: references/control-surfaces.md
    type: file
  - path: references/ai-config.md
    type: file
  - path: references/troubleshooting.md
    type: file
---

raycast

Drive Raycast from agents without a first-party ops CLI and without

an MCP. There is no FlashSpace-style inventory CLI. npx ray is for

extension authors (build/lint), not day-to-day control. Do not

build a Raycast MCP unless a real control API appears — it would only

wrap the same deeplinks/files.

Sibling skill: raycast-autojack owns Autohub raycast/ install,

doctor, sync, smoke. This skill owns general Raycast operation +

file-native AI config.


When to use

User intentDo thisDetails
"Open clipboard history / paste queue"deeplink built-in clipboard commandsreferences/control-surfaces.md
"Run Raycast command X"Copy/construct deeplink → openreferences/control-surfaces.md
"Add/edit a Script Command"write file under Script Directoryreferences/control-surfaces.md
"Point Raycast AI at AutoJack"edit providers.yamlreferences/ai-config.md
"Reusable AI instructions as code"write Raycast AI Skills (SKILL.md)references/ai-config.md
"One-shot AI prompt as a command"AI Commands JSON → Import AI Commandsreferences/ai-config.md
"Change my Agent preset instructions"draft text; Jack applies in Settings → AI → Agentsreferences/ai-config.md
"Install Autohub quick-reply / voice-note scripts"raycast-autojack skillsee below
"Something isn't working / verify setup"run Doctor, check the symptom tablereferences/troubleshooting.md
"Configure every extension pref / Agent UI field"cannot fully automate — open settings, assist

Safety / autonomy

ClassOpsPolicy
🟢 GreenInventory manifests; open known-safe deeplinks; read providers.yaml structure (redact secrets); list Script Directories; draft AI Skills / AI Command JSONRun freely
🟡 YellowEdit Script Commands; edit providers.yaml models/base_url; write AI Skills under ~/.config/raycast/skills; open Import/Create AI Command UI; deeplinks that change app state (mute, caffeinate, send Slack, …)State intent; proceed if clear
🔴 RedPaste/read API keys into chat; rewrite .rayconfig bulk import blindly; delete Agents/commands en masse; edit encrypted SQLite under Application Support; change OAuth tokens in prefsAlways confirm; never dump secrets

Never print ~/.config/raycast/config.json or raw API keys from

providers.yaml into the conversation.


Architecture (what is / isn't agent-writable)

Supported config surfaces

AssetPath / mechanismWritable?
Deeplink launchraycast://extensions/<author>/<ext>/<cmd>Invoke only
Script Commandse.g. ~/Documents/Raycast Scripts/Yes (files)
AI providers~/.config/raycast/ai/providers.yamlYes (YAML)
AI Skills~/.config/raycast/skills/<name>/SKILL.md (+ default scan dirs)Yes
AI CommandsUI create/edit; Import AI Commands from JSONDraft + import
Agents (ex-Presets)Settings → AI → Agents; ray.so/presetsUI / share links
PersonalizationSettings → AI → PersonalizationUI
Extension preferencesRaycast Settings → ExtensionsUI (no write API)
Bulk backupExport/Import Preferences & Data (.rayconfig)UI, coarse

Not supported (don't fake it)

  • Programmatic CRUD of every extension preference
  • Silent Store install + OAuth without user
  • Reading live Raycast UI state from raycast-enc.sqlite
  • Treating plist keys under com.raycast.macos as a stable API

Autohub Raycast scripts (`raycast-autojack`)

Repo path: autohub/raycast/quick-reply.js, context-reply.js,

voice-note-raycast.js, summon-autojack.js, install.sh, …

# from autohub repo root, via the dedicated skill helper:
autovault skill doctor raycast-autojack --repo .
autovault skill setup raycast-autojack --repo .
autovault skill sync raycast-autojack --repo .
autovault skill smoke raycast-autojack --repo .

Do not re-implement installers in this skill; load raycast-autojack.


Anti-patterns

  • Do not invent an MCP server that only shells open raycast://….
  • Do not use npx ray as an ops tool.
  • Do not cat secrets from config.json / providers.yaml api_keys.
  • Do not hand-edit raycast-enc.sqlite or treat plist keys as API.
  • Do not confuse Raycast AI Skills with AutoVault operator skills — different consumers; share formats carefully.
  • Do not claim Agents/extension prefs are fully automatable.
  • Prefer flashspace CLI over FlashSpace Raycast extension for workspace switching when both exist.

Reference files

FileRead when
references/control-surfaces.mdLaunching a Raycast command (deeplinks, known Autohub deeplinks, installed-extension inventory) or writing/editing a Script Command; also window-management alternatives.
references/ai-config.mdConfiguring Raycast AI: providers.yaml, AI Skills, AI Commands, Agents (presets), Personalization, PromptLab.
references/troubleshooting.mdRunning the Doctor check, or diagnosing a symptom (deeplink/script/AI Skill not working) — plus upstream Raycast doc links.

Related skills

SkillRole
raycast (this)General operate + file-native AI config
raycast-autojackAutohub script install/doctor/sync/smoke
flashspaceVirtual workspaces (CLI)
story.md

Why it exists

No official Raycast MCP. The skill is file-native + deeplink operations.

History

1.0.0

Synced to claude-code/codex/autojack; pairs with raycast-autojack.

How Jack actually uses it

Deeplinks, Script Commands, AI skill imports — UI-only prefs stay manual.

What it is not

Not a generic tutorial. It's the house runbook for this machine and these agents.

Bundle contents

Every file declared by this skill is inspectable here. Static resources are previewed from same-origin hosted files; script-like files are shown as text only.

4files
markdownSKILL.md
view raw →

SKILL.md

Primary agent instructions, frontmatter, workflow, and declared resource manifest.

Select a package file to inspect it.

Declared capabilities

network
false
filesystem
readwrite
tools
Bash,Python

No secrets declared by this package.

Public, pinned, and inspectable

This house package is installed from the pinned Git commit shown here. Inspect the source and every bundled file before you run it.

package pin775e1e1sourceGitHub packagecompatibilityclaude-code, codex, autojack
VersionBundleSourcePinRaw
v1.0.0latest4 files · 17 KBhouse775e1e1SKILL.md