> For the complete documentation index, see [llms.txt](https://chaoses-ib.gitbook.io/directory-opus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_add-ins/script_package.md).

# Script Package

To make it easier to distribute your scripts to others, you can bundle one or more script add-ins in an archive called a *Script Package* (a zip file with the **.osp** suffix).

You can also include a set of icons that can provide the default icon images for any internal commands your scripts add.

To make a script package:

* Create a Zip archive (leave its suffix as **.zip** for the moment).
* Copy your script files (**.js**, **.vbs**, etc) into the archive.
* When finished, rename the archive to give it a **.osp** suffix.

If you like you can add **.osp** to the list of recognized Zip file extensions on the [**Zip & Other Archives / Zip Files**](/directory-opus/manual/preferences/preferences_categories/zip_and_other_archives.md) page in Preferences, to make script packages easier to deal with in Opus.

If you want to add icons that your scripts can refer to:

* Create an icon set, following the specifications in the [Icon Sets](/directory-opus/manual/reference/icon_sets.md) reference section. *Do not zip this to a **.dis** file.*
* Create a sub-folder in the script package archive called **icons**.
* Copy all the files of your icon set into the **icons** sub-folder.

In your scripts, you can use the icons in your icon set as the default toolbar button images for any [internal commands](/directory-opus/manual/scripting/example_scripts/adding_a_new_internal_command.md) you add, using the [**ScriptCommand**](/directory-opus/manual/reference/scripting_reference/scripting_objects/scriptcommand.md)**.icon** property.

Script packages can also include external [script resource](/directory-opus/manual/scripting/resources.md) files. These must be XML files with the file extension **.odxml**. You can use the [**Script**](/directory-opus/manual/reference/scripting_reference/scripting_objects/script.md)**.LoadResources** method in your script to load the script resource file from the package.


---

# 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://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_add-ins/script_package.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.