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
Quality
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 well-crafted skill description that excels across all dimensions. It clearly specifies the tools (jq, yq), data formats (JSON, YAML, TOML), and actions (filter, transform, query), while providing comprehensive trigger terms that cover common use cases like config files, Docker Compose, and Kubernetes manifests. The 'Triggers on:' clause effectively communicates when Claude should select this skill.
| 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 and operations. | 3 / 3 |
Completeness | Clearly answers both what ('Process JSON with jq and YAML/TOML with yq. Filter, transform, query structured data') AND when ('Triggers on:' followed by explicit trigger terms). The 'Triggers on:' clause serves as an explicit 'Use when' equivalent. | 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 terms users naturally use when working with structured data. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on jq/yq tools for structured data formats (JSON, YAML, TOML). Specific file types and tools mentioned (Docker Compose, K8s manifests, package.json) create distinct triggers unlikely to conflict with general file or code 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 exemplary skill file that maximizes token efficiency while providing comprehensive, actionable guidance. The content is well-organized with clear tables, executable examples, and appropriate progressive disclosure to reference files for advanced patterns. It respects Claude's intelligence by jumping straight into practical commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what JSON/YAML are or how jq/yq work conceptually. Every line is actionable with real commands and examples. | 3 / 3 |
Actionability | All examples are fully executable, copy-paste ready commands with real file references (package.json, docker-compose.yml, deployment.yaml). Covers common use cases with concrete syntax. | 3 / 3 |
Workflow Clarity | This is a reference/utility skill rather than a multi-step workflow. The single-action commands are unambiguous, and the quick reference table provides clear guidance for choosing the right approach. | 3 / 3 |
Progressive Disclosure | Excellent structure with essentials in the main file and clear one-level-deep references to detailed pattern libraries (jq-patterns.md, yq-patterns.md, config-files.md). Navigation is well-signaled. | 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
5342bca
- 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.