Light-Help: PowerShell scripts you run straight from a raw GitHub URL

Every tool is one line that downloads a script and runs it

Light-Help is a repository of Windows PowerShell scripts, published in the primary language of PowerShell, whose stated purpose is helping the audience perform some complex operations.

The delivery mechanism is uniform across the whole repository, and it is the first thing to understand. Each tool is invoked by piping a raw GitHub URL into the interpreter:

iwr -useb https://raw.githubusercontent.com/Cotton059/Light-Help/main/light/LightShift/LightShift_Tool.ps1 | iex

That is iwr with the use basic flag, which fetches a URL, piped into iex, which executes the result as PowerShell. Nothing is downloaded to disk, inspected, or signed on the way in. The readme states that all the scripts provided are general purpose, and that you should open a terminal and paste the code to run it, with four ways given to reach a terminal: the Windows plus X menu, the taskbar search, the administrator shortcut the project creates for you, or a desktop icon built from the one line code.

Because the source lives in the repository, the security posture is better than the one line suggests. The code is public, the readme says the core code is fully open and transparent and welcomes inspection before running, and the repository carries a linter workflow badge and a separate powershell-audit workflow badge. The scripts live under light/, and the top level also holds a ThirdParty directory, a Tutorial-References directory and an images folder.

The tradeoff remains real, though. The one line fetches whatever is at that path on the main branch at the moment you run it, so the code that executes is not the code you read yesterday.

The toolset covers disk space, multi instance apps and local servers

The video tutorial navigation at the top of the readme lists what the repository actually contains, and the range is wider than the name suggests.

On storage, there are two separate tools. The user folder transfer tool moves the Windows user folder to another partition to free tens of gigabytes on the C drive, and the documentation describes it as lossless and safe. The DeepCleanPRO tool is a deeper clean that installs an open source cleaning application and clears cache-type junk files from any disk.

On application launching, the MultiInstance tool creates a desktop shortcut generator that gives any software or game its own independent environment so several copies can run at once. Its documentation notes a fallback variant with broader environment compatibility that has to be copied and run manually each time.

The Shortcut Generator is the meta tool. It takes any single line GitHub command, such as the ones above, and turns it into a desktop shortcut that runs with administrator rights, so the one line operation becomes a click. That is what makes the rest of the repository usable for people who do not want to paste code into a terminal.

For gaming, there is a three step PalServer installer that downloads and configures a game server on a local Windows machine, a second command that fills in missing runtime libraries and DLLs when the server crashes on launch, and a third that sets up virtual LAN networking so a friend on another network can connect to your machine by IP without a public address or a rented server.

The remaining entries in the navigation cover building a home media server without a NAS, wireless transfer of photos and videos from an iPhone, a one line GitHub translation setup, and a script that blocks the silent iOS update on an iPhone.

Two scripts create the shortcuts the rest of the tools depend on

Two of the entries are infrastructure rather than tools, and it is worth separating them from the payload scripts.

The first creates a desktop shortcut pointing at the repository itself. The command detects the desktop path, including OneDrive redirected desktops, and writes a .url file:

$s=(New-Object -COM WScript.Shell).CreateShortcut("$([Environment]::GetFolderPath('Desktop'))\Light-Help.url"); $s.TargetPath="https://github.com/Cotton059/Light-Help"; $s.Save()

The New-Object call with the WScript.Shell COM class is what makes this work on a stock Windows install without extra modules.

The second creates an elevated PowerShell shortcut, and its own description says the script detects the desktop path and injects the underlying elevation flag so the generated icon runs with administrator rights by default:

iwr -useb https://raw.githubusercontent.com/Cotton059/Light-Help/main/light/Create_AdminPSShortcut_Tool.ps1 | iex

That second one is the most consequential of the set, and it is worth being clear about why. It creates a shortcut on your desktop whose default behaviour is to run PowerShell as administrator. After that, any script the project publishes can be launched from a click, with elevation, without the user touching a command line.

The MultiInstance and DeepCleanPRO entries follow the same pattern of a desktop shortcut generator with a fallback to a manually pasted command when system security restrictions block shortcut creation, which tells you the project has run into execution policy problems on locked down machines and has worked around them in two ways.

None of the scripts are signed, and the documentation about elevating your shell is not a security recommendation from the project so much as a practical instruction for making the tools work.

The newest scripts are gated behind an invitation code

The readme opens with a usage notice that any adopter needs to understand, because it changes what you can actually run.

The notice states that the most recently published video scripts will require an invitation code to run when the traffic or publication time conditions are not yet met. The invitation is described as obtainable by leaving a comment after any interaction with the channel, such as subscribing, liking or sharing. It also states that the restriction lifts if you fork the repository and modify the code yourself, if you help the channel's video reach its numbers, or automatically after seven to fourteen days from publication.

This is an unusual arrangement for an open source repository, and the GPL-3.0 licence on the code does not change it. The licence covers the code. The gate is on the hosted script path and on the distribution of the tools to viewers.

The practical consequence for a reader is that the scripts you see in the readme may not be the scripts you get. If the newest entry in the navigation is gated and you have not obtained a code, the one line command may fail or may not exist at the path, and the fallback is to fork and read the code yourself, which is the option the notice points at first.

For a repository whose entire value proposition is one line commands you can paste, having those commands conditionally unavailable is a significant limitation, and it is the main thing to check before recommending the project to someone.

A YouTube channel with a repository attached to it

The project is unusual in that the repository is described throughout as the companion resource for a video channel rather than as a standalone project.

The usage notice says every script in the project is the exclusive companion resource for the channel's video tutorials, and points to the channel as the official source. It also says the channel's community space is where users vote on and customise service requests, so the roadmap is a community vote rather than a maintainer backlog.

That framing explains several otherwise odd choices. The navigation section is a list of video links with anchors pointing at the readme headings for each tutorial, each with a thumbnail, because the readme is effectively a landing page for the videos. The Tutorial-References directory at the root exists to hold the reference files the videos rely on. The bilingual readme, with separate Chinese and English versions, exists because the audience is international while the channel is not.

The repository metadata says the project is not archived and the last push was on 2026-10-19, four days before the current date, with no GitHub releases at all. There is a LICENSE file at the root under GPL-3.0, and the workflow badges cover a linter and a PowerShell audit rather than a build, which fits a collection of scripts that are read and executed rather than compiled.

So the honest way to assess it is as a curated script bundle with a video library attached, rather than as a software project with a release cadence.

Editorial conclusion

Light-Help suits a Windows user who wants to see exactly what a script does before running it, since the repository publishes the source of each helper alongside the one line command that fetches it, and it suits anyone following the linked video tutorials. It does not suit an environment where piping a downloaded script into iex is unacceptable practice, because that is the delivery mechanism for every tool here, and it does not suit a team that needs supported software. Before running anything, read the script under light/ in the repository rather than the URL, and note that the newest scripts may require an invitation code obtained by interacting with the channel.

Frequently asked questions

Official sources

1. Cotton059/Light-Help on GitHub
2. Issues
3. License: GPL-3.0
4. README