> For the complete documentation index, see [llms.txt](https://docs.tabiya.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tabiya.org/readme.md). # Welcome Welcome to Tabiya docs! This collection of documents provides an overview of our overall approach and our work.

Tabiya creates open-source software, models and standards to help tackle the global youth employment challenge. We foster research, coordination, and harmonization among partners that create learning and career pathways. Our vision is to unlock human capital and empower people in informal and formal labor markets. We are a non-profit organization that started at the [University of Oxford](https://www.oxfordmartin.ox.ac.uk/future-of-development/). ### Discover Tabiya's Work


Inclusive Livelihoods Taxonomy	Make visible and usable the human capital of everyone in an economy	Inclusive Livelihoods Taxonomy
Compass by Tabiya	Assist job-seekers in exploring and discovering their skills	Compass
Livelihoods Classifier	Use natural language processing to automatically process unstructured text from jobseeker profiles and vacancies	Livelihoods Classifier

If you have any questions or comments, please do not hesitate to reach out via [email](mailto:hi@tabiya.tech). You can also create an [issue](https://github.com/tabiya-tech/docs/issues) in the [Github repository](https://github.com/tabiya-tech/docs/) that hosts this documentation. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tabiya.org/readme.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 `build a script that syncs our docs to a CMS` 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.