Batch Script Progress

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: No account, no API key and no paid service. Local runtimes only, and only for the bundled verifier and examples: Node.js 20 or newer to run tests/verify-examples.mjs, plus Python 3.9 or newer and PowerShell 5.1 or newer for their probes (missing runtimes are reported as failures, not skipped). The skill itself is a design method you apply to your own scripts. At use time it works on your scripts locally; the method requires redacting credentials, query parameters, personal data and sensitive paths from progress and failure records before formatting them. Nothing is sent anywhere by the skill. Install "Batch Script Progress" for me. A method for creating or modifying Python, PowerShell or Node.js scripts that process many files, records or API requests, so their runtime output stays observable. The skill fixes the existing contract first (input unit, stdout consumers, failure and exit policies), then defines a small output contract together with the work: a start record, bounded progress with counters, a sanitized per item failure record, and one final summary with the outcome and exit status. It separates progress (stderr by default) from the machine readable result on stdout, forbids fabricated percentages for unknown totals, and requires verification that reads the child process output while it is still running. It ships executable example probes in Python, PowerShell and Node.js, language notes, a verification guide, and a cross language verifier that runs the probes only. Repository: https://github.com/github/awesome-copilot (the skill is the whole skills/batch-script-progress/ folder at the pinned commit: SKILL.md, examples/batch.mjs, examples/batch.ps1, examples/batch.py, references/language-notes.md, references/verification.md, tests/verify-examples.mjs) Pinned version: install the code at commit cb64ad12e32737ae764becd6885462e9b4c7cb00 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/github/awesome-copilot into a temporary folder, check out commit cb64ad12e32737ae764becd6885462e9b4c7cb00, and copy the skills/batch-script-progress/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 3ca5d448539a2dfe8cf47b4c673c06f07acd9b08e71f69c3b15d1c27b5942641 - examples/batch.mjs: SHA-256 7044f415f065cab028bf3b47345d53b6e94a666e96392e4fded2351ce5e86968 - examples/batch.ps1: SHA-256 71dd690ab34cd75cbb3fb5787da541f5aa126e5404119cd8c050a11a389d0fd5 - examples/batch.py: SHA-256 67f0a54f59d8cfc544ad47bb0c435f97990098b6863720fbb4826d437fea1b93 - references/language-notes.md: SHA-256 40cbb417e4fb87b2920fe83e5a3bc74ccb2752d8552c9a3b5c29bb6a47fb37b4 - references/verification.md: SHA-256 fe94e7140bed3d35a713abaa0671b0d7c08f0f00f21dc7894d44c9b2cb791314 - tests/verify-examples.mjs: SHA-256 75edaea2d607fd2ba2d006a1793e284178552bc679ec2b5cf8a7f2453b9f976f If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 7 files: SKILL.md, two reference files, three executable example probes (examples/batch.py, batch.ps1, batch.mjs) and one verifier (tests/verify-examples.mjs). The examples are output contract probes on harmless fixtures, not production processors. - Nothing is sent anywhere during installation itself; the only download is the skill folder from GitHub at the pinned commit. The verifier runs the local probes only and makes no network calls. - The method explicitly requires redacting credentials, query parameters, personal data and sensitive paths before any progress or failure record is formatted, and forbids dumping raw exceptions or whole input records by default. - The verifier checks the bundled probes only: SKILL.md says plainly that it does not prove an arbitrary generated script works. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "batch-script-progress", keeping every file (SKILL.md, examples/batch.mjs, examples/batch.ps1, examples/batch.py, references/language-notes.md, references/verification.md, tests/verify-examples.mjs). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account, provide any API key, or install any local tool named in the prerequisites; using the skill is a separate step that only starts when I ask for it, and every paid or authenticated use disclosed above happens only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.