Skip to content

Skills, MCP and plugins

The extensions panel gathers four tabs: Skills, MCP, Plugins and LSP. They all serve the same idea: giving the agent new capabilities without you writing any code.

A Skill is a package of reusable instructions (“how to review a PR”, “how to write my reports”) that the agent activates when the task calls for it. In the Skills tab:

  • Installed: your Skills, both the ones that ship with the app and your own.
  • Market (skills.sh): search the public Skills catalog and install with one click.

The Create skill button opens a form that saves it already in the right format:

  1. Name (e.g. “PR reviewer”).
  2. Scope: Global (available in all your projects) or Project (only in the current workspace).
  3. Description — important: it defines when the Skill activates (“use it when the user asks to review a pull request…”).
  4. Instructions in Markdown: the step-by-step the AI should follow.
Creating a Skill: name, scope, when it activates and its instructions.

MCP (Model Context Protocol) is the standard for giving the agent external tools: databases, APIs, services. In the MCP tab:

  • Installed: your configured MCP servers, with hot reload (“Recargar servidores MCP” — Reload MCP servers).
  • Marketplace: a built-in catalog for discovering MCP servers with no API key needed — it combines a curated selection with the official public registry.
  • Add MCP by hand: paste the server command (e.g. -y @scope/server) and choose the scope to save it in.
The MCP marketplace: search, install and reload servers without touching config files.

The Plugins tab lists larger packages that combine several capabilities (for example, web scraping plugins with Puppeteer/Playwright, database administration, CI/CD automation…). You enable and disable them right from the list.

The LSP tab manages the language servers that power autocomplete and diagnostics in the editor: see which ones you have, install them and update them.

The Skills active in the chat are listed with their toggle: they step in on their own when needed.
The installed MCP servers and the tools each one contributes.
A plugin is a GitHub repo: it brings Skills and MCP servers together, and the engine loads them on its own.