seo-meta-generator
Seo Meta Generator - Auto-activating skill for Frontend Development. Triggers on: seo meta generator, seo meta generator Part of the Frontend Development skill category.
36
3%
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 boilerplate template with the skill name inserted, providing no meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SEO meta tags including title tags, meta descriptions, Open Graph tags, and Twitter Card markup for web pages.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about SEO tags, meta descriptions, Open Graph metadata, search engine optimization for HTML pages, or improving page discoverability.'
Remove the duplicated trigger term and expand with varied natural keywords users would actually say, such as 'meta tags', 'page title', 'SEO optimization', 'social media preview tags', '.html head section'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Seo Meta Generator') and its category ('Frontend Development') but does not describe any concrete actions like generating meta tags, creating title tags, producing Open Graph tags, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a duplicated skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('seo meta generator, seo meta generator'). It lacks natural user keywords like 'meta tags', 'SEO tags', 'title tag', 'Open Graph', 'meta description', or 'search engine optimization'. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'Seo Meta Generator' is somewhat specific to SEO meta tag generation, which gives it a narrower niche than a fully generic description. However, the lack of concrete details means it could overlap with other SEO or frontend 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 template with no actual content. It repeatedly references 'seo meta generator' without ever defining what it does, how to generate SEO meta tags, or providing any actionable code or instructions. It fails on every dimension as it contains zero technical substance.
Suggestions
Add concrete, executable HTML/JavaScript examples showing how to generate SEO meta tags (e.g., <meta name="description">, Open Graph tags, Twitter cards, structured data).
Define a clear workflow: e.g., 1) Analyze page content, 2) Generate meta title/description within character limits, 3) Add Open Graph and Twitter Card tags, 4) Validate with a tool or checklist.
Remove all boilerplate filler text ('This skill provides automated assistance...') and replace with actual technical guidance, character limit rules, and best practices for SEO meta content.
Add a validation checklist or reference to tools (e.g., Google Rich Results Test, social media debuggers) so outputs can be verified.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'seo meta generator' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific examples, no SEO meta tag formats, no HTML snippets. The skill describes rather than instructs and provides nothing executable. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The 'step-by-step guidance' is merely claimed in a bullet point but never actually provided. There are no sequences, validation steps, or checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no meaningful structure, no references to detailed materials, and no navigation to supplementary files. | 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
3076d78
- 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.