Install the Shoogle Skill in your AI assistant

Skills are packaged instructions your assistant loads on demand. The Shoogle Skill teaches it when to call Shoogle MCP tools and how to install matches with npx shadcn@latest add. Pair it with an MCP install so the tools are available.

Install command

Run this in your terminal to add the Shoogle Skill to your assistant.

Steps

Works with Cursor, Claude Code, and other assistants that support skills.

  1. Open a terminal in your project directory (or home directory for global install)
  2. Run the install command below
  3. Restart your AI assistant so it picks up the new skill
  4. Ask your assistant to search for a component (e.g. "find a hero section from shadcn registries")
  5. Configure the Shoogle MCP server if you have not already

Tools

The skill teaches your assistant to use these Shoogle MCP tools to search indexed shadcn registry items by keyword and install them with npx shadcn@latest add.

Search across all registries

search_registry_items

Search shadcn registry items by name across all indexed community registries. Returns registry namespaces and ready-to-use npx shadcn@latest add commands.

Parameters: query (required), offset, limit

Search within one/multiple registries

search_registry_items_scoped

Same name search, limited to specific registry namespaces (e.g. @shadcnblocks, @cult-ui). Use when you know which registries to check. Reports unknownRegistries for namespaces that did not resolve.

Parameters: query, registries (required), offset, limit

Prerequisite: The Shoogle Skill uses the Shoogle MCP server under the hood. If your AI agent cannot search registries, install and configure the MCP server first.

Troubleshooting

  • Confirm the skill installed successfully — check your assistant's skills list or .cursor/skills directory
  • The Shoogle Skill requires the Shoogle MCP server — follow the MCP install guide if search fails
  • Restart your assistant after installing the skill or MCP server
  • Try more specific keywords (e.g. "button" not "ui")
  • For semantic or layout-based block discovery, use shoogle.dev/search instead