design-metadata-schema

Design comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/design-metadata-schema/SKILL.md

Quality

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 purpose around metadata design but lacks explicit trigger guidance, which is critical for skill selection. It uses appropriate third-person voice but needs more specific actions and natural user keywords to be effective in a multi-skill environment.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to organize content with tags, create taxonomy structures, or design metadata schemas for content management.'

Include more natural trigger terms users would say: 'taxonomy', 'content classification', 'tag hierarchy', 'metadata schema', 'data labeling'.

List more concrete actions such as 'creates tag hierarchies, defines metadata fields, establishes naming conventions, designs content classification systems'.

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', 'data classification', 'content tagging', 'metadata schema', or 'tag structure'.	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 provides a conceptual framework for metadata schema design but lacks the concrete, executable guidance needed for actionability. The workflow is logically structured but missing validation checkpoints and actual code/schema examples. The content would benefit significantly from sample JSON Schema output and specific tooling commands.

Suggestions

Add a concrete JSON Schema example showing a complete metadata schema with Dublin Core mappings that Claude can use as a template

Include executable validation commands or code snippets (e.g., using ajv or jsonschema library to validate content against the generated schema)

Add a validation checkpoint after schema generation: 'Validate schema syntax with: npx ajv validate -s schema.json' with error recovery guidance

Provide a minimal working example showing input content and the resulting metadata schema output

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary explanation. Phrases like 'This skill defines structured fields, validation rules, and standards compliance to improve searchability and management' explain purpose Claude can infer. The workflow steps could be more compact.	2 / 3
Actionability	The skill provides abstract descriptions rather than concrete, executable guidance. There are no code examples, no actual schema templates, no sample JSON Schema output, and no specific commands. It describes what to do conceptually but not how to actually do it.	1 / 3
Workflow Clarity	Steps are listed in a logical sequence, but there are no validation checkpoints or feedback loops. No guidance on how to verify the schema is correct, no error recovery steps, and no concrete validation commands or tools mentioned.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but it's somewhat monolithic. References to Dublin Core and Schema.org standards could link to reference materials. No external files referenced for detailed examples or advanced usage patterns.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: dandye/ai-runbooks
Commit: 4d132c7

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

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.