> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/quality-library/faq/what-is-the-difference-between-the-quality-library-and-the-truffle-hunt.md). # What is the difference between the Quality Library and the Truffle Hunt? The Quality Library and Truffle Hunt share one common goal: searching for clauses to insert into your document. The way they go about achieving that goal, however, is vastly different: The **Truffle Hunt** allows you to search for useful clauses in the way that most legal teams are accustomed to: diving through dozens, if not hundreds of precedent documents by way of a keyword search. Truffle Hunt helps you to find this needle in the haystack by centralizing the precedent documents to search through, automatically extracting clauses from it, and giving you a range of different tools (besides simple keyword searching) to find the needle. The **Quality Library** is similar to Truffle Hunt in that it is ultimately a repository for clauses. It differs from Truffle Hunt in that its focus is not on quantity but on quality. To continue the analogy: whereas you build a haystack in Truffle Hunt and hope you will find the needles later on, Quality Library is all about collecting the individual needles in one place. To that end, Quality Library is much more suited to organisations who wish to standardize their legal drafting, e.g.: by collecting company standard clauses and fallback positions. It would be virtually impossible to achieve this goal in Truffle Hunt, where these clauses are accompanied by hundreds or thousands of other clauses with no way to tell their significance. --- # 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://help.clausebuddy.com/quality-library/faq/what-is-the-difference-between-the-quality-library-and-the-truffle-hunt.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.