hatch3r-cli-jq

<!-- HATCH3R-CLI-SKILL-GENERATED v1 --> # jq JSON processor and query language ## §0 — Ambiguity & Safety Gate (P8 B1) Before invoking `jq`, resolve these via `agents/shared/user-question-protocol.md` (default behavior, not exception-driven): - **Scope:** when the input JSON path is ambiguous (a glob like `*.json` or a slurp over several shards), confirm which files feed the filter before running. - **Irreversibility:** `jq` reads stdin and writes stdout, so it is non-destructive by itself — but redirecting its output over the source (`jq … input.json > input.json`) truncates the file before `jq` reads it. Write to a temp file and rename, never redirect over the input. - **Ambiguity:** when the request maps to two or more filter expressions with materially different output shape (raw `-r` vs JSON, `select` vs `map`), ask which one. ## Fan-out Discipline (P8 B2) Tier 1 reference card — no fan-out. This skill is a single-tool usage reference an agent consults inline; it spawns no sub-agents. Fan-out is owned by the calling workflow per its own Fan-out Discipline block. Source: `rules/hatch3r-fan-out-discipline.md` (P8 B2). ## When to Use Reach for `jq` when the task is in the **json** category and the agent would otherwise call an MCP tool or read large outputs into context. ## Token Cost CLI tools return structured stdout that fits in <1KB for typical queries; equivalent MCP calls regularly exceed 10KB. Reference: Anthropic engineering (Nov 4 2025) — code-execution-ov...