Seo Meta Generator - Auto-activating skill for Frontend Development. Triggers on: seo meta generator, seo meta generator Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill seo-meta-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It relies entirely on the skill name without explaining what the skill actually does, what outputs it produces, or when Claude should select it. The duplicate trigger term suggests auto-generated content that was never properly customized.
Suggestions
Add specific capabilities: 'Generates SEO meta tags including title tags, meta descriptions, Open Graph tags, and Twitter cards for web pages.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about meta tags, SEO optimization, page titles, meta descriptions, og:tags, or improving search engine visibility.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'SEO', 'meta tags', 'page metadata', 'search optimization', 'title tag'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill 'Seo Meta Generator' without describing any concrete actions. There are no specific capabilities listed like 'generates title tags', 'creates meta descriptions', or 'analyzes keyword density'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('seo meta generator, seo meta generator'). Missing natural user phrases like 'meta tags', 'page title', 'meta description', 'SEO optimization', 'search engine', or 'og tags'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SEO meta generator' is somewhat specific to a niche, the lack of detail means it could overlap with general SEO skills, content writing skills, or HTML generation skills. The category 'Frontend Development' is too broad to provide distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what a skill should do without any concrete guidance on SEO meta tag generation. The content fails on all dimensions by providing zero actionable information, no code examples, and no real workflow.
Suggestions
Add concrete code examples showing how to generate meta tags (e.g., title, description, Open Graph, Twitter cards) in React/Vue components
Include a clear workflow: analyze page content → generate appropriate meta tags → validate with structured data testing tools
Provide specific meta tag templates with character limits and best practices (e.g., title 50-60 chars, description 150-160 chars)
Remove all generic boilerplate text and replace with actionable, copy-paste ready code snippets
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to generate SEO meta tags. The content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
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.