AGENT SKILL

meta-title-optimizer

Writes title tags and meta descriptions that survive SERP truncation, place the primary keyword early for relevance, and frame the snippet to win the click against competing results. Use when someone asks "write a title tag for this page", "why does this page rank but get no clicks", "is my title too long", "rewrite my meta description", or wants a snippet that stands out from the pattern on the results page. Do NOT use for broad on-page or technical SEO (headings, internal links, schema, crawlability, Core Web Vitals) - use seo-optimizer. Do NOT use for classifying what searchers want from a query - use search-intent-classifier. Do NOT use for finding what content the page itself is missing versus competitors - use serp-gap-analyzer.

License 许可
MIT
所属仓库
SkillMedev/skills
最近更新
2026-10-14
Stars
★ 25
Forks
3

01 前言 Front Matter

name
meta-title-optimizer
metadata
{ "title": "Meta Title Optimizer" }
description
Writes title tags and meta descriptions that survive SERP truncation, place the primary keyword early for relevance, and frame the snippet to win the click against competing results. Use when someone asks "write a title tag for this page", "why does this page rank but get no clicks", "is my title too long", "rewrite my meta description", or wants a snippet that stands out from the pattern on the results page. Do NOT use for broad on-page or technical SEO (headings, internal links, schema, crawlability, Core Web Vitals) - use seo-optimizer. Do NOT use for classifying what searchers want from a query - use search-intent-classifier. Do NOT use for finding what content the page itself is missing versus competitors - use serp-gap-analyzer.

03 SKILL.md 正文

Meta Title Optimizer

Write the title tag and meta description for a single page so the snippet fits SERP limits, earns relevance, and wins the click. This skill owns snippet copy only; broader on-page work belongs to seo-optimizer. The costly mistake it prevents: a page that ranks but bleeds clicks to worse pages with better snippets - position without click-through is rent paid on a store nobody enters, and an overlong or generic title is the usual cause.

Operating procedure

Step 1: gather inputs

  • The page's primary keyword - one term. A second keyword means a second page, not a longer title.
  • The search intent behind it (informational, comparison, transactional). If unknown, infer and label the inference a guess, or route to search-intent-classifier.
  • What the page actually delivers: its H1 and main content. The snippet must be able to keep its promise.
  • The current title/description and, if the page already ranks, its click-through problem ("ranks #4, CTR under 2%").

If the keyword or the page content is unknown, ask before writing.

Step 2: read the live SERP

Look at the current top results for the keyword. Note the dominant title pattern - the phrasing most results share - so it can be broken instead of blended into. A snippet that looks like the other nine is invisible at any position.

Step 3: draft the title tag

  • Lead with the primary keyword or a close natural variant in the first few words. Relevance is read left to right by both engines and humans.
  • Keep it to 55-58 characters and treat 60 as the hard ceiling - titles truncate near 580 pixels, and wide capitals (W, M, all-caps words) consume the pixel budget faster than a character count implies. A truncated title loses its promise mid-sentence.
  • Append the brand after a separator (| or - ) only if room remains. Never let the brand push the keyword or the payoff past the cutoff.

Step 4: differentiate the framing

If every competing title repeats the same pattern, break it with one CTR pattern - never stack several:

  • A specific number ("7 Ways", "in 15 Minutes", "$40/mo") - specificity signals substance; odd and concrete beats round and vague.
  • A concrete benefit or outcome the page actually delivers.
  • A question that mirrors the query when intent is informational.
  • A bracketed qualifier ("[Template]", "[Checklist]", "[Free]") when the page contains that artifact.

Match the intent: a transactional query wants the product and the differentiator, not a clever question.

Step 5: draft the meta description

  • Front-load the value in the first ~155 characters; the rest truncates, and on mobile the cutoff comes sooner.
  • Mirror the searcher's own words so the engine bolds the matched terms - bolding is free visual weight.
  • Name one concrete differentiator: a number, "free", "step-by-step", a unique angle.
  • End with a soft call to action ("See the full comparison", "Get the template").

Step 6: verify against the page

Confirm the title and description reflect the H1 and the page's real answer. Overpromising gets the title rewritten by the engine and bounces the users who do click - both lose. If the engine is already rewriting the current title, treat that as evidence of a title/content mismatch, not bad luck.

Worked contrast pair

Page: a guide to home cold brew ratios with a conversion table. Keyword: "cold brew ratio".

Bad title (78 chars, keyword buried, brand first, stacked patterns):

AcmeCoffee Blog | The Ultimate, Complete 2-Minute Guide to Perfect Cold Brew Coffee Ratios!!

Truncates around "Guide to", the keyword arrives after the cutoff on narrow displays, the brand spends the best pixels, and the hype ("Ultimate, Complete", "!!") promises nothing specific.

Good title (52 chars, keyword first, one pattern, room for brand):

Cold Brew Ratio: 1:4 to 1:8 Explained [Chart] | Acme

Bad description (value after the cutoff):

Here at Acme we have been passionate about coffee for many years and we love sharing everything we know about brewing methods with our wonderful community of readers, including cold brew.

Good description (147 chars, front-loaded, one differentiator, soft CTA):

Cold brew ratio made simple: 1:4 for concentrate, 1:8 ready-to-drink, with a cups-and-liters chart for any batch size. See the full ratio table.

Deliverable

Produce, per page: one title tag (with character count shown), one meta description (with character count shown), a one-line rationale naming the SERP pattern being broken and the differentiator used, and a pass/fail note against the quality bar below.

Do NOT

  • Do not stuff a second keyword or repeat the brand in every title - dilution costs relevance and reads as boilerplate.
  • Do not use ALL CAPS or clickbait the page cannot deliver; the engine rewrites dishonest titles and the users bounce.
  • Do not pad a description past ~155 characters expecting the overflow to display - the payoff must land before the cutoff.
  • Do not ship auto-generated boilerplate titles that read identically across the site; every page competes in its own SERP.
  • Do not hardcode a year or other dated token into evergreen titles; it goes stale and forces maintenance.
  • Do not stack CTR patterns (number + brackets + question + emoji); one differentiator reads confident, four read desperate.

Quality bar

  • Title is 55-58 characters (60 hard max) and survives truncation with the keyword and the payoff intact.
  • Primary keyword or a close variant appears in the first few words; no second keyword stuffed in.
  • Meta description front-loads value within ~155 characters and contains exactly one concrete differentiator.
  • Title and description accurately match the H1 and on-page content - nothing promised that the page does not deliver.
  • Snippet is visibly distinct from the dominant pattern in the live SERP, using one CTR pattern, not several.

04 同仓库更多 Skills

SkillMedev
SkillMedev/skills

有氧运动计划

zone-2-cardio-plan

当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。

★ 25
SkillMedev
SkillMedev/skills

youtube-script-writer

Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.

★ 25
SkillMedev
SkillMedev/skills

win-back-campaign

Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.

★ 25
SkillMedev
SkillMedev/skills

wikipedia-style

Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.

★ 25
SkillMedev
SkillMedev/skills

whitepapers

Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.

★ 25
SkillMedev
SkillMedev/skills

white-space-analysis

Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.

★ 25