#### Features

# Skills, Plugins & Marketplaces

## Skills

Skills are reusable folders containing markdown instructions, script files, and resources for agents.

Grok discovers skills from:

* `./.grok/skills/`
* `<repo_root>/.grok/skills/`
* `~/.grok/skills/`
* `~/.claude/skills/`

User-invocable skills also appear as slash commands, for example `/<skill-name>`.

## Plugins

Plugins extend Grok with additional tools, skills, and MCP servers.

Plugin locations:

* `.grok/plugins/`
* `~/.grok/plugins/`
* `--plugin-dir <PATH>`

Manage plugins inside the TUI with `/plugins`.

Browse, search, and toggle plugins in the TUI.

Similarly, manage MCPs with the slash command `/mcps`.

Manage MCP servers with a built-in modal.

## Hooks

Hooks run scripts on tool and session lifecycle events, such as before or after tool calls.

Project hooks live in `.grok/hooks/`. Plugins can also provide hooks.

## Marketplaces

The TUI plugin UI includes a Marketplace tab for browsing and installing plugins from configured sources.

Marketplace sources can come from:

* `[[marketplace.sources]]` in `~/.grok/config.toml`
* Compatible Claude Code files marketplaces in `~/.claude/plugins/known_marketplaces.json`

## Subagents

Subagents spawn independent child sessions that handle tasks in parallel.

## Claude Code compatibility

Grok is fully compatible with Claude Code with zero configuration needed.

Grok automatically reads Claude Code marketplaces, plugins, skills, MCPs, agents, and instruction files (`AGENTS.md`, `CLAUDE.md`) alongside `.grok/`. No extra setup is needed.