reading-buildsworth-logs

To download and inspect Buildkite build artifacts, you can use this skill to retrieve `.jsonl` pi session logs from Buildsworth builds and delegate reading to sub-agents to manage context size efficiently.

You can read large Buildsworth session logs without exceeding context limits because this skill offloads the processing of large log files to sub-agents, maintaining context efficiency while answering specific inquiries about build findings.

To download Buildsworth artifacts, you need the `using-buildkite` skill to list and download artifacts, along with `jq` and `bk` dependencies installed in your environment to support the retrieval and parsing of `.jsonl` session logs.

To check a failed Buildkite build for security issues, download the session log artifact for the specific build number and ask a sub-agent to query whether any security issues were detected in the agent's findings.

This skill specifically downloads and reads pi session logs from builds on the buildkite/buildsworth pipeline, meaning it is tailored for inspecting artifacts from that particular pipeline rather than arbitrary Buildkite pipelines.

The best way to ask specific questions about agent behavior is to use this skill to download the `.jsonl` pi session log and delegate focused inquiries to sub-agents, allowing them to extract targeted answers about errors or findings without overwhelming context.