skogai-jq_skill

This skill enables rapid JSON transformations and schema-driven operations to extract, validate, and compose nested data efficiently.
  • Shell

1

GitHub Stars

14

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill skogai/lore --skill skogai-jq

  • AGENTS.md2.8 KB
  • backlog.md5.9 KB
  • CHEAT_SHEET.md6.9 KB
  • CLAUDE.md6.6 KB
  • examples.md7.2 KB
  • IMPLEMENTATION_SPEC.md15.4 KB
  • patterns.md4.6 KB
  • proposals.md8.6 KB
  • README.md5.1 KB
  • SKILL.md6.4 KB
  • test-all.sh1.2 KB
  • USAGE_EXAMPLES.md7.6 KB
  • vision.md5.3 KB
  • whats-next.md9.6 KB

Overview

This skill provides a schema-driven library of 60+ jq transformations tailored for AI agents working with JSON. It exposes small, composable transforms with explicit input/output contracts and argument-based invocation. The collection emphasizes discoverability and safe, minimal implementations to make JSON manipulation predictable and testable.

How this skill works

Each transform is a standalone jq script that accepts parameters via --arg and --argjson and operates on JSON piped through stdin. Transforms are organized by category (CRUD, array, string, extract, validate, type conversions) and are designed to be chained with Unix pipes for multi-step workflows. Schemas describe expected inputs, outputs, and examples so you can pick transforms by contract rather than guessing behavior.

When to use it

  • Manipulating nested JSON (get/set/delete/check/merge) without writing custom jq every time
  • Filtering, mapping, reducing, flattening or deduplicating arrays in JSON payloads
  • Extracting patterns from text fields (URLs, code blocks, mentions) embedded in JSON
  • Validating required fields or types before further processing
  • Converting JSON values between types (to-string, to-number, to-array) safely
  • Composing multi-step transformations for API response normalization or config generation

Best practices

  • Prefer transforms by schema: choose a transform whose input/output contract matches your goal
  • Pass parameters only via --arg or --argjson to keep transforms deterministic and reusable
  • Chain small transforms via pipes instead of creating a single large jq script
  • Run the provided test scripts for a transform before using it in production
  • Use try/catch patterns and has() checks in custom additions to avoid jq pitfalls

Example use cases

  • Normalize API responses: filter active users, map to emails, and convert timestamps to ISO
  • Edit configuration files: set nested fields, add defaults, and validate required keys
  • Extract metadata: pull URLs and mentions from text fields into a summary array
  • Data cleaning: deduplicate, flatten nested arrays, and coerce string numbers to numbers
  • Validation pipeline: assert required fields and types before ingestion into a database

FAQ

Supply parameters with jq's --arg and --argjson flags; transforms use those args instead of hardcoded values.

Can I chain transforms?

Yes. Transforms are designed to be composable via Unix pipes so you can build multi-step workflows.

What if a path is missing or has the wrong type?

Transforms follow type-safe patterns: they use existence checks, try/catch, and graceful fallbacks to avoid hard failures.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational