> For the complete documentation index, see [llms.txt](https://docs.uselessrobuk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uselessrobuk.com/welcome-to-uruk-and-co.md). # Welcome to URUK & CO If you have found yourself here then you have been intertested or are currently using our development and IT Support services.\ \ **About URUK & CO:** URUK & CO (UselessRobUK & CO) is owned and managed by Rob (UselessRobUK) and Wullie (Silent Streamer), Rob started his IT journey back in 2012 as a freelance developer however during the lockdown in 2020 he seen a high demand for services and support. Whilst doing content creating he started #LOL in September 2021 which would then expand with #LOL STUDIOS in early 2024. With Rob, Wullie (Content & Community Manager) & Jack (Lead Developer) at the helm of URUK & CO they continue to expand and utilise vast amounts of software to provide high profile services to our clientclients ranging from custom developed systems, websites, graphics and applications. More about the brand and projects can be found at [https://uselessrobuk.com](https://uselessrobuk.com/) --- # 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://docs.uselessrobuk.com/welcome-to-uruk-and-co.md?ask=&goal= ``` `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.