> For the complete documentation index, see [llms.txt](https://docs.algomojo.com/algomojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algomojo.com/algomojo/my-signals.md). # My Signals "My Signals" is a comprehensive section that encompasses various tabs to track and manage your trading activities. When you buy or sell assets, they are organized into the following tabs: * **Signals:** This tab displays the trading signals generated by your strategy, providing insights into market conditions and recommended actions. * **Orders:** In this tab, you can view and manage your open orders, including buy and sell orders for different assets. * **Positions:** The "Positions" tab shows your current positions, including the assets you own and the quantity held for each asset. * **Holdings:** This tab details your asset holdings, including information about the assets in your portfolio and their current status. * **Summary:** The "Summary" tab provides an overview of your trading activities, summarizing your performance, gains, losses, and other key metrics. * **Realized P\&L:** This tab displays your realized profit and loss (P\&L) from closed positions, helping you assess your trading success. --- # 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.algomojo.com/algomojo/my-signals.md?ask=&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.