Loading...
Product
Core Features
Top Extensions
Company
Search and manage AI agent skills from Skills directly in Raycast.
skills.sh before installingSearch for agent skills from skills.sh with real-time results. Results show which skills are installed locally and flag skills that may conflict with a local install from another source. Open a result to view full-screen details, including security audit status when available.
View installed skills discovered by the Skills CLI, grouped by management source. The extension verifies the installed GitHub skill contents against the CLI lock before enabling removal. Removal is available for verified Codex and Claude Code installations. Other local or externally managed skills remain available for reading, opening, and copying. For local-path installs, the source and dates are shown as recorded lock-file details, not verified ownership. Outdated verified skills are highlighted for review. Automatic updates are unavailable because the Skills CLI update command can change installations for other detected agents. Filter by agent to see which skills are available for each AI agent.
View plugins already installed in Claude Code and Codex using each host's CLI. The full-width list shows each installation separately, including Claude Code project installations. Open a plugin to inspect its status, version, scope, and location. User-scope Claude Code plugins can be enabled, disabled, or removed; removal keeps their persistent data. Codex plugins can be removed. Project and local Claude Code plugins are shown for inspection, since changing them requires their owning project directory. Removal asks for confirmation.
The host CLI must be installed for its plugins to appear. The command reports a host-specific error if one CLI is unavailable.
Enter the path to a local skill or plugin folder. The inspector checks Agent Skills frontmatter and portable Agent Plugins v1 structure, shows bundled resources and MCP servers, and reports invalid paths or metadata. It recognizes Claude Code and Codex compatibility layouts separately. Inspection does not install packages or run their code.
This extension runs the Skills CLI via bunx/npx, which download the skills package from a package registry. If your machine installs packages through a corporate proxy instead of the public npm registry, note that Raycast is launched by the OS and does not inherit environment variables from your shell profile (~/.zshrc, ~/.bash_profile, etc.). Registry overrides set only as shell environment variables (for example NPM_CONFIG_REGISTRY or BUN_CONFIG_REGISTRY) will not reach the CLI.
Configure your registry in files in your home directory, which every launch context reads:
npm / npx — ~/.npmrc:
registry=https://your-proxy.example.com/
bun / bunx (tried first by this extension) — ~/.bunfig.toml:
[install]
registry = "https://your-proxy.example.com/"
After editing these files, fully quit and relaunch Raycast so it re-reads the configuration. If automatic npx detection also fails, set Custom npx Path in the extension preferences.
Search for agent skills
Review installed skills and manage verified Skills CLI installs
View installed Claude Code and Codex plugins
Validate a local Agent Skill or Plugin package
~-relative source in Manage Skills, instead of the absolute path offered as a repository link and URLgrok ID instead of failingSKILL.md frontmatter that starts with a byte order mark or has no content after it--json in the troubleshooting commands so they match the installed-skills list command used by the extensionskills CLI actually printed when "Manage Skills" cannot parse its installed-skills list, instead of only reporting that the output was unexpectedskills CLI, so an ordinary first run on a slow connection no longer failsadd, remove, and update up to 5 minutes instead of 30 seconds, so "Update All Skills" no longer fails with a bare "Command failed: npx -y skills@latest update -g -y" once checking every installed skill's source takes longer than thatskills CLI timed out, including whatever it printed before being stopped, instead of only the command that failedbunx run through npx, which only doubled the waitnpx cache and intermittently failing with ENOTEMPTYbun/node installed outside a version manager or Homebrew, so "Unable to find a working bunx or npx command" no longer appears for Bun's official installer (~/.bun/bin), Nix / nix-darwin profiles, mise, and asdfskills CLI printed when it exits non-zero, instead of only "Command failed: bunx --silent skills@latest …" with no reason — the CLI writes its errors to stdout, which was being discardednpx when bunx dies without printing anything at all, limited to read-only commands so a mutating add/remove/update is never run twiceSKILL.md sits at the repository root (single-skill repos), which previously failed to load in the detail viewread-skill AI tool use the same repo-layout resolution as the detail view, so nested and root-level skills are readablebunx/npx at a custom package registry (corporate proxy) via ~/.npmrc and ~/.bunfig.toml, since Raycast does not inherit shell environment variablesskills/productivity/grill-me/SKILL.md) by locating the real SKILL.md anywhere in the repository tree⌘ ⇧ I so the canonical copy shortcut (⌘ ⇧ C) copies the skill contentsskills.sh detail link for published installed skills@skills support in Raycast AI Chat with five tools: search the marketplace by query, read a skill's full instructions, list installed skills, install a skill for specific agents, and remove a skillowner/repo) as the subtitle in "Search Skills" and "Manage Skills" to better distinguish skills between themskillId installed from different sources. Show a warning indicator and rename the "Install Skill" action to "Replace Installed Skill" for clarity on the outcome'"bunx"' is not recognized as an internal or external command on Windows when Bun is not installed; the extension now correctly falls back to npx as intendedbunx, it is only called optimally if npx is not foundDISABLE_TELEMETRY=1 to all Skills CLI invocations when the preference is enabled/opt/homebrew/opt/node@24/bin so the Skills CLI can find node when npx comes from Homebrew, while still preferring Node installs from version managers firstskills update <name> (requires skills CLI 1.5.0+), so a single outdated skill can be updated without touching the othersCommandStates components back into command filesuseSkillContent and expand skills-cli coverage around CLI error normalization and agent id mappingsearch and manage empty/error states with shared retry handling and clearer recovery copyREADME.md and add a manual smoke checklist in TESTING.mdvitest-based unit tests and an opt-in live API test for the skills extension?q=skill) that only returned skills with "skill" in the name, missing the majority of popular skillsfnm install locations, including ~/Library/Application Support/fnmfnm directory resolution preference order when resolving fnm paths.npx path preference for non-standard setupsnpx and Skills CLI failures, including a shortcut to open Extension Preferenceskills list --json for structured output instead of parsing ANSI textallowed-tools: Bash)