fixing-metadata
tessl i github:ibelick/ui-skills --skill fixing-metadataShip correct, complete metadata.
Validation
69%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
77%This is a well-structured metadata guidelines skill that efficiently communicates rules through prioritized categories and clear bullet points. Its main weakness is the lack of concrete code examples showing correct vs incorrect metadata implementations, which would significantly improve actionability for a developer-facing skill.
Suggestions
Add 2-3 concrete code examples showing correct metadata implementation (e.g., Next.js metadata API, HTML head tags) for the most critical categories
Include a before/after example demonstrating how to fix a common violation like duplicate title tags or mismatched canonical/og:url
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and bullet points to convey rules without unnecessary explanation. It assumes Claude understands metadata concepts and doesn't waste tokens explaining what Open Graph or canonical URLs are. | 3 / 3 |
Actionability | The skill provides clear rules and guidelines but lacks concrete code examples. While the rules are specific, there are no executable snippets showing correct metadata implementation patterns or before/after examples of fixes. | 2 / 3 |
Workflow Clarity | The workflow is clear: the skill defines two usage modes (apply constraints vs review file), prioritizes rules by category, and provides explicit review guidance with a clear sequence (fix critical first, verify agreement, test on real URL). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a priority table, but it's a monolithic file with no references to external documentation. For a skill of this length (~100 lines), some content like detailed examples could be split into separate files. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
0%This description is critically underdeveloped and fails on all dimensions. It provides no concrete actions, no trigger terms, no 'when to use' guidance, and is so generic it could apply to almost anything involving metadata. Claude would have no reliable basis for selecting this skill over others.
Suggestions
Specify what type of metadata this skill handles (e.g., 'file metadata', 'image EXIF data', 'package.json fields', 'HTML meta tags') and list concrete actions performed.
Add a 'Use when...' clause with specific trigger terms users would naturally say, such as 'Use when the user asks about package metadata, npm publish, or version fields'.
Define the domain clearly to distinguish from other metadata-related tasks (e.g., 'Validates and generates package.json metadata for npm publishing' vs generic 'metadata').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('Ship correct, complete metadata') without describing any concrete actions. It doesn't specify what kind of metadata, what 'shipping' means, or what operations are performed. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause or any explicit trigger guidance, and the 'what' is extremely vague. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Ship' and 'metadata' are generic terms that don't help identify when this skill should be used. Users wouldn't naturally say 'ship metadata' when requesting help. | 1 / 3 |
Distinctiveness Conflict Risk | 'Metadata' is extremely generic and could apply to countless domains (files, images, code, databases, APIs, etc.). This description would conflict with many other skills and provides no clear niche. | 1 / 3 |
Total | 4 / 12 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.