schema-validator
Schema Validator - Auto-activating skill for Data Pipelines. Triggers on: schema validator, schema validator Part of the Data Pipelines skill category.
33
Quality
3%
Does it follow best practices?
Impact
83%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/schema-validator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and any guidance on when to use it. The only distinguishing element is the category mention, but this is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific capabilities: describe what the validator does (e.g., 'Validates JSON/YAML schemas against data, checks field types, identifies missing required fields, reports validation errors')
Include a 'Use when...' clause with natural trigger terms like 'validate schema', 'check data format', 'schema errors', 'data validation', 'JSON schema', 'YAML validation'
Remove the duplicate trigger term and expand with variations users would naturally say when needing schema validation
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Schema Validator') without describing any concrete actions. There are no specific capabilities listed like 'validates JSON schemas', 'checks data types', or 'reports validation errors'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'schema validator' repeated twice, which is redundant and lacks natural variations users might say like 'validate schema', 'check data format', 'JSON schema', 'data validation', or 'schema errors'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Schema Validator' is somewhat specific to a domain (data validation), the lack of detail about what types of schemas or validation it performs means it could overlap with other validation-related skills. The 'Data Pipelines' category provides some context. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual content. It contains only meta-descriptions of what a schema validator skill should do without providing any concrete guidance, code examples, validation patterns, or schema formats. The content adds zero value beyond what Claude already knows about schema validation.
Suggestions
Add concrete schema validation code examples (e.g., JSON Schema, Avro, Protobuf validation with specific libraries like jsonschema, fastavro)
Include specific validation patterns with executable code showing how to validate data against schemas in ETL pipelines
Define a clear workflow for schema validation: load schema -> validate data -> handle errors -> report results
Add example schemas and sample data showing valid/invalid cases with expected error outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The entire content describes rather than instructs, with vague phrases like 'provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for schema validation tasks. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related resources despite mentioning 'Related Skills'. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.