菜单
Route a Raycast task to the right spoke — build an extension/command, build an AI extension (tools the Raycast AI calls), publish to the Store, or design a Raycast-aesthetic UI in your own app. USE WHEN a user wants to work with Raycast but the specific concern isn't named.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Sheshiyer/skill-clusters --skill raycast-orchestrator命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.
Shared reference for the Selemene cluster: the two report surfaces (deterministic Rust reports vs. narrative witness-pipeline readings), the @selemene/bridge CLI contract, the output manifest format, and non-prescriptive witnessing tone. USE WHEN deciding which Selemene surface to invoke or when routing between birth/compatibility/transit reports and solo/dyadic readings.
Route Selemene Engine tasks to the right surface: deterministic reports (birth/compatibility/transit) via selemene-core and the @selemene/bridge CLI, or narrative witness readings via selemene-report. USE WHEN the user wants anything under the Selemene/Noesis umbrella but has not named the exact surface.
正在显示 SKILL.md
| name | raycast-orchestrator |
| description | Route a Raycast task to the right spoke — build an extension/command, build an AI extension (tools the Raycast AI calls), publish to the Store, or design a Raycast-aesthetic UI in your own app. USE WHEN a user wants to work with Raycast but the specific concern isn't named. |
| cluster | raycast |
| version | 1.0.0 |
Entry skill for Raycast work. It separates the four distinct jobs people mean by "Raycast" and
routes accordingly. The extension model (command types, manifest, @raycast/api, data, build)
lives in raycast-core.
raycast-core — command types, the package.json manifest, UI/navigation, preferences, data/storage hooks, build/develop/publish.raycast-extension — build an extension/command with React + TypeScript (the hands-on building spoke).raycast-ai-extensions — AI extensions: declare tools[] the Raycast AI can call, with instructions, confirmations, and evals.raycast-store-publishing — package and submit to the Raycast Store (metadata, icon, screenshots, PR + review).raycast-ui-skills — design your own app to look like Raycast (light mode, Inter, 4px grid). Not the extension API.raycast-extension (+ raycast-core for the model).raycast-ai-extensions.raycast-store-publishing.raycast-ui-skills (aesthetic only).raycast-core (command mode, manifest entries, the right @raycast/api container).raycast-store-publishing.See raycast-core. Keep the package.json manifest in sync with code; confirm destructive
actions; never expose secrets from preferences; for AI tools, gate side-effecting tools behind
confirmation. Defer changing API specifics to developers.raycast.com.
To keep CLI startup context lean, this cluster's spokes are not separately registered as skills — only this orchestrator and its *-core are enumerated. When you route to a spoke named above, load it on demand by reading its file:
~/.agents/skill-clusters/skills/<spoke-name>/SKILL.md (or skills/<spoke-name>/SKILL.md inside the skill-clusters repo).