Seo Meta Generator - Auto-activating skill for Frontend Development. Triggers on: seo meta generator, seo meta generator Part of the Frontend Development skill category.
38
Quality
7%
Does it follow best practices?
Impact
98%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/seo-meta-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 triggers, lacks any explanation of capabilities, and provides no guidance on when Claude should select this skill. The description fails on all core dimensions needed for effective skill routing.
Suggestions
Add specific actions the skill performs, e.g., 'Generates SEO meta tags including title tags, meta descriptions, Open Graph tags, and Twitter cards for web pages.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs meta tags, SEO optimization, social media previews, og:tags, or page descriptions for HTML pages.'
Include varied trigger terms users would naturally say: 'meta tags', 'page title', 'meta description', 'social preview', 'og tags', 'Twitter card'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Seo Meta Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of generating meta tags, titles, descriptions, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' clause is just the skill name repeated, not meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The triggers listed are redundant ('seo meta generator' repeated twice) and overly specific. Missing natural variations users would say like 'meta tags', 'SEO tags', 'page description', 'title tag', 'og tags', or 'social media preview'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SEO meta generator' is somewhat specific to a niche, the lack of detail about what it generates (meta descriptions, OG tags, structured data?) could cause confusion with other SEO-related or frontend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%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 generic template with no actual SEO meta generation guidance. It lacks any executable code, specific meta tag formats, or concrete examples of generating title tags, descriptions, or Open Graph metadata. The content describes capabilities without demonstrating them.
Suggestions
Add concrete code examples showing how to generate meta tags (e.g., title, description, og:image) for different frameworks like React or Vue
Include specific meta tag templates with character limits and best practices (e.g., title under 60 chars, description 150-160 chars)
Provide example inputs and expected outputs showing how to transform page content into optimized meta tags
Remove generic boilerplate sections like 'Example Triggers' and replace with actionable implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about SEO meta 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 abstractly ('Generates production-ready code') but never shows how to actually generate SEO meta tags. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content only lists vague capabilities without any sequence, process, or validation checkpoints for generating SEO meta content. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections (Purpose, When to Use, Capabilities), but there are no references to detailed materials and the sections contain no substantive content worth organizing. | 2 / 3 |
Total | 5 / 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 | |
994edc4
Table of Contents
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.