> For the complete documentation index, see [llms.txt](https://hookrank.gitbook.io/hookrank/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hookrank.gitbook.io/hookrank/core-features/dashboard/hook-list.md).

# Hook List

This design ensures that users can easily access all pertinent details about each hook without unnecessary navigation. Including clickable elements, such as linking the hook name to the [Hook Details](/hookrank/core-features/dashboard/hook-details.md) page and the deployer address to the chainscan page, allows users to quickly access necessary information from one card. The inclusion of labels for source code verification and [NoOp](/hookrank/hooks-knowledge/noop-hooks.md) type status adds transparency and aids in quick assessments of the hook's attributes. Metrics like transaction volume, TVL, success rate, and total earnings provide a comprehensive overview of the hook's performance and impact, empowering users to make informed decisions or investments. Lastly, the explore button serves as a direct gateway to the contract's page on Chain Scan, offering a complete view of all related transactions and activities.

<figure><img src="/files/lkzD3h4b8OqQXBI6b18I" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://hookrank.gitbook.io/hookrank/core-features/dashboard/hook-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.