> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eigi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plugins

> Add-on packs that teach your Eigi new skills and workflows

## Overview

Plugins are add-on packs that extend what your Eigi *knows how to do*. Where a connector gives Eigi access to an app, a plugin gives it know-how: bundled skills, commands, and pre-configured tools built for a purpose — a project-management workflow, a content pipeline, a company-specific toolkit.

Install one, and your Eigi immediately knows the workflow — no teaching required.

***

## What's Inside a Plugin

<CardGroup cols={2}>
  <Card title="Skills" icon="graduation-cap">
    Step-by-step playbooks Eigi follows for specific tasks — the plugin's
    know-how.
  </Card>

  <Card title="Commands" icon="terminal">
    Slash commands you can trigger from chat to kick off the plugin's
    workflows directly.
  </Card>

  <Card title="Connectors" icon="plug">
    Some plugins bring their own integrations, ready to authorize on install.
  </Card>

  <Card title="Sub-agents" icon="users-gear">
    Specialist helpers the plugin defines for its workflows.
  </Card>
</CardGroup>

***

## Installing Plugins

<Steps>
  <Step title="Browse the catalog">
    The **Plugins** section lists available plugins. Search or browse by what
    you're trying to do.
  </Step>

  <Step title="Preview before installing">
    Every plugin shows exactly what it contains — each skill, command, and
    connector — before you install. No surprises.
  </Step>

  <Step title="Install and use">
    One click installs it. The new abilities show up in chat immediately —
    ask Eigi, or type `/` to see the plugin's commands.
  </Step>
</Steps>

***

## Private Plugins via GitHub

Teams and companies can keep plugins in their own private GitHub repositories.

<AccordionGroup>
  <Accordion title="Connect GitHub" icon="github">
    Link your GitHub account from the Plugins page. You approve access through
    GitHub's own authorization screen.
  </Accordion>

  <Accordion title="Install from your repos" icon="lock">
    Once connected, your private plugin repositories appear alongside the
    public catalog — install them the same way.
  </Accordion>

  <Accordion title="Stay updated" icon="arrows-rotate">
    When the repository changes, you can pull the update from the same place.
    You'll see what changed before it applies.
  </Accordion>
</AccordionGroup>

***

## Staying in Control

* **Review first** — a plugin's full contents are visible before you enable it.
* **Enable/disable anytime** — turn a plugin off without uninstalling; its abilities disappear from Eigi immediately.
* **Approvals still apply** — plugin workflows follow the same [permission rules](/eigi-computer/settings) as everything else Eigi does.
* **Remove cleanly** — uninstalling removes the plugin's skills, commands, and tools in one go.

<Note>
  Connectors give Eigi **access**; plugins give Eigi **know-how**. A great
  setup usually combines both — for example, a "content publishing" plugin
  paired with your Notion and X connectors.
</Note>