From 656d6041d18a60323a26488f03f5a1cc9d294ad6 Mon Sep 17 00:00:00 2001 From: Mark Schaller Date: Fri, 16 Oct 2026 01:46:09 -0400 Subject: [PATCH] Say that jq is optional (for discussion) SKILL.md lists jq among the tools every migration requires, and says to stop and ask the user to install anything missing. No script in scripts/ calls jq. An unattended agent cannot ask, so it improvises. In any2bazel-lab's migration runs, in containers without jq, agents tried `sudo apt-get install jq`, downloaded a jq binary from GitHub (two runs), or spent three or four calls establishing they did not need it. One agent wrote the finding down itself: "No script under the skill's scripts/ directory invokes it". jq is now described as a convenience, with python3 -m json.tool as the fallback. In the lab's six runs with this change, no agent installed or downloaded jq. This is a proposal for discussion: the maintainers may want jq for interactive use, where asking the user is cheap. Lab-Proposal: P28 Co-Authored-By: Claude Opus 5.5 --- SKILL.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/SKILL.md b/SKILL.md index 5ba87c7..0e10ae8 100644 --- a/SKILL.md +++ b/SKILL.md @@ -25,7 +25,9 @@ install them. - `python3` - `bazel` or `bazelisk` - `curl` or `wget` -- `jq` + +`jq` is handy for reading the JSON outputs, but no script needs it: if it is +missing, carry on with `python3 -m json.tool`. ## Migration strategy overview