TUTORIAL · SCRIPT TOOLS LIBRARY V1.1

From unzip to your first script run.

Everything you need to get productive with Script Tools Library: installing, starting the trial or activating a license, touring the main window, understanding the RISK headers, and building your own script collection. Ten minutes, start to finish.

1Install & first launch

There is no installer, and that is on purpose. Script Tools Library ships as a single zip:

Unzip the download anywhere you like — Desktop, D:\Tools, a USB stick. The folder is the whole application: settings, scripts and notes all live inside it.
Run LaunchScriptsLibrary.exe from that folder. Nothing is written to the registry and no background service is installed.
To uninstall later, close the app and delete the folder. That's it.

On first launch you'll see the Get started welcome dialog. It offers two paths: enter your email address to start the 15-day free trial, or click "I already bought it" if you purchased a copy on itch.io. Both are covered in the next section.

2Start your free trial / activate a purchased copy

Starting the trial Trial — 15 days

In the welcome dialog, enter your email address and confirm. The full application unlocks for 15 days — every feature, all 25 included tools, nothing held back. The status badge in the main window keeps you posted, e.g. "Trial — 15 days left".

Activating a purchased copy

Click "I already bought it" in the welcome dialog. You can activate with your itch.io download link/key or with your serial. Once activated, the trial badge disappears and the copy stays licensed on this machine.

The activation dialog with fields for an itch.io key or serial, plus Deactivate this machine and Check for updates buttons — The activation dialog. It also hosts "Deactivate this machine" and "Check for updates" — see section 7.

Not purchased yet? The product page is at toprogos.com/stl.html, and the store page is toprogos.itch.io/script-tools-library.

3Tour of the main window

The Script Tools Library main window: categories on the left, scripts list in the middle, script details on the right — The main window: three panels, left to right — Categories, Scripts, Script Details.

Everything happens in one window, split into three panels:

Categories (left). Your script collection, grouped. Select a category to filter the scripts list. The New, Refresh and Delete buttons manage categories here.
Scripts (middle). Every script in the selected category, with a search box at the top to filter by name as you type.
Script Details (right). The selected script in full: a code preview (with its # RISK: header — see section 4), the Source field, a free-form Notes field, a Type dropdown, and a Shortcut field for a per-script keyboard shortcut.

The categories panel with the New, Refresh and Delete buttons — The Categories panel. New creates a category, Refresh re-scans it, Delete removes it.

Below the details pane sit the action buttons: Run green, Run Admin orange, Save (stores your edits to notes, type, shortcut) and Tweak (open the script for editing). The status badge in the window shows your license state, such as "Trial — 15 days left".

4Read before you run — the code preview and RISK headers

Script Tools Library's safety philosophy is simple: you should never run code you haven't looked at. The application is built to make looking easy, not to make trust automatic.

Every script — the 25 included ones and any you add — is plain-text PowerShell you can read in the preview pane before running.
Every included script starts with a # RISK: header: a one-glance statement of what the script touches and what could go wrong. A read-only report and a script that closes processes carry very different RISK lines, and the header tells you which one you're holding.

The code preview pane showing a script whose first line is a # RISK: header — The preview pane. The first line of every script is its RISK header — read it before anything else.

Being honest with you: no tool can make running scripts risk-free, and this one doesn't claim to. What it does is put the code and its RISK statement in front of your eyes before every run. If a RISK header or the code itself makes you unsure, don't run it — that hesitation is the feature working.

5Run a script / Run as Administrator

Select a script, read its preview, then choose:

Run green — launches the script in a normal PowerShell console with your regular user rights. Most of the included tools (reports, finders, converters) run this way.
Run Admin orange — launches the script elevated, for tasks that genuinely need administrator rights (reading the system event log, closing another process's file handle, and so on).

A script running in a PowerShell console window after clicking Run — A normal Run: the script executes in its own PowerShell console so you can see everything it prints.

Run Admin never elevates silently. It always shows an "Elevated execution" consent dialog first, naming the script you're about to elevate, and only proceeds after you confirm — followed by Windows' own UAC prompt. Two deliberate clicks stand between you and an elevated script, both times with the script's name in front of you.

The Elevated execution consent dialog shown before any Run Admin launch — The "Elevated execution" consent dialog. Every Run Admin starts here — no exceptions, no "don't ask again".

6Add your own scripts, categories, notes and shortcuts

The 25 included tools are the starter set; the point of the app is your collection.

Add a script. Click Add and point it at your .ps1 file. It appears in the scripts list and gets the same treatment as the built-ins: preview, notes, type, shortcut. Consider giving your own scripts a # RISK: first line too — future-you will thank present-you.
Organize with categories. Use New in the Categories panel to create groups that match how you think ("Network", "Cleanup", "Work"). Refresh re-scans a category; Delete removes one.
Notes. The Notes field is free text saved per script — what it expects, which server it targets, why you wrote it at 2 a.m. Click Save after editing.
Source and Type. Record where a script came from in Source, and classify it with the Type dropdown so similar tools sort together.
Keyboard shortcuts. Give a frequently-used script its own shortcut in the Shortcut field and launch it without touching the mouse.
Hide what you don't use. Scripts you rarely need can be hidden from the list without deleting them.
Tweak. The Tweak button opens a script for editing — the included tools are plain PowerShell, so adapting one to your needs is encouraged.

7Managing your license

Seats. One license activates up to 3 machines.
Moving to a new PC. On the old machine, open the activation dialog and click "Deactivate this machine" — this frees the seat. Then copy or re-download the app on the new machine and activate there with your key or serial. Because the whole app is one folder, copying the folder also brings your scripts, categories and notes along.
Old machine died first? If you couldn't deactivate before a machine was wiped or lost, write to support@toprogos.com and the seat can be sorted out.
Updates. The activation dialog has a "Check for updates" button. Updating is manual and deliberate: download the new zip, unzip, done — see the FAQ for keeping your data.

8FAQ

My trial expired — what now?: The trial runs 15 days with every feature enabled. When it ends, buying a license on the itch.io page and activating with your key or serial picks up exactly where you left off — your scripts, categories and notes are untouched.
Can I move my license to another machine?: Yes. Each license covers up to 3 machines. Click "Deactivate this machine" in the activation dialog on the machine you're leaving, then activate on the new one. See section 7.
My antivirus flags the launcher / Windows shows "unknown publisher". Is that normal?: Honest answer: yes, and here's why. LaunchScriptsLibrary.exe is not code-signed — signing certificates cost more per year than this tool does, so as a one-person shop we ship unsigned. Windows SmartScreen and some antivirus products are rightly cautious about unsigned executables from small publishers, so a warning on first run is expected behavior, not a malfunction. We won't tell you to whitelist anything — that's your call to make, not ours to ask for. What we can offer is transparency: the product page publishes the SHA-256 hash of the exact release zip so you can verify your download matches the audited build, and every script the app runs is plain text you can read first.
Where are my scripts and notes stored?: Inside the application folder, as ordinary files. Nothing goes to the registry, nothing goes to the cloud, and there is no telemetry. Back up the folder and you've backed up everything; copy it to a USB stick and your whole setup travels with you.
How do I update to a new version?: Use "Check for updates" in the activation dialog, or watch the itch.io page. Download the new zip and unzip it. Since your scripts and data live in the application folder, the safe routine is: back up your current folder first, then follow the release notes for carrying your data over.
How do I completely remove it?: If licensed, click "Deactivate this machine" first to free the seat. Then close the app and delete the folder. That is the entire uninstall — no leftovers, no registry entries.

↑ Back to top · Questions this page didn't answer? support@toprogos.com