seo-meta-optimizer

Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-meta-optimizer/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, actionable SEO-meta rules and a ready-to-use output template, with clean section organization. Its main weaknesses are generic boilerplate sections that waste tokens and an implicit (rather than explicit) validation checkpoint in the workflow. No external references are needed and none are used.

Suggestions

Remove or replace the generic 'Use this skill when', 'Do not use this skill when', and abstract 'Instructions' bullets with skill-specific guidance to improve token efficiency.

Insert an explicit validation step in the Approach workflow, e.g. 'Verify each element against its character/pixel limit before delivering; regenerate any element that exceeds the limit.'

Make the mobile-vs-desktop truncation check a concrete checkpoint rather than only a listed consideration.

Dimension	Reasoning	Score
Conciseness	The domain sections (Optimization Rules, Output template) are lean and useful, but generic boilerplate in 'Use this skill when', 'Do not use this skill when', and the abstract 'Instructions' bullets ('Apply relevant best practices and validate outcomes') pad the token budget without adding skill-specific value.	2 / 3
Actionability	Concrete, specific guidance throughout: explicit character/pixel limits ('under 60 characters', '50-60 characters', '150-160 characters'), placement rules ('Primary keyword in first 30 characters'), and a copy-paste-ready Meta Package Delivery template with char counts.	3 / 3
Workflow Clarity	The Approach section lists a clear 6-step sequence, but validation is only mentioned as a deliverable ('Character count validation') rather than as an explicit checkpoint within the workflow, leaving feedback loops implicit.	2 / 3
Progressive Disclosure	No bundle files exist, and the single-file skill is organized into well-labeled sections (Focus Areas, Optimization Rules, Approach, Output) with no nested references; per the simple-skills note, well-organized sections warrant a 3.	3 / 3
	Total	10 / 12 Passed

Description

50%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states concrete capabilities in third person but weakens with a second-person imperative and a vague 'Use PROACTIVELY for new content' trigger that lacks concrete firing conditions. It answers what the skill does well but only weakly addresses when to use it. Natural trigger-term coverage is partial, missing common SEO phrasings.

Suggestions

Rewrite the trigger in third person with concrete conditions, e.g. 'Use when generating or revising page meta titles, meta descriptions, or URL slugs for SEO, or when the user mentions meta tags, SERP snippets, or on-page SEO.'

Add common user terms like 'SEO', 'meta tags', 'title tag', 'SERP snippet', and 'slug' to improve trigger-term coverage.

Drop the vague 'for new content' framing in favor of specific scenarios (new posts, page launches, CMS metadata fields).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Creates optimized meta titles, descriptions, and URL suggestions', 'Generates compelling, keyword-rich metadata'), which would score 3, but the second-person imperative 'Use PROACTIVELY for new content' incurs the prescribed -1 voice penalty, bringing it to 2.	2 / 3
Completeness	The 'what' is clearly answered (titles, descriptions, URLs, metadata), and a trigger clause exists, but the 'when' ('Use PROACTIVELY for new content') is too vague to match the explicit, concrete triggers expected for a 3.	2 / 3
Trigger Term Quality	Relevant keywords like 'meta titles', 'descriptions', 'URL suggestions', and 'keyword-rich metadata' appear, but common user phrasings such as 'SEO', 'meta tags', and 'title tag' are missing, and 'new content' is generic.	2 / 3
Distinctiveness Conflict Risk	The SEO meta niche is somewhat specific, but the generic 'new content' trigger and overlap with broader SEO/content skills leave moderate conflict risk.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/seo-meta-optimizer/SKILL.md
Commit: e63f7dd

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.