Win10 Initial Setup Script
by bytesagain3
PowerShell script for automation of routine tasks done after fresh installations of Windows 10 / Ser win10 initial setup script, powershell, powershell.
安装
claude skill add --url github.com/openclaw/skills/tree/main/skills/bytesagain3/windows-setup文档
Windows Setup
A utility toolkit for tracking and managing Windows setup, configuration, and post-installation tasks. Log setup runs, check configurations, analyze system state, generate reports, and export data — all from the command line.
Commands
All commands accept optional <input> arguments. Without arguments, they display recent entries from their log.
| Command | Description |
|---|---|
windows-setup run <input> | Run a setup task and log the result |
windows-setup check <input> | Check a system configuration or prerequisite |
windows-setup convert <input> | Convert setup scripts or configuration formats |
windows-setup analyze <input> | Analyze system state, installed components, or logs |
windows-setup generate <input> | Generate setup scripts, checklists, or templates |
windows-setup preview <input> | Preview a setup operation before executing |
windows-setup batch <input> | Batch process multiple setup tasks at once |
windows-setup compare <input> | Compare two system configurations or setup states |
windows-setup export <input> | Log an export operation |
windows-setup config <input> | Log or update configuration entries |
windows-setup status <input> | Log a status check result |
windows-setup report <input> | Generate or log a report entry |
windows-setup stats | Show summary statistics across all log files |
windows-setup export json|csv|txt | Export all data in JSON, CSV, or plain text format |
windows-setup search <term> | Search across all log entries for a keyword |
windows-setup recent | Show the 20 most recent activity entries |
windows-setup help | Show all available commands |
windows-setup version | Print version (v2.0.0) |
Data Storage
All data is stored locally in ~/.local/share/windows-setup/. Each command maintains its own .log file with timestamped entries in YYYY-MM-DD HH:MM|value format. A unified history.log tracks all operations across commands.
Export formats supported:
- JSON — Array of objects with
type,time, andvaluefields - CSV — Standard comma-separated with
type,time,valueheader - TXT — Human-readable grouped by command type
Requirements
- Bash 4.0+ with
set -euo pipefail(strict mode) - Standard Unix utilities:
date,wc,du,grep,tail,sed,cat - No external dependencies — runs on any POSIX-compliant system
- Works on WSL, Git Bash, or any Bash environment on Windows
When to Use
- Post-installation task tracking — Log all setup steps after a fresh Windows install for reproducibility
- Configuration auditing — Record and compare system configurations before and after changes
- Batch setup automation — Queue up multiple setup tasks and track their completion status
- Generating setup reports — Export task history to JSON/CSV for documentation or compliance
- Comparing system states — Use
compareto record differences between baseline and current configurations
Examples
# Log a setup task
windows-setup run "Disable telemetry via Group Policy"
# Check a system prerequisite
windows-setup check ".NET Framework 4.8 installed"
# Analyze current system state
windows-setup analyze "Startup apps: 12 enabled, 3 high-impact"
# Compare before and after setup
windows-setup compare "Default vs hardened: 23 registry changes"
# Batch process multiple tasks
windows-setup batch "Privacy settings: 8 toggles disabled"
# Export all setup history to JSON
windows-setup export json
# Search for specific setup entries
windows-setup search "registry"
# View summary statistics
windows-setup stats
How It Works
Windows Setup stores all data locally in ~/.local/share/windows-setup/. Each command creates a dedicated log file (e.g., run.log, check.log, config.log). Every entry is timestamped and appended, providing a full audit trail of all setup operations. The history.log file aggregates activity across all commands for unified tracking.
When called without arguments, each command displays its most recent 20 entries, making it easy to review past setup work without manually inspecting log files.
Output
All output goes to stdout. Redirect to a file with:
windows-setup stats > report.txt
windows-setup export json # writes to ~/.local/share/windows-setup/export.json
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
相关 Skills
表格处理
by anthropics
围绕 .xlsx、.xlsm、.csv、.tsv 做读写、修复、清洗、格式整理、公式计算与格式转换,适合修改现有表格、生成新报表或把杂乱数据整理成交付级电子表格。
✎ 做 Excel/CSV 相关任务很省心,能直接读写、修复、清洗和格式转换,尤其擅长把乱七八糟的表格整理成交付级文件。
PDF处理
by anthropics
遇到 PDF 读写、文本表格提取、合并拆分、旋转加水印、表单填写或加解密时直接用它,也能提取图片、生成新 PDF,并把扫描件通过 OCR 变成可搜索文档。
✎ PDF杂活别再来回切工具了,文本表格提取、合并拆分到OCR识别一次搞定,连扫描件也能变可搜索。
Word文档
by anthropics
覆盖Word/.docx文档的创建、读取、编辑与重排,适合生成报告、备忘录、信函和模板,也能处理目录、页眉页脚、页码、图片替换、查找替换、修订批注及内容提取整理。
✎ 搞定 .docx 的创建、改写与精排版,目录、批量替换、批注修订和图片更新都能自动化,做正式文档尤其省心。
相关 MCP 服务
文件系统
编辑精选by Anthropic
Filesystem 是 MCP 官方参考服务器,让 LLM 安全读写本地文件系统。
✎ 这个服务器解决了让 Claude 直接操作本地文件的痛点,比如自动整理文档或生成代码文件。适合需要自动化文件处理的开发者,但注意它只是参考实现,生产环境需自行加固安全。
by wonderwhy-er
Desktop Commander 是让 AI 直接执行终端命令、管理文件和进程的 MCP 服务器。
✎ 这工具解决了 AI 无法直接操作本地环境的痛点,适合需要自动化脚本调试或文件批量处理的开发者。它能让你用自然语言指挥终端,但权限控制需谨慎,毕竟让 AI 执行 rm -rf 可不是闹着玩的。
EdgarTools
编辑精选by dgunning
EdgarTools 是无需 API 密钥即可解析 SEC EDGAR 财报的开源 Python 库。
✎ 这个工具解决了金融数据获取的痛点——直接让 AI 读取结构化财报,比如让 Claude 分析苹果的 10-K 文件。适合量化分析师或金融开发者快速构建数据管道。但注意,它依赖 SEC 网站稳定性,高峰期可能延迟。