design-metadata-schema
Design comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill design-metadata-schema46
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 provides a basic understanding of the skill's domain (metadata frameworks and tagging systems) but suffers from missing explicit trigger guidance, which is critical for skill selection. It uses appropriate third-person voice but lacks the specificity and natural trigger terms needed for reliable skill matching among many options.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user needs to organize content, create taxonomies, define tagging conventions, or structure data classification systems.'
Include more natural trigger terms users would say: 'taxonomy', 'categorization', 'data classification', 'content organization', 'labeling system', 'schema design'.
Expand specific actions to include concrete deliverables: 'Creates metadata schemas, defines controlled vocabularies, establishes naming conventions, designs hierarchical taxonomies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (metadata frameworks) and some actions ('develops structured metadata templates and tagging systems'), but lacks comprehensive concrete actions like specific deliverables or methods. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'metadata', 'templates', 'tagging systems', but misses common variations users might say such as 'taxonomy', 'categorization', 'data classification', 'schema', or 'labeling'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to metadata work, but 'frameworks' and 'templates' are generic enough to potentially overlap with documentation, data modeling, or content management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill describes a metadata schema design process at a high conceptual level but fails to provide actionable, executable guidance. It tells Claude what to do without showing how - no actual JSON Schema examples, no code for generating schemas, no concrete validation commands. The workflow is logically structured but lacks the specificity needed for Claude to execute reliably.
Suggestions
Add a complete, executable JSON Schema example showing the expected output format with Dublin Core mappings
Include concrete code or commands for schema validation (e.g., using jsonschema library or ajv)
Add a validation checkpoint after schema generation: 'Validate schema syntax with: jsonschema.validate(schema)' with error recovery steps
Replace abstract descriptions like 'Define fields and their properties' with actual field definition examples showing exact syntax
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably efficient but includes some unnecessary structure like the 'Quick Reference' section that adds little value, and the inputs section could be more compact. | 2 / 3 |
Actionability | Entirely abstract with no concrete code, commands, or executable examples. Describes what to do ('Define fields', 'Generate schema') without showing how - no actual JSON Schema example, no code snippets, no copy-paste ready content. | 1 / 3 |
Workflow Clarity | Steps are listed in logical sequence but lack validation checkpoints. No feedback loop for verifying the generated schema works correctly, no concrete validation commands or testing steps. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections but everything is inline. References to Dublin Core and Schema.org standards could link to detailed reference files. The schema could benefit from separate example files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.