data-processing

Process JSON with jq and YAML/TOML with yq. Filter, transform, query structured data efficiently. Triggers on: parse JSON, extract from YAML, query config, Docker Compose, K8s manifests, GitHub Actions workflows, package.json, filter data.

1.20x

Quality

81%

Does it follow best practices?

Impact

82%

1.20x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, executable, and well-organized with copy-paste command examples, but its progressive disclosure is undermined by references to bundle files that are not actually present in the skill directory.

Suggestions

Add the missing ./references/jq-patterns.md, ./references/yq-patterns.md, and ./references/config-files.md files, or remove the 'Additional Resources' section so navigation does not point to nonexistent bundles.

De-duplicate the 'Quick Reference' table against the 'jq Essentials' and 'yq Essentials' sections to recover token budget and push conciseness higher.

Consider a brief explicit 'validate output' note for in-place edits (yq -i) since modifying config files is a destructive operation that currently lacks a verification checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean code blocks with inline comments assume Claude's competence and avoid explaining what JSON/jq is; held back from 5 by the 'Quick Reference' table partially duplicating the 'jq/yq Essentials' sections.	4 / 5
Actionability	Provides fully executable, copy-paste-ready bash snippets covering the common cases (extract, filter, transform, count, raw output, in-place edit, format conversion).	5 / 5
Workflow Clarity	A single-purpose tool-reference skill with unambiguous usage examples; the simple-skill exception applies, but there is no explicit multi-step sequencing, so it stops short of 5.	4 / 5
Progressive Disclosure	Navigation is well-signaled one-level-deep ('Additional Resources' -> three reference files), but the references/ directory is empty, so the cited ./references/jq-patterns.md, yq-patterns.md, and config-files.md do not exist — broken references anchor this low.	2 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities and explicit trigger guidance with concrete tool and domain references. Minor improvements would add file extensions and slightly more specific action verbs.

Dimension	Reasoning	Score
Specificity	Names the tools (jq/yq), domains (JSON, YAML/TOML), and three concrete actions ('Filter, transform, query'), with only minor gaps versus comprehensive coverage; not a 5 because the actions remain somewhat generic.	4 / 5
Completeness	Explicitly answers both what ('Process JSON with jq and YAML/TOML with yq. Filter, transform, query') and when ('Triggers on: ...') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Lists many natural trigger phrases users would say ('parse JSON', 'extract from YAML', 'Docker Compose', 'K8s manifests', 'GitHub Actions workflows', 'package.json'); below 5 because explicit file extensions like .json/.yaml are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to specific CLI tools (jq, yq) and concrete config domains, giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/data-processing/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.