> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/integration-toolkits/litk.md).

# Lab Instrument Toolkit

Lab Instrument Toolkit provides a number of scripts that can be used for custom configuration.

* The *driver\_file\_generator* script ([*Template File Generator*](/clarity-lims/integration-toolkits/litk/litk-template-file-generator.md)) is a file-generation solution that produces custom template files without requiring scripting or development knowledge or resources.
* The *addBlankLines* script allows for the creation of files that require a line entry for every well in a container, including those wells that are empty.
* The *convertToExcel* script converts separated-value files (eg. CSV) to Microsoft Excel XLS or XLSX spreadsheet format.
* The *parseCSV* script allows for the data for each well to be parsed into fields on either derived samples or measurement records that map directly to the derived samples being measured.
* The *parseXmlBySampleName* script matches data in a result file to samples in the LIMS, using the measurement record LIMSID.
* The *PlacementHelper* script automates sample placement according to a transfer file produced by a robot. The script covers a one-to-one, many-to-one (pooling), or one-to-many (replicates) mapping of samples for placement.


---

# 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.bioinsight.illumina.com/clarity-lims/integration-toolkits/litk.md?ask=<question>&goal=<user_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.
