CtrlK
BlogDocsLog inGet started
Tessl Logo

design-metadata-schema

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

55

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/design-metadata-schema/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured instruction-only skill that lays out inputs, a sequenced workflow, and a clear output spec. Its main weaknesses are the absence of executable examples and missing validation checkpoints in the workflow.

Suggestions

Add a short concrete schema example (e.g., a minimal JSON Schema snippet) so the output is copy-paste ready rather than purely templated.

Insert an explicit validation checkpoint in the workflow (e.g., verify generated schema against discovered content types at PATH before finalizing output).

Show a sample "Required Outputs" instance for one content type to make the deliverable unambiguous.

DimensionReasoningScore

Conciseness

Lean, well-sectioned instruction content with no padding or re-explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Provides a concrete output-object spec (Field Dictionary, Validation Logic, Mapping) and field types, but guidance is templated rather than executable, missing copy-paste-ready examples.

3 / 5

Workflow Clarity

Four sequenced steps are clearly listed, but validation checkpoints are only implicit (e.g., verifying schema against PATH content types) and no feedback loop is specified.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is well-organized into clearly labeled sections (Inputs, Workflow, Required Outputs, Quick Reference).

5 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 states what the skill does in a specific, third-person voice but omits any explicit "Use when..." trigger guidance, leaving Claude without clear invocation cues. Trigger-term coverage is adequate but lacks natural synonyms.

Suggestions

Add an explicit "Use when..." clause naming concrete user triggers (e.g., "Use when designing content metadata schemas, tagging systems, or standards-aligned field dictionaries").

Broaden trigger terms with natural synonyms and formats users say (e.g., "metadata schema", "field dictionary", "tagging taxonomy", "Dublin Core", "JSON Schema").

Name one or two additional concrete deliverables beyond templates and tagging systems to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the metadata domain and two concrete actions ("Develops structured metadata templates and tagging systems"), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

Provides a clear "what" but no "Use when..." trigger clause; per judging guidelines, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant terms (metadata, templates, tagging systems) but lacks natural synonyms, file extensions, or phrases users would commonly say.

3 / 5

Distinctiveness Conflict Risk

The metadata-schema niche with templates and tagging systems is mostly distinct with only minor overlap risk against general content skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
dandye/ai-runbooks
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.