> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/automation-and-powershell/scripting-for-osd/scripting-examples-simple-inline-script..md).
# Scripting Examples - Simple inline script.
PowerShell scripts in DeployR task sequences can be simple or complex. A basic PowerShell step might look like this:
```
Get-ChildItem tsenv:
```
You can paste this script directly into a step. It returns a list of all task sequence variables, which are then written to the DeployR log. This is useful for debugging and checking variable values at a specific point in the task sequence.
This is a simple example. Another option is to have a step install a module and run a command. The following example updates the HP BIOS from WinPE:
```
install-module -name HPCMSL -AcceptLicense -SkipPublisherCheck -Force
if ((Get-HPBIOSUpdates -Check) -eq $false){Get-HPBIOSUpdates -Flash -Yes -Bitlocker Ignore}
```
This step also supports longer scripts, which you can more easily view by clicking the enlarge icon on the upper right corner of the script dialog box.
The script editor then opens in full-screen mode. Click the blue **Minimize** button in the upper-right corner to return to the normal view.
---
# 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://documentation.2pintsoftware.com/deployr/automation-and-powershell/scripting-for-osd/scripting-examples-simple-inline-script..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.
