# Create a Chrome Extension

<figure><img src="/files/rA7KEcv4kDmXCT2czGYB" alt=""><figcaption><p>Link Reveal Chrome Extension</p></figcaption></figure>

We'll follow the design and creation of an extension named **Link Reveal**.  It will be activated by clicking an icon to the right of the Chrome address bar.  The red hook is the icon associated with this extension.

<div data-full-width="false"><figure><img src="/files/qEMEHNEOe7DnJ1eqxNpQ" alt=""><figcaption><p>Chrome Address Bar with Extension Icons on the Right</p></figcaption></figure></div>

When the user clicks on the icon, this triggers an action that results in a popup window displayed with the **Link Reveal** report of all the links in the current web page.

Creating a Chrome extension starts with understanding the requirements that files containing code and configuration must meet.  Knowing how Chrome communicates between the user web page and the extension web page is essential. &#x20;


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rpeltz.gitbook.io/create-and-publish-a-chrome-browser-extension/create-a-chrome-extension.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
