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

—

Does it follow best practices?

Impact

82%

1.20x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is an efficient, highly actionable command reference with no wasted tokens. Its only real weakness is that the Additional Resources section points to reference files that are not present in the bundle.

Suggestions

Create the referenced ./references/ files (jq-patterns.md, yq-patterns.md, config-files.md) or remove the Additional Resources section so the skill does not point to missing material.

Add a brief validation note near the destructive `yq -i` in-place edit example (e.g., preview the change before writing) to guard against accidental config mutation.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables and executable code blocks only, with no padded explanations of what JSON/YAML are or how the tools work; every token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands with real file examples (e.g., `jq '.scripts.build' package.json`, `yq '.services.web.image' docker-compose.yml`) and a side-by-side quick-reference table.	3 / 3
Workflow Clarity	This is a single-purpose command reference rather than a multi-step process; per the simple-skills note the unambiguous, well-organized single action scores 3, and no batch/destructive workflow requires validation checkpoints here.	3 / 3
Progressive Disclosure	The body cleanly signals one-level-deep references with descriptions, but the referenced files (./references/jq-patterns.md, yq-patterns.md, config-files.md) and the references/ directory do not exist in the bundle, so the navigation points to missing material.	2 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is concise, third-person, and names concrete tools and actions with an explicit 'Triggers on' clause covering both what and when. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Process JSON with jq', 'Filter, transform, query structured data') tied to specific tools and formats, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Process JSON with jq and YAML/TOML with yq. Filter, transform, query') and when ('Triggers on: ...'), matching the anchor that requires explicit trigger guidance.	3 / 3
Trigger Term Quality	The 'Triggers on:' list covers natural user terms ('parse JSON', 'Docker Compose', 'K8s manifests', 'GitHub Actions workflows', 'package.json', 'filter data') with good breadth of common variations.	3 / 3
Distinctiveness Conflict Risk	Clear niche of CLI structured-data processing with distinct, format-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: 26d37ce

Reviewed: about 23 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.