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.
96
100%
Does it follow best practices?
Impact
82%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly identifies the tools (jq, yq), the data formats (JSON, YAML, TOML), and the operations (filter, transform, query). The explicit 'Triggers on:' clause provides excellent coverage of natural user phrases and specific file types, making it easy for Claude to select this skill appropriately. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Process JSON with jq', 'YAML/TOML with yq', 'Filter, transform, query structured data'. Names specific tools (jq, yq) and operations (filter, transform, query). | 3 / 3 |
Completeness | Clearly answers both 'what' (process JSON/YAML/TOML with jq/yq, filter/transform/query structured data) and 'when' (explicit 'Triggers on:' clause listing specific scenarios like parse JSON, extract from YAML, query config, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'parse JSON', 'extract from YAML', 'query config', 'Docker Compose', 'K8s manifests', 'GitHub Actions workflows', 'package.json', 'filter data'. These are highly natural phrases users would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carved niche around structured data formats (JSON/YAML/TOML) with specific tools (jq/yq) and concrete file types (Docker Compose, K8s manifests, GitHub Actions workflows, package.json). Unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent reference skill that is concise, actionable, and well-structured. It provides executable examples for common use cases, a useful quick-reference comparison table, and clear pointers to deeper reference materials. The content respects Claude's intelligence by jumping straight into practical commands without explaining basic concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No explanations of what JSON/YAML are, no unnecessary preamble. The tool table, examples, and quick reference are all lean and information-dense. | 3 / 3 |
Actionability | All examples are concrete, executable bash commands with realistic file targets (package.json, docker-compose.yml, deployment.yaml). Copy-paste ready with no pseudocode. | 3 / 3 |
Workflow Clarity | This is a single-task reference skill (querying/filtering data), not a multi-step destructive workflow. The commands are unambiguous and self-contained. The in-place edit with yq -i is the only potentially destructive operation and it's clearly marked. | 3 / 3 |
Progressive Disclosure | Clean overview with essentials inline, then clearly signaled one-level-deep references to detailed pattern libraries (jq-patterns.md, yq-patterns.md, config-files.md). Content is appropriately split between overview and reference files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- Reviewed
Table of Contents
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.