What problem does it solve? Diagnosing CI failures requires pulling console logs, API responses, and build artifact ZIPs from a private Jenkins server, but doing this with raw curl or unbounded scripts risks leaking credentials, following unsafe redirects, exhausting memory on huge archives, or overwriting existing files. This Skill provides one fixed-policy helper that transports and inspects those artifacts under strict authentication, redirect, size, and time ceilings. ## Core Features & Use Cases - Bounded remote access: Probe URL metadata, view bounded text with grep/head/tail selection, or fetch artifacts to a new file, restricted to an allowlisted HTTPS host with named auth profiles and same-origin redirect validation. - Safe ZIP inspection: List, view, or extract individual ZIP members with metadata cross-checks, CRC and DEFLATE verification, and rejection of traversal paths, symlinks, encryption, and ZIP64. - Atomic no-clobber output: Fetched and extracted files publish through a same-parent mode-0600 temporary file with atomic rename, never overwriting existing paths. - Use Case: A build fails on the private Jenkins server. Use the helper to fetch the build's logs.zip, list its members, and show only the lines matching ERROR or Exception from the console log, all within fixed byte and deadline limits. ## Quick Start Use the bug-triage-playbook skill to fetch the console log from this Jenkins build URL and show the lines matching ERROR with two lines of context.
