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 PROACTIVELY for new content.

Quality

71%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/seo-meta-optimizer/SKILL.md

The canonical home for this skill is seo-meta-optimizer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers genuinely concrete numeric optimization rules and a clear step sequence, but it is diluted by circular boilerplate sections, duplicated platform guidance, and a reference to a nonexistent `resources/implementation-playbook.md`. Removing the filler and fixing or dropping the dead reference would make this a tight, self-contained skill.

Suggestions

Delete the circular "Use this skill when"/"Do not use this skill when" sections and the generic "Instructions" bullets — they restate the skill name and add guidance Claude already follows by default.

Fix the dangling reference: either remove "open `resources/implementation-playbook.md`" or create the actual file (and use the conventional `references/` directory) so progressive disclosure works.

Add one worked example (input content → real title/description/URL with counted characters) and fold the duplicate WordPress Yoast/RankMath bullets into the single Platform-Specific section.

DimensionReasoningScore

Conciseness

The Optimization Rules and Approach sections are lean, but the boilerplate "Use this skill when" section is circular filler ("Working on seo meta optimizer tasks or workflows" restates the skill name), the generic "Instructions" bullets ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") tell Claude nothing it doesn't know, and WordPress Yoast/RankMath guidance is duplicated in both "Additional Deliverables" and "Platform-Specific". This is more than the minor trimmable instances of anchor 4, matching anchor 3 (mostly efficient but includes unnecessary material that could be tightened) rather than the severe padding of anchor 2.

3 / 5

Actionability

Concrete, executable specs abound: "Keep under 60 characters", "Primary keyword in first 30 characters", "150-160 characters optimal", a 6-step Approach, "3-5 variations per element", and a structured output template. It falls short of anchor 5 because the output block is placeholder-only — no worked example showing actual input content turned into a real title/description package — leaving a minor gap rather than the pseudocode vagueness of anchor 3.

4 / 5

Workflow Clarity

The numbered Approach (analyze content → extract benefits → calculate limits → create 3-5 variations → optimize for mobile/desktop → balance keywords) is a clear sequence, and "Character count validation" in deliverables acts as a checkpoint. It misses anchor 5 because validation is listed as an output, not an explicit workflow step with a fix-and-retry loop (e.g., recount and trim when a title exceeds 60 chars). No destructive or batch operations are involved, so the score-3 cap does not apply.

4 / 5

Progressive Disclosure

Sections are well organized and the skill is short enough to be self-contained, but the sole reference — "open `resources/implementation-playbook.md`" — points to a file that does not exist in the bundle (no references/, resources/, scripts/, or assets/ directories are present), a dangling pointer that breaks navigation. This fits anchor 3 (references present but not working/clearly organized into a bundle) rather than 2, since no content that belongs in separate files is inlined and structure is otherwise good.

3 / 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 answers both 'what' and 'when' with several concrete deliverables, but it leans on buzzwords ("compelling", "keyword-rich") and misses the single most natural trigger keyword: "SEO". The 'when' clause ("Use PROACTIVELY for new content") is too generic to serve as a reliable trigger.

Suggestions

Add the natural keywords users actually say: "SEO", "meta tags", "title tag", "search snippet" — e.g., "Creates SEO meta tags (title, description) and URL suggestions...".

Replace "Use PROACTIVELY for new content" with concrete triggers: "Use when publishing or updating web pages, writing meta titles/descriptions, or auditing character limits for SEO".

Cut the redundant second sentence ("Generates compelling, keyword-rich metadata") and replace it with a distinct capability such as validating character/pixel limits or generating A/B variations.

DimensionReasoningScore

Specificity

"Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices" lists several concrete deliverables, but "Generates compelling, keyword-rich metadata" is redundant filler and coverage gaps remain (e.g., no mention of analysis of existing content or validation). It sits above anchor 3 (only 1-2 actions) but below anchor 5 (comprehensive coverage) because the second sentence repeats the first rather than adding new actions.

4 / 5

Completeness

The 'what' is clear (creates optimized meta titles, descriptions, and URL suggestions) and a 'when' clause is present ("Use PROACTIVELY for new content"), so it clears the anchor-3 cap for a missing trigger. It does not reach 5 because the 'when' is vague — "new content" does not specify content publishing, page edits, or character-limit audits, and lacks concrete trigger phrases.

4 / 5

Trigger Term Quality

The terms "meta titles", "descriptions", and "URL suggestions" are relevant, but the most natural user phrases are absent: "SEO", "meta tags", "title tag", "search snippet". "Use PROACTIVELY for new content" is also a weak, generic trigger. This matches anchor 3 (some relevant keywords, missing common variations/synonyms) rather than 4, which requires good keyword coverage with only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

Metadata optimization is a fairly distinct niche, but the description omits "SEO" and "meta tags", creating minor overlap risk with general copywriting, marketing, and broader SEO skills whose triggers ("compelling", "keyword-rich") could fire first. It is more distinct than anchor 3 (still notable overlap with similar skills) but does not have the clear niche triggers of anchor 5.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/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.