schema-validator
Schema Validator - Auto-activating skill for Data Pipelines. Triggers on: schema validator, schema validator Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill schema-validatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 skill name and category, which is insufficient for Claude to make informed decisions among multiple skills.
Suggestions
Add specific capabilities describing what the validator does, e.g., 'Validates JSON/YAML schemas against data, checks data types and required fields, reports validation errors with line numbers'
Include a 'Use when...' clause with natural trigger terms like 'validate schema', 'check JSON format', 'data validation', 'schema errors', 'malformed data'
Specify what types of schemas are supported (JSON Schema, YAML, XML, etc.) to distinguish from other potential validation skills
| 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 data-related skills. The 'Data Pipelines' category provides some context but isn't sufficient. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It describes what a schema validator skill would do without providing any concrete guidance, code examples, or actionable instructions. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add concrete, executable code examples showing how to validate schemas (e.g., using JSON Schema, Avro, or Protobuf validators)
Define specific validation workflows with clear steps: load schema, validate data, handle errors, report results
Include actual schema validation patterns and common pitfalls specific to data pipelines (e.g., schema evolution, backward compatibility)
Remove all generic boilerplate text and replace with actionable, copy-paste ready commands and configurations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it does rather than instructing how to do anything. There are no executable examples or actual schema validation techniques. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation steps, sequences, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.