> For the complete documentation index, see [llms.txt](https://docs.reveald.com/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveald.com/technical-documentation/admin-guides/epiphany-validation-engine-users-guide/chapter-3-eve-platform/navigation-tabs/emulation-control/custom-threats/editing-an-existing-script.md).
# Editing an Existing Script
To Edit an existing script, follow these steps:
1. In the Custom Threat tab, find the script to edit.
2. Click on the Edit icon  in the Actions column.
3. The Edit script Editor will appear.
4. Edit the part of the script the user need. The sections that can be edited are:
* Alias
* Code
* Description
* Execution Parameters.
Name, language, and Platform are not editable.
5. Click "Save Script” to keep the changes.
---
# 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.reveald.com/technical-documentation/admin-guides/epiphany-validation-engine-users-guide/chapter-3-eve-platform/navigation-tabs/emulation-control/custom-threats/editing-an-existing-script.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.