hypermedia-link-generator
Hypermedia Link Generator - Auto-activating skill for API Development. Triggers on: hypermedia link generator, hypermedia link generator Part of the API Development skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
0.89xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/hypermedia-link-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any explanation of capabilities or concrete actions, and provides no guidance on when to use it. The description would be nearly useless in a collection of 10+ skills.
Suggestions
Add specific actions the skill performs, e.g., 'Generates HATEOAS-compliant hypermedia links for REST APIs, creates self-documenting resource URLs, adds navigation links to API responses'
Add a 'Use when...' clause with natural trigger terms like 'Use when building REST APIs, adding HATEOAS links, creating self-documenting APIs, or when the user mentions hypermedia, resource links, or API navigation'
Include common variations users might say: 'HATEOAS', 'REST links', 'API links', 'resource URLs', 'self-documenting API', 'link relations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Hypermedia Link Generator') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what generating hypermedia links actually involves. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('hypermedia link generator, hypermedia link generator'). This is technical jargon that users are unlikely to naturally say, and there are no variations like 'HATEOAS', 'REST links', 'API links', or 'resource URLs'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'hypermedia link generator' is a specific concept, the lack of detail about what it actually does means it could potentially overlap with other API-related skills. The category mention 'API Development' is too broad to provide clear distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual instructional content. It describes what a hypermedia link generator skill would do without providing any concrete guidance, code examples, or actionable information about generating hypermedia links in APIs.
Suggestions
Add executable code examples showing how to generate hypermedia links (e.g., HAL format, JSON-LD, or custom link structures) in common frameworks
Include specific link relation types (self, next, prev, collection) with concrete JSON output examples
Provide a clear workflow for adding hypermedia to existing REST endpoints, including validation of link structure
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about hypermedia link generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually generate hypermedia links or provides any executable examples. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no sequences, validation checkpoints, or actual process instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no code examples to link to, and no structured navigation to deeper content about hypermedia patterns like HAL, JSON-LD, or HATEOAS. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.