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
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 names the skill and its category but fails to describe any concrete capabilities, use cases, or natural trigger terms. The duplicate trigger term and lack of a 'Use when...' clause make it nearly useless for distinguishing this skill from others in a large skill library.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates hypermedia links (HATEOAS) for REST API responses, including self links, pagination links, and related resource links.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about HATEOAS, REST hypermedia, API link relations, HAL format, adding navigation links to API responses, or self/rel links.'
Remove the duplicate trigger term and expand with varied natural language terms users might actually use, such as 'HATEOAS', 'REST links', 'link relations', 'HAL links', 'API navigation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Hypermedia Link Generator') and its category ('API Development') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'generates', 'creates', 'adds links to responses', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated as a trigger. There is no explicit 'Use when...' guidance or meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'hypermedia link generator' repeated twice. This is a narrow technical phrase that users are unlikely to naturally say. Missing common variations like 'HATEOAS', 'REST links', 'API links', 'HAL', 'link relations', or 'self links'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'hypermedia link generator' is fairly niche and unlikely to conflict with many other skills. However, the vague 'API Development' category and lack of specificity could cause overlap with other API-related skills. | 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 an empty shell with no actual instructional content. It consists entirely of generic meta-descriptions and trigger phrases repeated in various forms, without any concrete guidance on generating hypermedia links, HATEOAS patterns, link relation types, or any API development concepts. It provides no value to Claude beyond what the skill's title already conveys.
Suggestions
Add concrete, executable code examples showing hypermedia link generation (e.g., HAL, JSON:API, or Siren format responses with _links objects)
Include a clear workflow for generating hypermedia links: identify resources → define link relations → construct link objects → validate against standards like RFC 8288
Provide specific examples of common link relation types (self, next, prev, collection) with JSON output schemas that Claude can directly use
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable technical content covering HATEOAS patterns and link generation strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('hypermedia link generator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of hypermedia link structures, no API patterns, no schemas. The content only describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to detailed materials, no links to examples or schemas, and no meaningful structural organization beyond boilerplate headings. | 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
4dee593
- 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.