The scripts-folder problem
Every machine accumulates them: a batch file to clear caches, a PowerShell one-liner to reset the network stack, something to tidy temp directories. They work, but they have no shared conventions, no help, and no dry run. Handing them to someone else is a small act of hostility.
toolskit collects sixteen of those tasks into one application with consistent behaviour across all of them.
What is in it
- Cleanup: temp directories, caches, log rotation, recycle-bin handling.
- Network: stack reset, DNS cache, adapter state, connectivity checks.
- System: service state, startup entries, scheduled-task review.
- Reporting: hardware and OS inventory, disk usage, installed software.
Rules every module follows
- Dry run first. Every module can report what it would do without doing it.
- Say what happened. Modules report counts and paths, not
Done!. - Ask for elevation only when needed. And say why before asking.
- Fail loudly, continue safely. A failed step is reported and does not silently skip the rest.
Design decisions
One module, one job
Sixteen small modules beat four large ones. Small modules are easier to reason about, easier to dry-run, and easier to trust with elevation.
C# on purpose
Proper Windows APIs, real types, and a single binary to hand someone — rather than a script that depends on an execution policy and the right shell.
Getting started
git clone https://github.com/thecrewx/toolskit
cd toolskit
dotnet build -c Release
dotnet run -- --list
dotnet run -- cleanup.temp --dry-run