> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/mcp/skills/installation.md).

# Installation

Skills are installed in AI applications that support custom instructions or skill files.

### Claude Code

Run these two commands in your terminal:

```bash
/plugin marketplace add blotoutio/skills
/plugin install blotout@blotoutio
```

This installs all three skills (EdgeTag, ConsentIQ, Edge Lake) at once. Claude Code will automatically use the relevant skill based on your questions.

### Claude Cowork

1. Click the **+** icon in the chat input
2. Select **Plugins** > **Add Plugin**
3. Click the **Personal** tab
4. Click **+** and select **Add marketplace from GitHub**
5. Enter `blotoutio/skills` and click **Sync**

After syncing, the EdgeTag skills will be available in your conversations.

### Other AI applications

We support multiple AI applications including Cursor, Codex, and OpenCode. Installation steps vary by app. Check our GitHub repository for the latest instructions for your specific app:

[github.com/blotoutio/skills](https://github.com/blotoutio/skills)

### Skills + MCP

Skills and MCP work together. MCP provides the tools to access live data, while skills provide the knowledge to use those tools effectively. For the best experience, install both:

1. Add the EdgeTag MCP server ([installation guide](https://docs.edgetag.io/mcp/installation/overview.md))
2. Add the EdgeTag skills (above)

With both installed, your AI assistant can not only query your data but also help you implement, debug, and optimize your EdgeTag setup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.edgetag.io/mcp/skills/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
