CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-meta-optimizer

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

61%Weight 40%Scale 1-5

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

The content delivers genuinely specific and actionable SEO metadata rules with a concrete output template, and is reasonably well structured as a single-file skill. Its weaknesses are padding from generic trigger/instruction boilerplate, an Approach sequence lacking explicit validation checkpoints, and abstract step wording that undercuts copy-paste readiness.

Suggestions

Delete the "Use this skill when" / "Do not use this skill when" and "Instructions" boilerplate sections — they are circular filler whose job is already done by the frontmatter description, and they waste context tokens.

Weave validation into the Approach as an explicit checkpoint, e.g. step 5: "Verify character counts for every element against the limits above before delivery", instead of listing "Character count validation" only as a deliverable.

Add one worked example in the Output section (real keyword, filled title/description/URL with actual counts) so the guidance is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The core sections ("Optimization Rules", "Output") are dense and useful, but the circular "Use this skill when ... seo meta optimizer tasks or workflows" / "Do not use this skill when" sections and the generic "Instructions" bullets ("Clarify goals, constraints, and required inputs") are pure padding. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the noticeably-verbose anchor, since no concepts are re-taught.

3 / 5

Actionability

Concrete numeric limits ("under 60 characters", "50-60 characters", "Primary keyword in first 30 characters", "150-160 characters") plus a copy-ready output template with char-count annotations give mostly executable guidance. It falls short of 5 because the Approach steps are abstract ("Balance keyword placement with compelling copy") and there is no worked example with real keywords.

4 / 5

Workflow Clarity

The six-step Approach is clearly sequenced, but validation ("Character count validation") appears only as a deliverable bullet outside the sequence, so checkpoints are implicit rather than built into the workflow. This is not a destructive or batch operation, so the cap rule is irrelevant; it sits at "steps listed but validation gaps" rather than 4 because no step instructs verifying counts before delivery.

3 / 5

Progressive Disclosure

The body is well-organized into clear sections and is appropriately self-contained with no external files. It does not reach 5 because at ~80 lines it exceeds the under-50-line simple-skill exception, and the trigger boilerplate ("Use this skill when" / "Do not use this skill when") is misplaced content that belongs in the description.

4 / 5

Total

14

/

20

Passed

Description

67%Weight 40%Scale 1-5

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 communicates a clear, specific capability set in third person with an explicit use-when clause. Its main weaknesses are the absence of the most natural trigger term ("SEO") and related synonyms, and a vague when-clause ("Use for new content") that could over-trigger on any content-creation task.

Suggestions

Add natural trigger terms users actually say, e.g. "SEO metadata", "meta tags", "title tags", or "search result snippets", since "SEO" is the most likely keyword and is currently absent.

Make the when-clause concrete: replace "Use for new content" with something like "Use when creating or optimizing page titles, meta descriptions, or URLs for SEO, e.g. when publishing a new page or post."

Consider naming one or two more specific actions (e.g. character-count validation, A/B variations) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Creates optimized meta titles, descriptions, and URL suggestions" lists several concrete deliverables grounded in "character limits and best practices", matching the several-specific-actions anchor. It falls short of 5 because coverage stays at the artifact level without more granular actions.

4 / 5

Completeness

The "what" is clear (creates meta titles, descriptions, URL suggestions) and an explicit when-clause exists ("Use for new content."), matching the both-present-but-when-could-be-more-specific anchor. It is not 5 because "Use for new content" lacks concrete trigger phrases, and not 3 because the when-clause is explicitly stated rather than missing.

4 / 5

Trigger Term Quality

Terms like "meta titles", "descriptions", "URL suggestions", and "keyword-rich metadata" are natural phrases, but the most common user trigger "SEO" and synonyms like "meta tags" or "SERP" are absent. This matches "some relevant keywords but missing common variations or synonyms" rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

Meta-tag optimization is a clear niche with mostly distinct triggers around titles, descriptions, and URLs. It is not 5 because the broad "Use for new content" clause creates minor overlap risk with general content-creation skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/seo-meta-optimizer/SKILL.md

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.